Functional Verification testing (FVT) is usually performed post Unit testing, and before System Verification testing (SVT) / Integration testing. In general, in all System Verification test plans, I found entry criteria for SVT is FVT should be at least 100% attempted and 80 % passed. Here I am listing learning after leading FVT for one of the enterprise appliance products-1. FVT not only builds confidence in the quality of the module under development but also creates a positive vibe for that module. When we sign off from FVT, we observed that developers felt more confident as the happy path is working as expected. SVT team is confident too as there won’t be any functional blockers and they can start the verification from the first day itself.
2. As an FVT engineer, we are quality gatekeepers who are involved in the quality phase very early on, helping developers to identify the issues, defects, or any other missing requirements.
3. As we have started FVT hand in hand with the development team, test data was created at a very early stage. Also, accurate test data was shared with the SVT team which can be further enhanced by the SVT team and can be used easily during SVT Phase.
4. Early FVT helps to discover many missing defects which can be marked as “works-as-design” “missing design” “deferral candidate”, as these defects found out in early phases these were fixed and available. It also adds extra quality as well as usability to the feature.
5. FVT acts as a liaison between Dev and SVT teams as direct communication between them is usually lacking as their priorities and vocabulary do not always match. SVT team leverages the FVT team to get more clarity on any issues or doubts regarding development. I have observed that “the more quality of FVT, the more happy the customer will be”. As we know, a first impression makes a huge impact and the first impression for an individual module is achieved via better functional verification for that module.