Test Plan and Cases (TPC) Templateversion 1.0

Test Plan and Cases (TPC) TemplateVersion 1.0

Test Plan and Cases (TPC)

City of Los Angeles

Applicant Resource Center

Team 09

Team members and roles:

Vaibhav Mathur, Project Manager

Preethi Ramesh, Feasibility Analyst

Arijit Dey, Requirements Engineer

Shreyas Devraj, Life Cycle planner

Gaurav Mathur, Builder

Divya Nalam, OCE

Rakesh Mathur, IIV&V

29th November 2013

Version History

Date / Author / Version / Changes made / Rationale
11/29/13 / DN / 1.0 / ●Initial draft of test plan and test cases

Table of Contents

Test Plan and Cases (TPC)

Version History

Table of Contents

Table of Tables

1.Introduction

2.Test Strategy and Preparation

2.1.Hardware preparation

2.2.Software preparation

2.3.Requirements Traceability

3.Test Identification

3.1.TC-1: Email Generation

3.2.TC-2: Reference response submission

3.3.TC-3: Reference response retrieval

3.4.TC-4: Reference status review

3.5.TC-5: Reminder sending to reference

3.6.TC-6: Manager reviews

3.7.TC-7: Assignment information submission

3.8.TC-8: Investigator table update

3.9.TC-9: Language option for references

Table of Tables

Table 1: Requirements Traceability Matrix

Table 2: TC-01-01 Check candidate details update

Table 3: TC-01-02 Check reference details update

Table 4: TC-01-03 Check automatic email generation

Table 5: TC-02-01 Check successful login of the reference

Table 6: TC-02-02 Check prevention of reference form access without passcode

Table 7: TC-02-03 Check submission of reference responses

Table 8: TC-02-04 Prevent response submission if mandatory fields empty

Table 9: TC-02-05 Prevent resubmission of reference responses

Table 10: TC-03-01 Check the retrieval of reference responses

Table 11: TC-04-01 Check retrieval of reference status

Table 12: TC-05-01 Check reminder sending to Reference

Table 13: TC-06-01 Check display of assignments to investigator

Table 14: TC-06-02 Check display of candidate details

Table 15: TC-07-01 Check assignment of candidate

Table 16: TC-08-01 Check Investigator Management Page display

Table 17: TC-08-02 Check addition of investigator

Table 18: TC-08-03 Check deletion of investigator

Table 19: TC-08-04 Check editing of investigator details

Table 20: TC-09-01 Check Spanish version of reference form

Table 21: TC-09-02 Check English version of reference form

1.Introduction

Purpose, scope and focus:

The purpose of testing the ARC application is to ensure that the most important MMFs are implemented precisely. This includes the features of generating email to references, providing for electronic submission of reference responses and review of references. This document covers the test cases for these features in details. It also contains the high level test plan for features such as investigator assignment and language options. These features have not been taken up in the development stage currently.

Type of testing:

The project is currently in development phase and unit testing has been performed for the features that have been developed. The test plan for the test phase has been prepared using the Requirements-test traceability strategy.

2.Test Strategy and Preparation

A combination of inspection and testing is being used for the verification of ARC application development. Peer reviews (inspections) are performed to ensure that the code reflects the UML design and testing is performed to ensure that the features developed have the expected behavior.

The Requirements-test traceability strategy can be used for the testing process. The test cases are mapped to the Capability Goals and the win-conditions corresponding to the MMFs in the Win-book. Hence, the test plans are written for all the MMFs, namely, Automated Email, Investigator Assignment, Reference Letter Completion and Reference Letter Viewing.

Development has been currently performed for the three MMFs, Automated Email, Reference Letter Completion and Reference Letter Viewing.

2.1.Hardware preparation

Ideally, the ARC application needs to be tested on the client server. There are two different types of requests that can be received by the application depending on privilege level of the user:

●Type 1: Requests from the staff of City of LA to access candidate information, assignment information, reference status information, etc.

These requests can only come from workstations in the internal network of the City.

●Type 2: Requests from references to access the reference form and to submit responses.

These requests are sent from workstations that are not in the internal network of the City.

In order to test the above two types of requests, the following hardware are needed:

(i)Server:

Purpose: Running the ARC application.

Preparation:

• The ARC application should be loaded on server.
• The firewall should be configured to block Type 1 requests from workstations in external networks.

(ii) Two Workstations:

Purpose: To send requests to the server.

Preparation: One of the workstations needs to be connected to the intranet of City of LA and the other one should be connected to the Internet.

For the Development phase, testing is being performed on the test system which acts as the server and the workstations.

2.2.Software preparation

The following software preparations are required for testing:

(i)The ARC application:

After loading the application on the client’s server, the web.config should be changed to include the correct server address.

(ii)IIS Server:

The IIS settings on the client’s server need to be updated to include ARC application in the wwwroot directory. The folder where the code will be deployed will be different than the “Inetpub” folder. Also, code-behind pages which contain Application logic will not be deployed for security reasons. Configurations for the Application are created automatically by VS.NET. The Windows server on which the code is deployed must be configured so that the firewall doesn’t block the requests sent by the users.

There will be 2 IIS Servers needed for deployment. One within the firewall which will host the code for the Support Staff, Investigator, Manager and other LA City Personnel. The other IIS Server will need to sit in the DMZ and needs to be accessible over the internet via HTTP. This server will host the Feedback Form application for the Reference to verify and log on with. Both servers will need to be running IIS with ASP.NET 3.5 or above and will need to have access via port 50000 (or another secure port specified by LA CITY IT STAFF) to the DB2 Database.

(iii)Database (DB2):

• The tables in the ARCFinal database need to be exported to the client’s database. This can be done by running DBscript.db.
• All tables except Questions can be populated using an automatic data generation tool like the IBM DB2 Test Database Generator.
• The Questions table can also be populated by a data generation tool but it is more preferable to use a script which generates exactly those questions which are a part of the original questionnaire (Reference form).

(iv)Data Studio 4.1.0.0/ RazorSQL:

These are the database management tools that can be used to verify the database updates.

In the development phase, testing is being performed on small datasets using Chrome as the browser. Data Studio is being used for managing the tables in the database. Currently no auto-generation tools are being used.

2.3.Requirements Traceability

Table 1: Requirements Traceability Matrix

Requirements/ Capability goals / Verification Type / Test Case ID (if applicable)
WC-2395 / Testing / TC-1: Email generation
WC-2394 / Testing / TC-2: Reference response submission
WC-2393 / Testing / TC-3: Reference response retrieval
WC-2393 / Testing / TC-4: Reference status review – investigator
WC-2404 / Testing / TC-5: Reminder sending to reference
WC-2454, WC-2583 / Inspection / TC-6: Manager reviews
WC-2586 / Inspection / TC-7: Assignment information submission
WC-2453 / Inspection / TC-8: Investigator table update
OC-8: Language options / Inspection / TC-9: Language option for references

3.Test Identification

3.1.TC-1: Email Generation

This test case is meant to test the proper submission of candidate information to the database and email generation. It maps to the MMF, Automated Email.

3.1.1.Test Level

This test is at the software item level and is meant to test the Support staff module.

3.1.2.Test Class

This is a functionality test to check if the support staff can successfully enter the candidate details and corresponding reference details to the database and generate the first set of emails to the references requesting for responses. It also covers the erroneous tests of the support staff entering incorrect data.

3.1.3.Test Completion Criteria

The Email Generation test is considered complete when:

-When the candidate details are successfully added to the Candidate table.

-The reference details are added to the Reference Table.

-Emails are sent to the references requesting them to submit the response forms

-Email contains the link with the reference’s passcode encrypted.

3.1.4.Test Cases

Table 2: TC-01-01 Check candidate details update

Test Case Number / TC-01-01 Check candidate details update
Test Item / The Support staff module is tested by this case. The feature that is tested is the provision for support staff to add new candidate details to the database.
Test Priority / M
Pre-conditions / The user should be logged in as support staff
Post-conditions / The candidate details should be updated in the Candidate Table.
Input Specifications / -Candidate first name, last name and last four digits of SSN are should be entered in the support staff homepage.
-Submit button needs to be clicked.
Expected Output Specifications / -The candidate details submitted will appear in non-editable form on the screen.
-Provision for adding more references to the candidate will be displayed on the screen.
Pass/Fail Criteria / Pass criteria:
-The candidate details are added to the candidate table if not already present.
Fail criteria:
-Database update fails and the new candidate details are not added to the Candidate table.
Assumptions and Constraints / The user submits only after filling all the fields on the home page.
Dependencies
Traceability / WC-2395

Table 3: TC-01-02 Check reference details update

Test Case Number / TC-01-02 Check reference details update
Test Item / The Support Staff module is tested in this test case. The feature that is tested is the provision for the support staff to add references to a candidate.
Test Priority / M
Pre-conditions / -The user should be logged in as support staff.
-The candidate details should have been already added and fetched.
Post-conditions / -The reference details are added to the Reference Table in the database. The status of reference should be “response not received”.
Input Specifications / -The user needs to specify the reference name and email ID.
-“Add reference” button needs to be clicked.
Expected Output Specifications / -The newly added reference details will be displayed in non-editable format with options for “Delete” and “Edit”
-Provision for adding new reference will be displayed.
Pass/Fail Criteria / Pass criteria:
The reference table is updated and the status of the reference should show that the response is not yet received.
Assumptions and Constraints / The reference details entered are correct and reference email ID is valid.
Dependencies / TC-01-01
Traceability / WC-2395

Table 4: TC-01-03 Check automatic email generation

Test Case Number / TC-01-03 Check automatic email generation
Test Item / The Support staff module is tested by this case. The feature that is tested is the automatic generation of email when the
Test Priority / M
Pre-conditions / -The user should be logged in as support staff
-Candidate and reference details should have been added to the database.
Post-conditions / -‘Last email sent’ field is updated in the Email table.
Input Specifications / -The candidate details should be added or retrieved.
-“Send email” button for the respective reference needs to be clicked.
Expected Output Specifications / -Pop up to indicate if email has been sent is displayed.
-Email is received by the reference.
Pass/Fail Criteria / Pass criteria:
-Database gets successfully updated with the email-sent date and email count.
-The reference receives the request email.
Fail criteria:
-The reference does not get the request email.
Assumptions and Constraints / The user enters valid email ID for the reference.
Dependencies / TC-01-01, TC-01-02
Traceability / WC-2395

3.2.TC-2: Reference response submission

This test is meant for testing if the references will be able to submit their response through the online system. This maps to the MMF, Reference Letter Completion.

3.2.1.Test Level

This test is at the software item level and is meant to test the Reference module.

3.2.2.Test Class

This is a functionality test which is meant to ensure that the reference is able access the reference form with the help of the encrypted link in the email, complete the reference form online and submit it. It also includes erroneous tests to check that the reference form cannot be accessed without the passcode, the reference responses cannot be submitted more than once and the reference form is not submitted without being completed filled.

3.2.3.Test Completion Criteria

The Reference Response Submission test case is considered complete when:

-The reference successfully submits the response.

-The reference is unable to access the reference form again (Reference table should be updated by clearing off the Passcode field for the reference).

-The Response table is updated with the response-received date.

-The Response-Text table is updated with the responses submitted.

3.2.4.Test Cases

Table 5: TC-02-01 Check successful login of the reference

Test Case Number / TC-02-01 Check successful login of the reference
Test Item / The Reference module is tested in the case. The feature that is tested is the provision for reference to use the link sent in the email to access the reference form.
Test Priority / M
Pre-conditions / -The user should have received the email with link.
Post-conditions / -The reference form is displayed to the user.
Input Specifications / -The user system should be in an external network.
-The user clicks on the link to access the reference form.
Expected Output Specifications / -The reference form is displayed to the user.
Pass/Fail Criteria / Pass criteria:
The reference form is displayed to the user.
Assumptions and Constraints / The link has been accessed by the actual reference.
Dependencies / TC-01-01, TC-01-02, TC-01-03
Traceability / WC-2394

Table 6: TC-02-02 Check prevention of reference form access without passcode

Test Case Number / TC-02-02 Check prevention of reference form access without passcode
Test Item / The Reference module is tested in the case. In order to ensure that the reference form is accessible only to the reference who have received request email, the link is encrypted with a passcode. This passcode must match with the user email address to access the reference form. This feature is tested here.
Test Priority / M
Pre-conditions / Null
Post-conditions / -No updates to database.
Input Specifications / -The user needs to give the link to the reference form in the browser.
Expected Output Specifications / -Error message is displayed to the user.
Pass/Fail Criteria / Pass criteria:
User is denied access.
Assumptions and Constraints / The user knows the link to the reference form.
Dependencies
Traceability / WC-2394

Table 7: TC-02-03 Check submission of reference responses

Test Case Number / TC-02-03 Check submission of reference responses
Test Item / The Reference module is tested in this case. The feature that is tested here is the submission of reference responses online.
Test Priority / M
Pre-conditions / -The reference should have got the email with the encrypted link to the reference form.
Post-conditions / -The Response table should be updated with the response received date.
-The ResponseDetail should be updated with the responses of the reference.
-The Reference table should be updated by deleting the passcode for the reference.
Input Specifications / -The user needs to click on the encrypted link in the email.
-The user should choose the language option.
-The user needs to fill in all the answers to the questions in the reference form and click on the Submit button.
Expected Output Specifications / Message is displayed to the user mentioning that the responses have been submitted successfully.
Pass/Fail Criteria / Pass criteria:
-The responses are stored in the database.
Assumptions and Constraints / -The language option works without any bugs.
-The reference has filled all the mandatory fields.
Dependencies / TC-02-01
Traceability / WC-2394

Table 8: TC-02-04 Prevent response submission if mandatory fields empty

Test Case Number / TC-02-04 Prevent response submission if mandatory fields empty
Test Item / The Reference module is tested in this case. The responses should not be submitted unless all the mandatory fields are filled up.
Test Priority / M
Pre-conditions / -The reference should have got the email with the encrypted link to the reference form.
Post-conditions / -No change in the database.
Input Specifications / -The user should click on the submit button without filling up some of the mandatory fields.
Expected Output Specifications / Error message should be displayed to the user.
Pass/Fail Criteria / Pass criteria:
The responses should not be submitted and the user should be allowed to fill the form completely and then submit.
Assumptions and Constraints
Dependencies / TC-02-01
Traceability / WC-2394

Table 9: TC-02-05 Prevent resubmission of reference responses

Test Case Number / TC-02-05 Prevent resubmission of reference responses
Test Item / The Reference module is tested in this case. Once the reference submits the responses, he/she should not be allowed to access the reference form again.
Test Priority / M
Pre-conditions / -The reference should have already submitted the response.
Post-conditions / -No change in the database.
Input Specifications / -The user should click on the link to the reference form after submission of the response.
Expected Output Specifications / Error message should be displayed to the user.
Pass/Fail Criteria / Pass criteria:
The user should be denied access to the reference form.
Assumptions and Constraints / <to be updated with investigator assignment test case>
Dependencies / TC-02-01
Traceability / WC-2394

3.3.TC-3: Reference response retrieval

This test is meant for checking if the investigators are able to retrieve and review the responses submitted by the references. This maps to the MMF, Reference Letter Viewing.