Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.
Sign up to join this community
Currently I have a program that I'm tentatively done with and I'm comparing the output with the output of a process that is known to be correct.
This is a once a day process.
How many times should I call it good if the output of my program matches the process output?
A week? (5 correct outputs 1 per day)
OR
A month? (20 correct outputs 1 per day)
I don't want any errors on this program as that would be pretty bad as this is an important process.
Phase 1 Run smoke tests, if bugs = 0; Run Tests of the most critical requirements Else fix bug AND Run smoke tests
Phase 2 Run Tests of the most critical requirements if bugs = 0; Run Full Regression Else fix bug AND Run most critical requirements
Phase 3 Run full regression if bugs = 0; Ready for homologation tests by the business area and THEN Release
if that dont is what you need, you should do performance tests with a load above average so you can see on a long shot how your software will behave on a stress
