Software testing plan

The specification for your system is as follows: At the start of each rental transaction, the system will first scan a barcode to do a customer lookup. (Assume other people in the company will be writing the database software. Your software only needs to be passed a date of birth, followed by a progression of ratings. In other words, you will be using test stubs to test your software.)

After the date of birth is received, the system will scan bar codes on each game being rented. This time, instead of being passed a date of birth, the test stubs will return a series of video game ratings. Video game ratings and restrictions are shown in the accompanying table. This process loops until the cashier signals the end of the transaction (in other words, no more games to be scanned).

Your software must (1) correctly calculate an age given a date of birth and today’s date, and (2) correctly determine whether or not each item being rented passes the store’s age restriction policy or not.

Part 2. Project Milestones & Expectations In accordance with the V-Model for software development, you will begin by writing the test plan. Then you will write the software, then you will execute the test plan. Due dates are as follows:

Note: Make sure you employ the principles of equivalence class testing and boundary testing when you write your test plan!

Note: Make sure you employ the principles of equivalence class testing and boundary testing when you write your test plan!