Increase coverage report. Unit testing

[sasha240100]

Coverage on coveralls decreases. That's why we need to add more tests for Whitestorm.js API.
Those should include:

• Components
  • AreaLight
  • Model
  • Text
  • Line
• Modules
  • PostProcessorModule
  • VirtualMouseModule
  • DynamicGeometryModule
• Controls
  • OrbitModule

Version:

• v2.x.x
• v1.x.x

Issue type:

• Bug
• Proposal/Enhancement
• Question

---

Tested on:

###### --- Desktop - [ ] Chrome - [ ] Chrome Canary - [ ] Chrome dev-channel - [ ] Firefox - [ ] Opera - [ ] Microsoft IE - [ ] Microsoft Edge

--- Android

• Chrome
• Firefox
• Opera

--- IOS

• Chrome
• Firefox
• Opera

[sasha240100]

@nickooms Any progress?

[hirako2000]

Looking at the existing tests, we have a few problems there:

• Existing tests' spec don't describe properly (see example of proper description done the FogModule tests).
• More assertions should be added across existing tests, not just those mentioned on this issue
• The Structure should change, I suggest we bring tests closer to each src files (or maybe folder to keep src lists clean) as an incentive to add tests as we add code.
• I suggest we raise an issue to bring structure to test folder, and simply encourage adding tests where missing to parts of code that gets modified. e.g I modify the TextureModule to add some param? I add test for the TextureModule if missing, then add my test to cover the new param.

Check tests during code review. Unless unreasonably difficult, I feel all PRs should include
appropriate tests (except for examples).