| || |
How to measure product coverage
How to measure product coverage using modules, business flow and interfaces.
This is one of the goal and can some one explain me what would each of them refer to when we say modules for product
Can some one give me examples of module sol, business flows and interfaces
Can you please elaborate in detail on what is your expectation.
To give an "In general" explanation of just product coverage...
Ensure that you have understand the domain well + product design. Then come up with a test design that would help you to group your test cases. Create a test design that would help you to "cover" all aspects of the product with respect to the domain.
A typical way, in which I would want to look at this would be to identify checks for...
2. Functional (Happy Paths)
4. Internal Workflows (covering a product or a single application per se with multiple modules).
5. External Workflows (covering many applications).
7. Batch jobs.
8. Security Requirements &
You can add more types - based on specialized "business" needs and create a test design.
Once, you implement a test design, you can then work on an approach - on how optimally you can create the required test types given above. This is again driven by business priorities etc... (you would need to consult the business and technical heads for this).
This can be then used to "define" product coverage.
Since, you have the "number" of test cases or test scenarios now, this gives the metrics that "defines" the product / application coverage.