Tag: documentation

Introduction Documentation is “How a product is expected to be used” and needs to be accurate, understandable, and up-to-date. Documentation that is: Accurate can become long and cryptic (bad for understanding and updating) Often updated, can become fluffy and fragmented (bad for accuracy and understanding) Understandable can become long and shallow...

Introduction A test case describes the properties and behavior of a system. Knowing what a test case is, will improve your documentation, specifications, and code by making them testable and easier to read and understand....

Introduction Testing helps with complexity, but need to be applied at the right situation, to deal with complexity, without adding increasing it unnecessary. Complexity level 0 – clarity The code is simple and easy to read. How to deal with it: No need to test it and no documentation...