UML Events and Signals Common Modeling Techniques

Testability Tips

⊕The following are some tips related to path testing regarding testability and for creating testable software
⊕Count the total number of paths (C₁), the total number of achievable paths (C₂) and the number of paths required for achieving C₂ coverage (C₃). The closer the numbers C₁, C₂, C₃ the more testable the software is

⇒Make your decisions only once and stick to the plan without making decisions in the middle
⇒Don't compress the code
⇒Build the software only if you can test it
⇒Don't introduce any additional functionality, generalizations and extras to the code as that needs more cases to cover
⇒Be sure about how to sensitize a path that you need for coverage
⇒Covering paths is very important for functionality
⇒Avoid deeply nested and horrible looping code. They don't indicate the skill of the programmer
⇒Avoid flags, switches, program status counters and other violations of code as they make things complex
⇒The most important is to always remember - Don't reduce/compress the code