software testing test methodologies

Assignment 3 Best Sell Test Plan

As discussed in class, for the Best Sell project please:

Form a team of 2 (maximum 2) and Enroll You and Your partner in a Project&Assign3 FOL Group, and:

1. Create A test plan (Using the exact Template as built in class) , focusing on the specific test cases and the important features/functions/screens of the project as described in FOL and discussed in class (This template was built starting from FOL content slides in Lesson 4 using the IEEE 829 Test Case specifications).

a. Use the knowledge you have gained in this course & the detailed description of the Best Project Requirements to create all your test cases. Separate your test cases into Valid & Invalid cases (when complete you will need to “merge the test cases together by creating 1 excel spreadsheet with 2 tabs, 1 for VALID and 1 for INVALID). You will also review each others test cases since you both must learn how to do both types, and you will indicate which student created the Valid & which student created the Invalid cases in the Assignment Dropbox comments.

b. Make sure to include/indicate the order that you plan to execute these test cases, and why they need to be in that order.  Just put this info at the top of your test Cases. (Yes, often a Test Plan might also include details of exactly who & when - what date each test case is expected to be executed - but please include in your "Test Plan" the expected order - but NOT dates. This is because when a project starts usually there is an order that things must be done in, and some planned dates ... but usually - in fact almost always - those dates will change...)

2. Update your Test Strategy: Decide which partner's Test strategy you are going to start with, and update that persons original Test Strategy (that you already handed in earlier this semester) based on:

a. Information you have both learned recently - in class / feedback / etc.

b. Discussion with your partner of their original Assignment 2 Test Strategy. 

c. Remember to include a specific revision history update.

d. When finished your updates, create an MS Word comparison of your Original Test Strategy and the updated Test Strategy document (it should highlight the differences between these 2 versions of the document!). NOTE: This will serve multiple purposes :

1. You will be able to confirm you included all the changes you wanted

2. You will be able to use this same compare process to automatically compare TEST OUTPUT as part of any re-test (something you will be doing soon as part of the next project)

   Rules for Assignment Dropbox submission :

1. I will be looking for Just 1 Student to submit, and list their Partner's name & their Partner's student # in the Assignment dropbox comments, stating who created the valid & who did the invalid cases. Submit these 3 files as created/described above,:

1. The Test Plan (including all your test cases IN 2 TABS – 1 Valid & 1 Invalid).

2. The Updated Test Strategy.

3. The MS Word comparison file of the students original Test Strategy compared to the Updated Test Strategy (Should show changes highlighted).

2. As discussed in class do not share your Assignment solutions with anyone who is not your partner.  

3. Note compressed (ZIP , etc. ) files will not be accepted - please submit the individual MS Word/Excel files). 

Rubric / Grading :

Item	Description	Weight
Updated Test Strategy	Updated as per detailed instructions/feedback & compared	15%
Test Cases ID & Description	All cases created as expected, using template instructions, for all expected fields	30%
Test Case Expected/Actual results	All cases created as expected, using template instructions, for all expected fields	20%
Test Case Assumptions/Order	Test plan / test case document includes test environment/user assumptions, and expected order of test cases.	15%
Test Plan clear	Test plan with test cases uses template, is updated following instructions, and is clear/logical.	20%
Not following instructions	Penalty for not following instructions	Up to - 20%
Total		100%