Tests: Set individual tests as TODO, not modules.

[donmccurdy]

Fixes #12714, fixes #12759.

Also removes TODOs on private methods (or the ones that I found, anyway...).

	result
before
after

[donmccurdy]

/cc @Itee

[mrdoob]

Thanks!

[Itee]

It is better to mark todo in the right place.

But remove the test about private methods is an error i think !
Currently we are unable to prove that private methods are correct ! And IMO they should be tested harder than public interface.

[donmccurdy]

Currently we are unable to prove that private methods are correct ! And IMO they should be tested harder than public interface.

It's OK for people to contribute tests of private methods when they're helpful, but in general I do not think all private methods should have tests. See discussion here. It is better to test what happens, rather than how it happens, and private methods are often the latter.

Certainly it is fine for tests on private methods to be written — I have no objection to that — but I would rather add those tests only when/if they make sense, and not to have TODOs complaining when they aren't there.

[Itee]

Ok i understand your opinion !

But like said in comment:

I disagree. Ideally, you write a quick test before you start coding a function. Think of typical input and what the output will be. Write the test (which shouldn't take you longer than a few seconds) and code until it gets the test right. There is no reason to abandon that style of work for private methods. – Frank