Vault7: CIA Hacking Tools Revealed
Navigation: » Latest version
Owner: User #524297
Developer Testing
THOU MUST
- Test your code, we don't have dedicated beta testers
THOU SHOULD
- Write unit tets to assist with regression testing
- Isolate code as much as possible; test the isolated units
- Utilize industry standard testing libraries like googletest, winunit, or pyunit
- If manual tests are required, document what those tests are so future developers are aware
- Test "The Good, the Bad, and the Ugly"
- Good - Expected values
- Bad - Acceptable but extreme values
- Ugly - Out of range values (does the function fail as expected)
- Follow a consistent naming pattern for your tests
THOU SHOULD NOT
- Test TRULY trivial code (think getters and setters)
- Test non-determinist code or write non-deterministic tests (think random numbers) (if you must, look into Google Mock to abstract away what you are truly trying to test)
THOU MUST NOT
- Write your own unit testing framework