Description of Issue
There’s some inconsistency in how test types are labeled in the plan. Ideally, each test should specify both whether it’s “dynamic” or “static” and whether it’s “automatic” or “manual,”. Some tests only include one of these distinctions or both, making it harder to understand the full testing approach.
In addition, a few tests that are challenging to automate have been marked as automated (such as static testing of the database compliance) without a clear explanation of how the static tests are going to be conducted, while some easier tests, like frontend ones, are set as manual.
Artifact Under Review VnV Plan
Team Number for Team Doing the Review Group 19
Description of Issue There’s some inconsistency in how test types are labeled in the plan. Ideally, each test should specify both whether it’s “dynamic” or “static” and whether it’s “automatic” or “manual,”. Some tests only include one of these distinctions or both, making it harder to understand the full testing approach.
In addition, a few tests that are challenging to automate have been marked as automated (such as static testing of the database compliance) without a clear explanation of how the static tests are going to be conducted, while some easier tests, like frontend ones, are set as manual.