actual test case document

TEST CASE DOCUMENT

CTODS 1.0 Compliance Test Cases for

LSD 1.2

Author: Aynur Abdurazik

Current Owner: Aynur Abdurazik

Creation Date: 10/14/09

Last Updated: 10/14/09

Version: 1.0

Status: Draft/In Process/Approved

1. Document Control

1.1 Change History

Name Position Date Document Version

Description of Change Including Section of Script

Aynur Abdurazik LSD Compliance Test Coordinator

10/14/09 1.0 First Draft

1.2 Review and Approval History

Reviewer Name Position Document Review Status (Approved/Not Approved)

Date Reviewed

Comments Incorporated(Yes/No)

1.3 Document References

Name Type of Reference Document Location

2. Table of Contents

1. DOCUMENT CONTROL.................................................................................2

1.1 CHANGE HISTORY...........................................................................................................................................21.2 REVIEW AND APPROVAL HISTORY..................................................................................................................21.3 DOCUMENT REFERENCES................................................................................................................................2

2. TABLE OF CONTENTS..................................................................................3

3. FUNCTIONAL TEST......................................................................................4

3.1 INTRODUCTION/OVERALL TEST OBJECTIVES..................................................................................................4

4. LIMITATIONS/DEPENDENCIES/REQUIREMENTS..............................................5

4.1 TEST CASE LIMITATIONS.................................................................................................................................54.2 TEST CASE DEPENDENCIES / ASSUMPTIONS....................................................................................................54.3 DEFAULT SETUP..............................................................................................................................................5

5. TEST CASES...............................................................................................6

5.1 TEST CASES FOR CTODS WEB.......................................................................................................................65.1.1 Configure CTODS with UPT..................................................................................................................65.1.2 Log in CTODS Application.....................................................................................................................75.1.3 Search CTODS Data...............................................................................................................................7

5.2 TEST CASES FOR CTODS API AND GRID SERVICE........................................................................................8

Appendix:..........................................................................................................9

3. Functional Test

3.1 Introduction/Overall Test Objectives

This test case is intended to verify that the following functionality is working successfully:

CTODS web application functions correctly in LSD 1.2 compliance tier CTODS API works correctly in LSD 1.2 compliance tier. CTODS grid service is available in LSD 1.2 compliance tier.

4. Limitations/Dependencies/Requirements

4.1 Test Case Limitations

The test cases for CTODS web application are selected to perform sanity check on COTDS web application. Therefore, this test is not a full regression testing of CTODS features.

4.2 Test Case Dependencies / Assumptions

CTODS web application uses UPT to provision users and data. CTODS database has data available for test purposes.

4.3 Default Setup

CTODS web application default user account: lsdtestuser1/password

5. Test Cases

The following test cases are executed on LSD linux 64 bit machine, cbapp-s1002.

5.1 Test Cases for CTODS Web Application

5.1.1 Configure CTODS with UPT

Req. ID

Step Num

Description Step / Action Expected Results Actual Results (if different)

Pass/Fail Comments/ Issue ID

01. Go to UPT web application

Go to htpp://cbapp-s1002.nci.nih.gov:39080/uptlogin

CSM UPT login page is displayed Pass

02. Login as superadmin

Enter “superadmin” for username, “changeme” for password, and “csmupt” for application name

UPT superadmin page is displayed

Pass

03. Register CTODS in UPT

1. Go to “Application” Tab2. Click on “Create new Application”

link3. Enter correct values for CTODS

application in the displayed form fields

4. Click “Create” 5. Click “Test Connection”

CTODS application is registered in UPT with correct DB information for COTDS; Database connection test passes.

Pass

04. Create an admin for CTODS

1. Go to “User” Tab2. Click on “Create New User” Link3. Enter valid values for the new user

form (i.e., usrname: ctodsadmin, password: ctodsadmin)

4. Go to “Application” Tab5. Click on the “Select Existing

Application” Link6. Search for CTODS application7. Assign ctodsadmin as the admin for

CTODS (See UPT manual for details of this procedure)

Newly created ctodsadmin user is assigned as an admin to CTODS application.

Pass

05. Superadmin logout

Click the “Log Out” Tab Superadmin loggeg out from UPT;UPT login page is displayed

Pass

06. Log in to CTODS application as CTODS admin

1. Enter “ctodsadmin” in username 2. Enter “ctodsadmin” in password; 3. Enter “ctods” in the application

field;4. Click “Submit”

UPT displays CTODS application provisioning page

pass

07. Create CTODS users

Create users with different privileges; See details from UPT manual.

Pass

End

5.1.2 Log in CTODS Application

Req. ID

Step Num



01. Go to CTODS web application

Go to http://cbapp-s1002.nci.nih.gov:44210/CTODSViewer/

CTODS web application login page is displayed

Pass

02. Login as CTODS user

1. Enter “lsdtestuser1” in the Login Id field

2. Enter “Password” in the Password field

User is in the CTODS application ready to explore CTODS data

Pass

END

5.1.3 Privileged User Explore/Search CTODS Data

Req. ID

Step Num






Pass


1. Enter “lsdtestuser1” in the Login Id field

2. Enter “Password” in the Password field


Pass

03. Explore Adverse Events

1. Go the “Adverse Event” tab2. Click “Submit”

Complete list of Adverse Events are presented on the page

Pass

04. Explore Protocols

1. Go the “Protocol” tab2. Click “Submit”

Complete list of Protocols are presented on the page

Pass

END

5.1.4 Non-Privileged User Explore/Search CTODS Data

Req. ID

Step Num






Pass


3. Enter “ctods_qa1” in the Login Id field

4. Enter “123” in the Password field


Pass

03. Explore Adverse Events

3. Go the “Adverse Event” tab4. Click “Submit”

Adverse Events are NOT presented on the page

Pass The error message was not descriptive. See GF # 23919

04. Explore Protocols

3. Go the “Protocol” tab4. Click “Submit”

Protocols are NOT presented on the page

Pass

END

5.2 Test Cases for CTODS API and Grid Service

To run the api and grid unit tests against a deployed instance of CTODS:

1) Check out CTODS software from https://gforge.nci.nih.gov/svnroot/cactus/ctods2) Go to software/ctods-api directory3) Set the jboss.url property in build.properties

a)There are three jboss servers to test: i) http://cbapp-s1002.nci.nih.gov:44210/ctods/http/remoteService ii) http://cbapp-s1003.nci.nih.gov:44210/ctods/http/remoteService iii) http://cbwapp-p1001.nci.nih.gov:44210/ctods/http/remoteService

Therefore the following steps should be repeated with each JBoss URL.4) Add a dummy password to build.properties.default5) Run "ant build-ctods"6) Run "ant test", you will be prompted for a user/password. lsdtestuser1/password will work if instance was created using lsd installers.7) Confirm that the build finished successfully.8) Change to the /grid directory.9) Set the ctods-grid.uri property in build.properties.

a)Again, there are three CTODS grid services residing on three JBosses:i) http://cbapp-s1002.nci.nih.gov:44210/wsrf/services/cagrid/Ctods ii) http://cbapp-s1003.nci.nih.gov:44210/wsrf/services/cagrid/Ctods iii) http://cbwapp-p1001.nci.nih.gov:44210/wsrf/services/cagrid/Ctods

Each ctods-grid.uri should match the jboss.url property specified in step 3).10) Run "ant test"11) Confirm that the build finished successfully and that the file myResults.xml was created.

(http://gforge.nci.nih.gov/svnroot/cactus/ctods/software/ctods-api/remote%20unit%20tests%20readme.txt )

http://gforge.nci.nih.gov/svnroot/cactus/ctods/software/ctods-api/remote%20unit%20tests%20readme.txt

http://cbwapp-p1001.nci.nih.gov:44210/wsrf/services/cagrid/Ctods

http://cbapp-s1003.nci.nih.gov:44210/wsrf/services/cagrid/Ctods

http://cbapp-s1002.nci.nih.gov:44210/wsrf/services/cagrid/Ctods

http://cbwapp-p1001.nci.nih.gov:44210/ctods/http/remoteService

http://cbapp-s1003.nci.nih.gov:44210/ctods/http/remoteService

http://cbapp-s1002.nci.nih.gov:44210/ctods/http/remoteService

https://gforge.nci.nih.gov/svnroot/cactus/ctods

Appendix:

actual test case document

Education