In the initial release of an insurance risk assignment application, a variety of test techniques were employed, especially equivalence partitioning.
After a thorough root cause analysis of this release, it was determined that the developers tended to incorrectly use ">" and "<" rather than the ">=" and " <= " in the code at several decision points.
This caused several borderline cases to be handled incorrectly.
Based on this analysis, how would you modify your test strategy for the next version's release?
Boundary value analysis is a technique that focuses on testing the values at the boundaries of valid and invalid partitions. It is suitable for testing the errors caused by incorrect use of relational operators in the code, such as ''>'' and ''<'' instead of ''>='' and ''<=''. By creating test cases using boundary value analysis, the tester can verify that the system handles the borderline cases correctly and does not miss any edge cases.
Reference=
ISTQB Advanced Level Test Analyst Syllabus 2019, Section 3.2.2.2, page 411
Software Testing - Boundary Value Analysis - GeeksforGeeks2
State Transition Testing -- Diagram & Technique (Example) - Guru993
Evan
3 months agoMeghann
3 months agoLorrine
2 months agoGilbert
2 months agoDaryl
2 months agoGladys
3 months agoIsreal
3 months agoGerardo
3 months agoCyndy
2 months agoAlysa
2 months agoLigia
2 months agoLawanda
3 months agoStanford
2 months agoLynelle
2 months agoJean
3 months ago