Group18-CUCE2012. Mr. Mobile Project. Software Testing Plan (STP) Version: 4.0. CM Identifier: G18_SE004

Transcription

1 Group18-CUCE2012 Mr. Mobile Project Software Testing Plan (STP) Version: 4.0 CM Identifier: G18_SE April 2010

2 Revision History Prepared/ Modified by Ahmed Adel Ahmed Abdullah, Ahmed Hafez and Sheriff Hani Version Date May 10 th, 2010 May 12 th, 2010 May 16 th, 2010 May 17 th, 2010 Approved by Descriptions/ Remarks Brainstorming on the testing elements Design of testing plan Design of testing schedules First draft of the document

3 Distribution list Name Notes Dr Sayed Hemayed For Approval Eng Mustafa Mahmoud For Approval

4 1. Introduction This STP is for Mr. Mobile, which is a mobile application that allows us to easily deal with the data on the mobile phone, All of us use mobile phone, and we all face a lot of problems using it.one of the most common problems is losing some of the data from the phone, and more specifically losing contacts. But don t worry; from now on Mr. Mobile is here! 1.1. The purpose of this STP is to give all the information needed about the testing of Mr. Mobile such as the elements of testing such as Inspection, Analysis, and Demonstration, and of course different types of testing, as the basic idea of this project is to make a mobile application that keeps an online backup of all the contacts on the mobile phone of the person who subscribes to this service, where in case of losing these contacts by one way or another, you can easily restore these lost contacts. The system will also be used to backup different important files on the mobile phone, like photos, important documents, and even some audio and video files, easily restoring these data in case they are lost, either by damaging of the phone, or by changing the mobile phone, this will be explained more clearly along the rest of the document. It will allow sharing the data of the subscribed person with other users (if the user allows it). And the system will also automatically add contacts of Facebook friends (if user allows it) to the mobile phone registered. This is all going to be accessible through a website by the username and password of the user, allowing him to add or edit more contacts, delete contacts or even add or delete multimedia files. All of this while maintaining the maximum security and privacy of information for the users, this will be explained more clearly at the functional requirements section. The mobile application will automatically make a notification to the application users to remind them about updating their version of backup, the users will be able to choose the time intervals between these notifications as mentioned in the functional requirements section. G18 Page 1

5 Finally, this application would mean nothing if it is not secured, reliable, fast, easy to use, and most important of all, the least in memory consumption, as will be shown at the nonfunctional requirements section Scope The scope of this STP was discussed thoroughly by the team members developing this mobile application. It was agreed-upon that the project will have more than one testing strategy, like Functional Testing, Data Testing, User Testing and Non-Functional Testing. Moreover, we are going to use other types of testing like Component Testing, System Testing which consists of Integration and Release Testing, also we are going to use Smoke Testing, Stress Testing and finally Regression Testing Overview The rest of this document is going to specify the means that we are going to follow in order to ensure that we passed on all the types of testing mentioned above as it can be applied on our project, it will also have as many test cases as needed to cover all the project. 2. Test Methodology We chose a test methodology that will help us cover as many parts of the project as possible, this test methodology is as follows: 2.1. Types of Testing Functional Testing In this section, we will identify the test cases that we are going to test after finishing the implementation phase, these test cases are as follows: G18 Page 2

6 TC_ID 1 Test Case Name Add new friend To test adding a new friend to the friends list of the user. The user is logged in, the friend isn t added before, and the friend s username already exists in the database. Low 1- Sign in. 2- Choose the friends list. 3- Choose to add a new friend. 4- Write the username of the friend. 5- Check the friends list. Expected Results The friend is added to the list. The friend is added to the list. Table 2.1 TC_ID 2 Test Case Name Add an already existing friend To test adding an existing friend to the friends list of the user. The user is logged in, the friend is added before, and the friend s username already exists in the database. Low 1- Sign in. 2- Choose the friends list. 3- Choose to add an already existing friend. 4- Write the username of the friend. Expected Results An error message appears. An error message appears. Table 2.2 G18 Page 3

7 TC_ID 3 Test Case Name Add a friend that is not registered To test adding a friend that s not in the database. The user is logged in, the friend is not added before, and the friend s username doesn t exist in the database. Low 1- Sign in. 2- Choose the friends list. 3- Choose to add an already existing friend. 4- Write the username of the friend. Expected Results An error message appears. An error message appears. Table 2.3 TC_ID 4 Test Case Name Delete a friend To test deleting a friend from the list. The user is logged in, the friend is added to the friends list before. Low 1- Sign in. 2- Choose the friends list. 3- Choose a friend from the list. 4- Choose to delete the friend. 5- Check the friends list. Expected Results The friend is deleted successfully. The friend is deleted successfully. Table 2.4 G18 Page 4

8 TC_ID 5 Test Case Name Enable sharing with a friend To test sharing data with a friend that exist in the friends list. The user is logged in, the friend is added to the friends list before. Low 1- Sign in. 2- Choose the friends list. 3- Choose a friend from the list. 4- Choose to share data with the friend. Expected Results Data sharing is enabled successfully. Data sharing is enabled successfully. Table 2.5 TC_ID 6 Test Case Name Disable sharing with a friend To test to disable sharing data with a friend that exist in the friends list. The user is logged in, the friend is added to the friends list before. Low. 1- Sign in. 2- Choose the friends list. 3- Choose a friend from the list. 4- Choose not to share data with the friend. Expected Results Data sharing is disabled successfully. Data sharing is disabled successfully. Table 2.6 G18 Page 5

9 TC_ID 7 Test Case Name Verify an existing account To test the verification of an existing username and password. High. 1- The user enters a valid username. 2- The user enters a valid password. Expected Results Account is verified successfully. Account is verified successfully. Table 2.7 TC_ID 8 Test Case Name Verify an existing account with invalid username To test the verification of an invalid username and a valid password. High. 1- The user enters an invalid username. 2- The user enters a valid password. Expected Results A message appears saying Username doesn t exist.. A message appears saying Username doesn t exist.. Table 2.8 G18 Page 6

10 TC_ID 9 Test Case Name Verify an existing account with invalid password To test the verification of a valid username and an invalid password. High. 1- The user enters a valid username. 2- The user enters an invalid password. Expected Results A message appears saying Invalid Password.. A message appears saying Invalid Password.. Table 2.9 TC_ID 10 Test Case Name Restore password via username To test if the user can restore his lost password successfully. The user is already registered to our system, and is not logged in. Low. 1- The user chooses to restore his lost password. 2- The user enters his username. Expected Results A message appears saying The new password sent to the mail successfully.. A message appears saying The new password sent to the mail successfully.. Table 2.10 G18 Page 7

11 TC_ID 11 Test Case Name Restore password via To test if the user can restore his lost password successfully. The user is already registered to our system, and is not logged in. Low. 1- The user chooses to restore his lost password. 2- The user enters his . Expected Results A message appears saying The new password sent to the mail successfully.. A message appears saying The new password sent to the mail successfully.. Table 2.11 TC_ID 12 Test Case Name Grab facebook contacts To test if the user can add his facebook contacts to his contact list. The user is already registered to our system, is logged in, and has a facebook account. Low. 1- The user signs in. 2- Chooses to grab facebook contacts. 3- Enters facebook username and password. 4- Views his contact list. Expected Results The contact list is updated successfully. The contact list is updated successfully. Table 2.12 G18 Page 8

12 TC_ID 13 Test Case Name Grab facebook contacts with wrong account info To test if the user can add his facebook contacts to his contact list if he enters invalid facebook account info. The user is already registered to our system, is logged in, and has a facebook account. Low. 1- The user signs in. 2- Chooses to grab facebook contacts. 3- Enters invalid facebook username or password. Expected Results A message appears saying Facebook account doesn t exist.. A message appears saying Facebook account doesn t exist.. Table 2.13 TC_ID 14 Test Case Name Grab facebook contacts with wrong account info To test if the user can add his facebook contacts to his contact list if he enters invalid facebook account info. The user is already registered to our system, is logged in, and has a facebook account. Low. 1- The user signs in. 2- Chooses to grab facebook contacts. 3- Enters invalid facebook username or password. Expected Results A message appears saying Facebook account doesn t exist.. A message appears saying Facebook account doesn t exist.. Table 2.14 G18 Page 9

13 TC_ID 15 Test Case Name Grab facebook contacts with wrong account info To test if the user can add his facebook contacts to his contact list if he enters invalid facebook account info. The user is already registered to our system, is logged in, and has a facebook account. Low. 1- The user signs in. 2- Chooses to grab facebook contacts. 3- Enters invalid facebook username or password. Expected Results A message appears saying Facebook account doesn t exist.. A message appears saying Facebook account doesn t exist.. Table 2.15 TC_ID 16 Test Case Name Register a new account To make sure that a new user could register if he specifies all the required data. That Mr. Mobile website is working and the user goes from the homepage to the registration page correctly. Low. 1- Open Mr. Mobile website. 2- Go to registration page. 3- Insert all required data for registration. 4- Click the register button to complete the registration. Expected Results The new Mr. Mobile is registered and to transfer to the homepage of the registered users. It s Supposed that the new user is registered and he/she became a Mr. Mobile user. G18 Page 10

14 Table 2.16 TC_ID 17 Test Case Name Register a new account with an existing username To make sure that a new user couldn t register if he/she specifies an existing username That Mr. Mobile website is working and the user goes from the homepage to the registration page correctly. Low. 1- Open Mr. Mobile website. 2- Go to registration page. 3- Insert valid data except that the username already exists. 4- Click the register button to complete the registration. An exception about the existing username appears in the Expected Results screen to the new user that he/she should choose another valid username. An exception about the existing username appears in the screen to the new user that he/she should choose another valid username. Table 2.17 G18 Page 11

15 TC_ID 18 Test Case Name Register a new account with an already used E- mail To make sure that a new user couldn t register if he/she specifies an existing . That Mr. Mobile website is working and the user goes from the homepage to the registration page correctly. Low. 1- Open Mr. Mobile website. 2- Go to registration page. 3- Insert valid data except an already used Click the register button to complete the registration. An exception about the existing address appears in the Expected Results screen to the new user that he/she should choose another valid . An exception about the existing address appears in the screen to the new user that he/she should choose another valid . Table 2.18 G18 Page 12

16 TC_ID 19 Test Case Name Register a new account with mismatching passwords To make sure that a new user couldn t register if he/she specifies two different passwords. That Mr. Mobile website is working and the user goes from the homepage to the registration page correctly. Low. 1- Open Mr. Mobile website. 2- Go to the registration page. 3- Insert valid data except inserting mismatching passwords. 4- Click the register button to complete the registration process. An exception that he/she wrote two mismatching passwords Expected Results appears in the screen to the new user that he/she should retype their password. An exception that he/she wrote two mismatching passwords appears in the screen to the new user that he/she should retype their password. Table 2.19 G18 Page 13

17 TC_ID 20 Test Case Name Register a new account with an invalid phone number To make sure that a new user couldn t register if he/she specifies an invalid telephone number. That Mr. Mobile website is working and the user goes from the homepage to the registration page correctly. Low. 1- Open Mr. Mobile website. 2- Go to the registration page. 3- Insert valid data except a valid phone number. 4- Click the register button to complete the registration process. An exception about the invalid telephone number appears in Expected Results the screen to the new user that he/she should choose a valid telephone number. An exception about the invalid telephone number appears in the screen to the new user that he/she should choose a valid telephone number. Table 2.20 G18 Page 14

18 TC_ID 21 Test Case Name Register a new account without filling all required data To make sure that a new user couldn t register if he/she specifies some missing data. That Mr. Mobile website is working and the user goes from the homepage to the registration page correctly. Low. 1- Open Mr. Mobile website. 2- Go to the registration page. 3- Insert valid data except that some of them are missing. 4- Click the register button to complete the registration process. An exception about the missing required data appears in the Expected Results screen to the new user that he/she should fill all the required data. An exception about the missing required data appears in the screen to the new user that he/she should fill all the required data. Table 2.21 G18 Page 15

19 TC_ID 22 Test Case Name Add a new contact To make sure that registered Mr. Mobile users can add new contacts to their backup. That Mr. Mobile website is working and the user can login and then he/she could go to the add contact page. High. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to manage contacts page. 4- Insert a valid contact name and number. 5- Click submit. Expected Results The new contact is now added for this user and he/she could use the new contact as it already exists on their backup. The new contact is now added for this user and he/she could use the new contact as it already exists on their backup. Table 2.22 G18 Page 16

20 TC_ID 23 Test Case Name Add a new contact with an existing contact name To make sure that registered Mr. Mobile users couldn t add new contacts to their backup if the contact name is already added. That Mr. Mobile website is working and the user can login and then he/she could go to the add contact page. High. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to manage contacts page. 4- Insert an existing contact name and a valid number. 5- Click submit. An exception about the existing contact name appears in the Expected Results screen to the new user that he/she should change their contact name and insert a new contact name that doesn t exist in their contacts. An exception about the existing contact name appears in the screen to the new user that he/she should change their contact name and insert a new contact name that doesn t exist in their contacts. Table 2.23 G18 Page 17

21 TC_ID 24 Test Case Name Add a new contact with an invalid number To make sure that registered Mr. Mobile users couldn t add new contacts to their backup if the contact number is invalid. That Mr. Mobile website is working and the user can login and then he/she could go to the add contact page. High. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go the manage contacts page. 4- Insert a valid contact name and an invalid number. 5- Click submit. An exception about the invalid contact number appears in the Expected Results screen to the new user that he/she should change their contact number and insert a valid contact number. An exception about the invalid contact number appears in the screen to the new user that he/she should change their contact number and insert a valid contact number. Table 2.24 G18 Page 18

22 TC_ID 25 Test Case Name Sign in To make sure that an existing user could sign in and enjoy all Mr. Mobile features. That Mr. Mobile website is working. High. 1- Open Mr. Mobile. 2- Enter a valid username and password. 3- Click sign in. Expected Results The user is redirected to a new homepage where he/she can enjoy all Mr. Mobile features The user is redirected to a new homepage where he/she can enjoy all Mr. Mobile features Table 2.25 G18 Page 19

23 TC_ID 26 Test Case Name Delete account To make sure that deleted accounts is really deleted and the deleted user couldn t login again to Mr. Mobile with the deleted user. That Mr. Mobile website is working and the user could go to delete page through his account. Low. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to edit account page. 4- Click delete account. 5- Confirms account deletion using the password. 6- Try to login to Mr. Mobile using the deleted account. Expected Results The user wouldn t be able to Login to Mr. Mobile using the deleted username. The user wouldn t be able to Login to Mr. Mobile using the deleted username. Table 2.26 G18 Page 20

24 TC_ID 27 Test Case Name Delete account using an invalid password To make sure that user couldn t delete his/her account if they inserted an invalid password. That Mr. Mobile website is working and the user could go to delete page through his account. Low. 1- Go to Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to edit account page. 4- Click delete account. 5- Confirm account deletion using an invalid password. An exception about the invalid password appears in the screen Expected Results to the new user that he/she should retype their password to confirm deletion. An exception about the invalid password appears in the screen to the new user that he/she should retype their password to confirm deletion. Table 2.27 G18 Page 21

25 TC_ID 28 Test Case Name Delete contact To make sure that user could delete his contacts. That Mr. Mobile website is working and the user could go to Manage contacts page through his account. Low. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to manage contacts page. 4- Select a contact. 5- Click delete contact. 6- View contacts list. Expected Results The loaded contacts from the database don t have the deleted contact. The loaded contacts from the database don t have the deleted contact. Table 2.28 G18 Page 22

26 TC_ID 29 Test Case Name Expected Results Edit account information To make sure that user could edit his info after he/she logins to Mr. Mobile. Mr. Mobile website is working and user could login and go to edit account s info page. High. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to edit account page. 4- Edit all required data to be modified. 5- Click submit. 6- Check the user s info after editing. The user s info has changed to the new desired data. The user s info has changed to the new desired data. Table 2.29 G18 Page 23

27 TC_ID 30 Test Case Name Edit account info using an existing username To make sure that when user want to changes his/her username he/she should enter a new username. Mr. Mobile website is working and user could login and go to edit account s info page. High. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to edit account page. 4- Edit all required data to be modified while inserting an existing username. 5- Click submit. An exception should appear on the screen that the new desired Expected Results username already exists and user should change it to a one that doesn t exist in the database. An exception should appear on the screen that the new desired username already exists and user should change it to a one that doesn t exist in the database. Table 2.30 G18 Page 24

28 TC_ID 31 Test Case Name Edit account info with an invalid telephone number To make sure that when user want to changes his/her telephone number then he/she should enter a valid telephone number. Mr. Mobile website is working and user could login and go to edit account s info page. High. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to edit account page. 4- Edit all required data to be modified while inserting an invalid telephone number. 5- Click submit. An exception should appear on the screen that the new desired Expected Results telephone number is invalid and user should change it to a valid one. An exception should appear on the screen that the new desired telephone number is invalid and user should change it to a valid one. Table 2.31 G18 Page 25

29 TC_ID 32 Test Case Name Edit account info with mismatching passwords To make sure that when user want to changes his/her telephone number then he/she should enter a valid telephone number. Mr. Mobile website is working and user could login and go to edit account s info page. High. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to edit account page. 4- Edit all required data to be modified while typing mismatching passwords. 5- Click submit. An exception should appear on the screen that the two Expected Results passwords are mismatching, and user should write a new password. An exception should appear on the screen that the two passwords are mismatching, and user should write a new password. Table 2.32 G18 Page 26

30 TC_ID 33 Test Case Name Edit contact To make sure that user could edit his contact name and number. That Mr. Mobile website is working and the user could go to Manage contacts page through his account. Low. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to manage contacts page. 4- Select a contact to edit. 5- Edit the contact through changing its name or number. 6- Click submit. Expected Results The contact should be edited to the new values. The contact should be edited to the new values. Table 2.33 G18 Page 27

31 TC_ID 34 Test Case Name Edit contact using an existing contact name To make sure that user couldn t change his/her contact name until this name doesn t exist in his/her contacts names. That Mr. Mobile website is working and the user could go to Manage contacts page through his account. Low. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to manage contacts page. 4- Select a contact to edit. 5- Edit the contact through changing its name to an existing contact name. 6- Click submit. Expected Results An exception should appear on the screen that this contact s name already exists in the user s backup. An exception should appear on the screen that this contact s name already exists in the user s backup. Table 2.34 G18 Page 28

32 TC_ID 35 Test Case Name Edit contact with an invalid number To make sure that user couldn t change his/her contact number until this new number is valid. That Mr. Mobile website is working and the user could go to Manage contacts page through his account. Low. 1- Open Mr. Mobile website. 2- Login to Mr. Mobile. 3- Go to manage contacts page. 4- Select a contact to edit. 5- Edit the contact by entering an invalid number. 6- Click submit. Expected Results An exception should appear on the screen that this new contact s number is invalid. An exception should appear on the screen that this new contact s number is invalid. Table 2.35 G18 Page 29

33 Data Testing External Data Testing Web Interface We will test that the data that the user enters in the web forms is a valid data and applicable in our database. We will test that the data going out of our website to other websites (e.g.: Facebook) is valid and can be used by the other website. We will test that the data coming in to our website from other websites is valid and can be used by our website and database Mobile Interface We will test the data that the user needs to backup on his mobile phone to see if it can be backed up on our database or not. We will test if the data entered by the user during logging in and adding other contacts using his mobile phone is valid before sending them on to our web server to save the cost of the redundant web usage Internal Data Testing We will test the validity of the data before it enters the database to avoid any problems that may face us in the database. We will test the encryption of the personal information of all the users along with the usernames and passwords to ensure maximum security of the user s privacy User Testing We will test the easiness of usage of the mobile application by a user that s not familiar with the program, where he should be able to backup the contacts with four clicks or less. We will test the easiness of usage of the website by a user that s not familiar with the interface of the web application, where he should be able to use any of the features of the website in five steps or less. We will test the easiness of the registering process by a user that wishes to sign up to Mr. Mobile in less than three clicks. G18 Page 30

34 Non-functional (Systems Requirements) Testing Performance Testing Merging contacts We will test merging a thousand contacts with the user s contact list successfully without too much loading of the program and within less than two minutes Backing up contacts We will test backing up a thousand contacts successfully without too much loading of the program and within less than five minutes Synchronizing We will test synchronizing a hundred contacts between the mobile contact list and the database contact list successfully in less than one minute Stress loading on website and database We will test stress loading on website and database where there will be a hundred users using the program or the website to backup or retrieve their data on the database successfully and without any failure from the website or the database Quality Testing Correctness We will test whether our functional and non-functional specifications are fully or partially satisfied, and if some of them are not satisfied, we will start an issue about them in the Issue Tracking Tool Efficiency We will test the different resources that the mobile and web application use, and try to bring them to a minimum level. For example, validating the data on the mobile phone to eliminate the redundant connectivity to the internet Flexibility We have designed Mr. Mobile to be very tolerant to change, if we want to add any new feature or remove any useless feature, we will only add or remove a class without any other changes in the code. We will test this by adding a dummy feature to the system then removing it. G18 Page 31

35 Security We will test the system for security where it should ensure the maximum security possible, and we will test the level of encryption for the personal information of the user as well as his username and password Interoperability We have designed Mr. Mobile to be easily integrated with any other system, like facebook, and we will test the integration of Mr. Mobile with the different systems that serves our application Maintainability We will test the maintainability of Mr. Mobile by releasing an alpha version of the application to our friends and family members, where they can locate the different bugs they find, and we will measure the efforts needed to fix those different bugs Portability We will test the portability of the mobile application by trying it on different models of different makes of mobile phones. We will also test the portability of the website by trying it on different web servers that can serve our purpose Reliability We will test the reliability of the system by exposing it to a very painful stress testing until the system reaches its limits or we get bored from trying Usability We will test the usability of the system as mentioned above, by testing the easiness of usage of the web application and the mobile application Interface Testing As mentioned above, we will test the easiness of using the mobile application and the web application, by making a user who is not familiar with the interface use the program and he should be able to use any of the features of the mobile or web application in five steps or less Phases of Testing Customize and complete the Test Phase Chart to reflect the test phases and approach for the project. G18 Page 32

36 Test Phase Chart Test Phases Unit Integration System Acceptance X Phase Objective To test units of code that are considered complete. To ensure that aggregates of units perform accurately together. To ensure that the system performs according to documented requirements and the customer s expectations To ensure that the completed system performs according to documented requirements and the customer s expectations. To Focus Correctness of specific functionality of a unit and its input, outputs, and primary and fault handling. Correctness of the aggregate with regard to its associated requirements. Correctness of the system and that it conforms to stated requirements. Correctness of all functionality of the system. Correct-ness of Test Types/ Subtypes Functional (lowlevel), Data, Performance, Integrity/Securit y, Interface. Functional, Data, Performance, Reliability, Integrity/Securit y, Interface, Usability. Functional, Data, Performance, Reliability, Integrity/Securit y, Interface, Usability. Functional, Data, Performance, Reliability, Integrity/Securit y, Interface, Usability. Staffing Development Team (author of a unit should not be the tester) Test Team, independent of the development team (member of the integration test team should not perform revisions to code he is testing). Test Team, independent of the development team (member of the system test team should not perform revisions to code he is testing). Customers or end users, can be lead by testers independent of the development team (member of the acceptance test team should not perform revisions to code he is testing). G18 Page 33

37 Test Phases Unit Integration System Acceptance X Phase Environment Development. Should be performed in an environment segregated from development and controlled by a group independent of the development team. Should be performed in an environment segregated from development and controlled by a group independent of the development team. Should be performed in an environment segregated from development and controlled by a group independent of the development team Should be identical to the product-ion environment or as close as possible.... Entry Criteria Code complete Test plan approved Unit test procedure and scenarios approved Unit test data approved. Code complete Test plan approved Unit test successful Integration test procedure and scenarios approved Integration test data approved Integration test exit criteria, including allowable errors and functional discrepancies, specified. Code and documentation baselined Test plan approved Integration test successful System test procedure and scenarios approved System test data approved System test exit criteria, including allowable errors and functional discrepancies, specified Unit and Integration test reports complete Requirements Traceability Matrix complete User documentation complete Test Readiness Review minutes complete. Code and documentation baselined Test plan approved Integration test successful Acceptance test procedure and scenarios approved Acceptance test data approved Acceptance test exit criteria, including allowable errors and functional discrepancies, specified Unit, Integration, and System test reports complete. G18 Page 34

38 Test Phases Unit Integration System Acceptance X Phase Suspension Criteria Environment Issues Design rework Development rework Requirements changes. Unit development not complete Unit test not complete, unsuccessful, or inadequate Environment issues Design rework Development rework Requirement changes Defects encountered > X Fault with major feature that prevents significant functionality from being tested. Environment issues Design rework Development rework Requirement changes Defects encountered > X Installation problems Fault with major feature that prevents significant functionality from being tested. Environment issues Design rework Development rework Requirement changes Defects encountered > X Installation problems Fault with major feature that prevents significant functionality from being tested. Exit Criteria Test logs approved Unit test scenarios passed Unit is baselined. Test logs approved Allowable errors and functional discrepancies Allowable errors and functional discrepancies do not exceed thresholds. Test logs approved Allowable errors and functional discrepancies do not exceed thresholds System is baselined Test logs approved Stakeholder acceptance 3. Test Schedule We have agreed-upon the testing plan along with the duration of each component of testing, as follows: 3.1. Component Testing This type of testing is scheduled to take about one day System testing This type of testing is scheduled to take about three days, it is divided into two subcategories: G18 Page 35

39 Integration Testing This type is scheduled to take about two days Release Testing This type is scheduled to take about one day Smoke and Stress Testing These types of testing is scheduled to take the rest of days available before the project delivery day. 4. Test Monitoring and Reporting 4.1. Monitoring 4.2. Reporting 5. References The first milestone we reaches was when we made our first successful build. The second milestone was reached when we added the backup contacts feature. The third milestone was reached when we added the grab facebook contacts feature. We discovered that we were reaching some milestones that we didn t even think of and that indicated a high success rate of implementing. We used the reporting bugs and testing tool available on our SVN server which is established on Google Code and it provides us with all the tools that we needed along the software cycle. Mr. Mobile SRS document. Mr. Mobile SDS document. Dr. Sayed Hemayed lectures notes. G18 Page 36