andre-nunes/cesium — pull request #1 by mramato (2013-07-18 17:55:42+00:00)
Title: Improve unit tests for Point geometry.

Andre, as I mentioned I write two new test for you to help you implement other tests for your new development. Good tests can go a long way to making sure your code works as intended. Here are some general rules for good tests.

1. Tests should not depend on each other, so each test can run individually and in any order.
2. Tests should only test 1 thing (within reason), for example, don't write a test that does position and billboards. Have a test for position and a test for billboards. The name should clearly state what it is doing.
3. Make the test as simple as possible to actually test what you want. For example, your existing Point Geometry test had a giant string for it's KML sample file that included a style and color. You are only testing Point geometry, so none of that is needed.
4. Actually test the values. You were checking that a position was created, but you weren't verifying that the position was actually correct.

Hope that helps. You can merge this and ask any questions in your open pull request if you have them.