Tests about three.js HOT 7 CLOSED

Uh, I have 0 experience with unit testing :D

from three.js.

lol ok i'll do something. maybe some markdown documentation too?

from three.js.

Sure! Some parts of the API seem to be getting pretty stable. I guess some documentation would be helpful for people trying to use the lib :)

from three.js.

Was this intentionally closed? : )

I think a good place to start would be adding expects to the existing examples and at least have some smoke tests. Then work down into core.

from three.js.

Feel free. I don't think it's something I would like to maintain myself though.

from three.js.

If I put the infrastructure in place and tested the current codebase, would you add new tests to future changes? That's key , since one of the benefits of tests is preventing regressions, because new features tend to introduce bugs in existing features. It's a common practice in TDD to ensure that every bug fix also has a new test added that defines the decision and locks in the fix. And stable releases can't have failing specs. Would you be on board with that? Or do you have an idealistic disposition to TDD?

BTW: It's actually really surprising to me that the project is as stable as it is without any tests. I've never seen anything like it. Normally if something gets to this size it starts to collapse under its own gravity as new features break things. I think the reason for this is A) you have some incredibly strong powers of foresight, and as such the the architecture is very well thought out from the start. and B) you probably pop open examples before committing changes to make sure they still work, which is some manual QA.

from three.js.

Yeah, we use the examples as tests. And we have incredibly strong powers of foresight too ;)

from three.js.