240 likes | 442 Views
Zebraware. Zebraware Team. Bob – President Lead web app developer Joe – VP Librarian Mark – VP Lead client app developer. Outline. Acceptance Test System Test Plan Questions. Acceptance Test Plan. Acceptance Test.
E N D
Zebraware Team • Bob – President • Lead web app developer • Joe – VP • Librarian • Mark – VP • Lead client app developer
Outline • Acceptance Test • System Test Plan • Questions
Acceptance Test • Purpose – Demonstrate all features specified in the Requirements Document. • Customer will sign off on each feature.
Test Case #1 • Search for flight from client application • Purpose: Demonstrate how to find a flight from within the client application. • Expected Result: Flights matching the specified search criteria will be displayed.
Test Case #2 • Search for pilot from client application • Purpose: Demonstrate how to find a pilot from within the client application. • Expected Result: Pilots matching the specified search criteria will be displayed.
Test Case #3 • Search for customer from client application • Purpose: Demonstrate how to find a customer from within the client application. • Expected Result: Customers matching the specified search criteria will be displayed.
Test Case #4 • View pilot information from client application • Purpose: Demonstrate how to view a pilot’s information from within the client application. • Expected Result: The specified pilot’s information will be displayed.
Test Case #5 • View customer information from within client application • Purpose: Demonstrate how to view a customer’s information from within the client application. • Expected Result: The specified customer’s information will be displayed.
Test Case #6 • View flight information from within client application • Purpose: Demonstrate how to view a specified flight’s information from within the client application. • Expected Result: The flight information will be displayed.
Test Case #7 • View aircraft information from within client application • Purpose: Demonstrate how to view aircraft information from within the client application. • Expected Result: The specified aircraft’s information will be displayed.
Test Case #8 • View flight information from the web app • Purpose: Demonstrate how to view a flight’s information within the web app. • Expected Result: The specified flight’s information will be displayed.
Test Case #9 • Login to the web application • Purpose: Demonstrate how to login to the web application. • Expected Result: User gets logged in to the web site
Test Case #10 • View customer information from the web app • Purpose: Demonstrate how to view a customer’s information when logged in to the web app. • Expected Result: The logged in customer’s information will be displayed.
System Test Plan • Purpose • Ensure that all functional and non-functional requirements specified in the Requirements Document are upheld. • Ensure that the software developed by Zebraware is of the highest quality to replace the existing system. • Ensure that the system will operate in Dodo Airline’s environment.
Unit Testing • 1.2.1.2 – Add Customer • Test cases:
Component Testing • 2.1.1 – Purchase Ticket • Test cases:
Transaction Flow Testing • 2.2.6.3 – Update Customer Profile • Step 1: Select the customer search tab • Step 2: Select Customer to updateEnter enough search criteria to find the customer to update, and select that customer. • Step 3: Open the popup to edit the customer informationClick the magnifying glass to the left of the customer entry to bring up the customer’s information. • Step 4: Edit Customer InformationMake any necessary changes to the customer’s information. • Step 5: Save ChangesClick ‘Apply’ to save the changes to the database.
Regression Test Policy • Guidelines for Zebraware developers: • Fixed bugs must be tested promptly • Watch for side effects of fixes • A regression test must be written for each bug fixed • Archive tests that the program consistently passes for future use • Trace the effects of the changes on program memory
Performance Test • Test Case: Perform 1000 customer searches sequentially. • Objective: Test the reliability of the database • Expected Results: Each search will have results returned in under 3 seconds, and the results returned each time will be identical.
Backup and Recovery Test • Test cases: