Continuous Integration Visualization Technique (CIViT)

Unit testing, component testing, E2E testing... There are different types of test that we use to check product quality. But is it enough? Are you sure?

CIViT is the model that is intended to visualize testing activities, identify bottlenecks and missing test coverage. It maps what is tested, when and at what automation level.

CIViT defines the following types of testing activities:
🔸 Functionality (F). This type checks functionality that is under development.
🔸 Legacy Functionality (L). It's regression testing that verify that previously delivered features are not broken.
🔸 Quality Attributes (Q). There are non-functional tests like performance, reliability, security, etc.
🔸 Edge Case (E). This type covers unusual or unexpected usage scenarios, that are typically discovered from defects.

Each type of testing is measured by automation level (manual, partial or full), execution frequency and coverage (fully covered, partially or not covered). The model often uses colors to indicate the state: e.g., green = fully automated or fully covered; orange = partial; red = manual or not covered.

The model can help to answer the following questions:
🔸 Which level of test requires the most manual efforts?
🔸 Are there any long feedback loops (e.g., regression tests only once per release) causing risk?
🔸 Are there missing tests for quality attributes or edge cases?
🔸 Is there some duplication in testing?
🔸 Where should you invest to increase reliability and improve quality?
 
Actually I cannot say that visual representation of the model is really clear (check next post with samples), probably it's the reason the model didn't become popular. But I think it's a good and helpful tool to perform the audit of your testing activities.

#engineering #testing #ci