How many separate tests will need to be conducted to prove that this new code is working correctly

A program needs to be modified to take some specific action, “PROCEDURE1” under certain conditions. PROCEDURE1 will try to read FILE1 found among the user’s personal data files. The modified code will need to work correctly whether the file is present or not present. Whenever PROCEDURE1 is executed, it will create a new FILE1 with a date-stamp record.

The user screen that triggers execution has 2 relevant selections:
- “Update And Exit”
- “Done”

Here are the rules that will control this action:

a) If the user selects “Update And Exit”, then PROCEDURE1 will be executed.

b) If the user selects “Done” and FILE1 does not exist, or it exists, but the date stamp is 30 days or older than the current system clock value, then PROCEDURE1 must be executed. Otherwise a different DONEPROCEDURE must be executed.

From the above requirements rules, how many separate tests will need to be conducted to prove that this new code is working correctly for all possible conditions according to the specifications? For each test, identify the test conditions, e.g. user-entered parameters, FILE1 condition. Are there any error conditions that should be tested?

Showing Answers 1 - 0 of 0 Answers

As it pertains to functional testing, the answer to this question depends on the importance of the functionality that was fixed.  The fix will certainly be re-tested at least once.  If the functionality is mission-critical, it may be regression tested in each build thereafter.  It may also be tested during end-to-end and/or acceptance testing. 

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions