Presentation is loading. Please wait.

Presentation is loading. Please wait.

Senior Design – Acceptance Test Plan Review The goal is to: define the criteria for approving the application. Tightly coupled to the Requirements document.

Similar presentations


Presentation on theme: "Senior Design – Acceptance Test Plan Review The goal is to: define the criteria for approving the application. Tightly coupled to the Requirements document."— Presentation transcript:

1 Senior Design – Acceptance Test Plan Review The goal is to: define the criteria for approving the application. Tightly coupled to the Requirements document. Tightly coupled to the Requirements document. Should be traceable to the requirements document. Should be traceable to the requirements document. Acceptance testing generally involves running a suite of tests on the completed system. Each individual test, known as a case, exercises a particular operating condition of the user's environment or feature of the system, and will result in a pass or fail, or boolean, outcome. There is generally no degree of success or failure. The test environment is usually designed to be identical, or as close as possible, to the anticipated user's environment, including extremes of such. These test cases must each be accompanied by test case input data or a formal description of the operational activities (or both) to be performed— intended to thoroughly exercise the specific case—and a formal description of the expected results. boolean Acceptance Tests/Criteria (in Agile Software Development) are usually created by business customers and expressed in a business domain language. These are high level tests to test the completeness of a user story or stories 'played' during any sprint/iteration. These tests are created ideally through collaboration between business customers, business analysts, testers and developers, however the business customers (product owners) are the primary owners of these tests. As the user stories pass their acceptance criteria, the business owners can be sure of the fact that the developers are progressing in the right direction about how the application was envisaged to work and so it's essential that these tests include both business logic tests as well as UI validation elements (if need be). Agile Software Developmentbusiness domain languageuser storyAgile Software Developmentbusiness domain languageuser story

2 Senior Design – Acceptance Test Plan Review WHAT’S INCLUDED?  Introduction  Test Approach  Test Assumptions and Exclusions  Entry and Exit Criteria  Testing Participants  Test Cases

3 Senior Design – Acceptance Test Plan Review INTRODUCTION  Background  Structure of the Document  References  Glossary

4 Senior Design – Acceptance Test Plan Review INTRODUCTIONBackground: This document provide the plan for completing the testing activities required for the Acceptance Test Plan of VODKA. VODKA is a tool to manage the financial accounts of student organizations within a school or university. It is described in greater detail in the Software Requirements Specification for VODKA.

5 Senior Design – Acceptance Test Plan Review INTRODUCTION – Structure of the Document: Section 2 - Describes the overall approach to the Acceptance Test Plan process Section 2 - Describes the overall approach to the Acceptance Test Plan process Section 3 - Describes in more detail individual issues covered or not covered by the Acceptance Test Plan process Section 3 - Describes in more detail individual issues covered or not covered by the Acceptance Test Plan process Section 4 - Describes the criteria which have to be satisfied for the Acceptance Test Plan project Section 4 - Describes the criteria which have to be satisfied for the Acceptance Test Plan project Section 5 - Describes the roles and responsibilities of the staff members involved in the Acceptance Test Plan project Section 5 - Describes the roles and responsibilities of the staff members involved in the Acceptance Test Plan project Section 6 - Describes the test cases used during the Acceptance Test Plan. Section 6 - Describes the test cases used during the Acceptance Test Plan.

6 Senior Design – Acceptance Test Plan Review INTRODUCTION – References: Software Requirements Specification for VODKA Software Requirements Specification for VODKA

7 Senior Design – Acceptance Test Plan Review INTRODUCTION – Glossary: Test Team Leader - The person in charge of all the testers. Test Team Leader - The person in charge of all the testers. Project Leader - The person in charge of the whole project. Project Leader - The person in charge of the whole project. Client's Representatives - Client's Representatives are people who overlook the Acceptance Test Plan execution on behalf of the customers Client's Representatives - Client's Representatives are people who overlook the Acceptance Test Plan execution on behalf of the customers Software Requirements Specification - A Software Requirements Specification is a document which describes the behavior of a system. Software Requirements Specification - A Software Requirements Specification is a document which describes the behavior of a system. Functional Requirements - Functional Requirements define the internal workings of the software. Functional Requirements - Functional Requirements define the internal workings of the software. Unit Tests - A procedure in the software to validate that individual modules and other units of source code are working properly Unit Tests - A procedure in the software to validate that individual modules and other units of source code are working properly...

8 Senior Design – Acceptance Test Plan Review TEST APPROACH AND CONSTRAINTS Introduction This section describes the overall approach, particular techniques and testing tools which will be used during the Acceptance Test Plan of the VODKA and any constraints that may apply. Test Objectives The Acceptance Test Plan process will prompt the client to evaluate VODKA and verify whether it performs in accordance with the client's requirements, listed in the Software Requirements Specification. Test Structure The Acceptance Test Plan will consist of a subset of test cases and methods, previously utilized in the Unit Tests, Integration Test and System Test conducted on the VODKA. The test cases will be carefully selected and agreed upon by both the developer and the client, and will allow for the most adequate verification of the functional requirements of the VODKA, as listed in the Software Requirements Document, without the extensiveness of the full-scale System Test. It is essential that all appropriate Unit Tests, Integration Test and the System Test were successfully performed for VODKA prior to the Acceptance Test Plan and their results were reported and presented to the client.

9 Senior Design – Acceptance Test Plan Review TEST ASSUMPTIONS AND EXCLUSIONS  Introduction  Test Objectives  Test Structure

10 Senior Design – Acceptance Test Plan Review TEST ASSUMPTIONS AND EXCLUSIONS Introduction This section provides greater details about what issues and features of VODKA will be covered by Acceptance Test Plan process, and what issues and features of VODKA will not be covered Assumptions It is assumed that all issues covered by the Acceptance Test Plan were also previously addressed by the Unit Tests, Integration Test and System Test of VODKA. The Acceptance Test Plan will cover: The functional requirements of the system listed in the Software Requirements Specification The functional requirements of the system listed in the Software Requirements Specification Usability of the system Usability of the system Consistency of the user related system documentation Consistency of the user related system documentation

11 Senior Design – Acceptance Test Plan Review TEST ASSUMPTIONS AND EXCLUSIONS Exclusions It is assumed that all issues not covered by the Acceptance Test Plan were previously addressed by Unit Tests, Integration Tests and System Tests of VODKA The Acceptance Test Plan will not cover: The non-functional requirements of the system (except the aforementioned Usability) listed in the Software Requirements Specification The non-functional requirements of the system (except the aforementioned Usability) listed in the Software Requirements Specification Structural integrity of the source code. Structural integrity of the source code.

12 Senior Design – Acceptance Test Plan Review ENRTY AND EXIT CRITERIA  Introduction  Entry Criteria  Exit Criteria

13 Senior Design – Acceptance Test Plan Review TEST ASSUMPTIONS AND EXCLUSIONS Introduction This section lists the criteria which must be satisfied in order for the Acceptance Test Plan to begin, as well as the criteria which must be satisfied in order for the Acceptance Test Plan to stop. Entry Criteria The Acceptance Test Plan can be initiated after the following preconditions are met: VODKA has successfully undergone Unit Tests, Integration Test and System Test. VODKA has successfully undergone Unit Tests, Integration Test and System Test. The testing environment which satisfies the System Requirements of Software Requirements Specification has been setup and inspected by the client's representative The testing environment which satisfies the System Requirements of Software Requirements Specification has been setup and inspected by the client's representative A copy of the latest version of the Software Requirements Specification has been received A copy of the latest version of the Software Requirements Specification has been received A copy of the latest version of the user-related documentation has been received A copy of the latest version of the user-related documentation has been received The latest released version of VODKA has been appropriately resourced. The latest released version of VODKA has been appropriately resourced. A consent of the Project Leader has been obtained. A consent of the Project Leader has been obtained. A consent of the Client has been obtained. A consent of the Client has been obtained. A consent of the Test Team Leader has been obtained. A consent of the Test Team Leader has been obtained.

14 Senior Design – Acceptance Test Plan Review TEST ASSUMPTIONS AND EXCLUSIONS Exit Criteria The Acceptance Test Plan should be halted after either of the following: All Priority 1 requirements were tested without any deviation from expected behavior. (Success) All Priority 1 requirements were tested without any deviation from expected behavior. (Success) At least one Priority 1 requirement deviated from the documented specification. (Failure) At least one Priority 1 requirement deviated from the documented specification. (Failure) By mutual agreement between Client's Representative and the Tester, in which both parties' supervisors should be notified and the Acceptance Test Plan should be rescheduled for a later date. (Failure) By mutual agreement between Client's Representative and the Tester, in which both parties' supervisors should be notified and the Acceptance Test Plan should be rescheduled for a later date. (Failure)

15 Senior Design – Acceptance Test Plan Review TESTING PARTICIPANTS  Introduction  Roles and Responsibilities  Training Requirements  Problem Reporting  Progress Reporting

16 Senior Design – Acceptance Test Plan Review TESTING PARTICIPANTS Introduction This section describes the roles and responsibilities of the staff members involved in the Acceptance Test Plan, as well as the procedure of reporting the test results and any problems that came up during testing. Roles and Responsibilities For the Acceptance Test Plan, the following roles were assumed by the following people: Test Team Leader: Archit Baweja Test Team Leader: Archit Baweja Client's Representative: A person in charge from the client's side who will overview the testing process. Client's Representative: A person in charge from the client's side who will overview the testing process. Tester: A person who will execute the use case tests. Tester: A person who will execute the use case tests.

17 Senior Design – Acceptance Test Plan Review TESTING PARTICIPANTS Training Requirements All parties involved in the Acceptance Test Plan should be familiar with the user interface of VODKA, as well as with the system documentation and the Software Requirements Specification. Problem Reporting Any problem pointed out by either the Client's Representative or the Tester must be documented and reported to the Test Team Leader. Later the problem report will be submitted to the project Leader, and addressed during a periodic or urgent staff meeting depending on the severity of the problems. Progress Reporting The Acceptance Test Plan Report will be compiled once, after testing process is finished by the Test Team Leader and submitted to the Project Leader.

18 Senior Design – Acceptance Test Plan Review TEST CASES  Introduction  Test Cases for All Users  Test Cases for Specific Users

19 Senior Design – Acceptance Test Plan Review TEST CASES Introduction The test cases are distributed in sections covering functionality elements and use cases in the Software Requirements Specification. Each of the following test cases is in the format: Name - The name of the test case Name - The name of the test case Preconditions - Conditions needed to initiate the test case Preconditions - Conditions needed to initiate the test case Actions - The actions expected form a tester Actions - The actions expected form a tester Post conditions - The expected outcome of the test case Post conditions - The expected outcome of the test case

20 Senior Design – Acceptance Test Plan Review TEST CASES Test Cases for all Users The following test cases are for all user accounts. 6.2.1 – Logging In PreconditionsThe user has a web browser opened visiting the VODKA web page ActionsThe tester enters his username and password in the appropriate fields and submits for verification. Post conditionsThe tester is logged in to the system if the verification is successful or The tester is not logged in to the system if the verification is not successful.

21 Senior Design – Acceptance Test Plan Review TEST CASES Test Cases for all Users The following test cases are for all user accounts. 6.2.1 – Logging In What is missing? PreconditionsThe user has a web browser opened visiting the VODKA web page ActionsThe tester enters his username and password in the appropriate fields and submits for verification. Post conditionsThe tester is logged in to the system if the verification is successful or The tester is not logged in to the system if the verification is not successful.

22 Senior Design – Acceptance Test Plan Review TEST CASES Test Cases for all Users The following test cases are for all user accounts. 6.2.2 – Accounts Information PreconditionsThe user has logged into the VODKA system ActionsNone Post conditionsThe tester is presented with the Accounts Summary page

23 Senior Design – Acceptance Test Plan Review TEST CASES Test Cases for all Users The following test cases are for all user accounts. 6.2.3 – Accounts Transitions Summary PreconditionsThe user has logged into the VODKA system ActionsNone Post conditionsThe tester is presented with the Accounts Summary page

24 Senior Design – Acceptance Test Plan Review TEST CASES Test Cases for all Users The following test cases are for all user accounts. 6.2.4 – Transaction Creation PreconditionsThe tester is at the Account Transactions Summary page. ActionsThe tester selects the "Create Transaction" option. Post conditionsThe tester is presented the Create Transaction page. PreconditionsThe tester is at the Create Transaction page. ActionsThe tester enters in all the details for a transaction. Then clicks Save. Post conditionsThe transaction is created.

25 Senior Design – Acceptance Test Plan Review TEST CASES 6.2.5 – Transaction Modification PreconditionsThe tester is at the Account Transactions Summary page. ActionsThe tester selects the "Change Transaction" button next to a transaction. Post conditionsThe tester is presented the Change Transaction page. PreconditionsThe tester is at the Change Transaction page. ActionsThe tester enters in all the new information for the transaction. Then clicks Change. Post conditionsThe transaction is modified.


Download ppt "Senior Design – Acceptance Test Plan Review The goal is to: define the criteria for approving the application. Tightly coupled to the Requirements document."

Similar presentations


Ads by Google