On Thursday 12 June 2014 01:59:22 Peter Dimov wrote:
Andrey Semashev wrote:
I think everything that needs to be tested, needs to be tested in Core. That includes legacy forwarding headers, if needed, although I wouldn't say that such a test is very useful.
Duplicating tests just adds confusion (and wastes resources, as you said). Even if we don't forget about them, which is possible, when the time comes it'll be more difficult to get rid of them. One would have to analyze both Core and Utility tests to see if anything needs to be pulled from Utility before removal. It's easier and safer to do everything once now, when the context is not lost.
That's a good point.
OK, I agree that tests that are now in Core can be removed from Utility.
Do you mean that all tests are in Core already and the tests in Utility can be safely removed? I didn't see your commit in Core. Will you remove the tests or shall I do this?
The old documentation probably needs to link to the new one so that people can "find their stuff". :-)
Agreed.