TEST CASE DOCUMENT

CTODS 1.0 Compliance Test Cases for

LSD 1.2
Author: Aynur Abdurazik
Current Owner: Aynur Abdurazik
Cr...
1.

Document Control

1.1

Change History

Name

Position

Aynur Abdurazik

1.2

Name

LSD Compliance Test
Coordinator

Do...
2.

Table of Contents

1. DOCUMENT CONTROL...................................................................................
Functional Test

2.1

Introduction/Overall Test Objectives
This test case is intended to verify that the following functio...
3.

Limitations/Dependencies/Requirements

3.1

Test Case Limitations
•

3.2

The test cases for CTODS web application are...
4.

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

4.1

Test Cases for CTODS ...
4.1.2
Req.
ID

Log in CTODS Application

Step
Num
1.
2.

Description
Go to CTODS
web application
Login as CTODS
user

Step...
Req.
ID

4.2

Step
Num
END

Description

Step / Action

Expected Results

Actual Results (if
different)

Pass/Fail

Commen...
Appendix:

Page 9
Appendix:

Page 9
Upcoming SlideShare
Loading in …5
×

Actual test case document

2,208 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,208
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
43
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Actual test case document

  1. 1. 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 Page 1
  2. 2. 1. Document Control 1.1 Change History Name Position Aynur Abdurazik 1.2 Name LSD Compliance Test Coordinator Document Version 10/14/09 1.0 Description of Change Including Section of Script First Draft Review and Approval History Reviewer Name 1.3 Date Position Document Review Status (Approved/Not Approved) Date Reviewed Comments Incorporated(Yes/No) Document References Type of Reference Document Location Page 2
  3. 3. 2. Table of Contents 1. DOCUMENT CONTROL..........................................................................................2 1.1 CHANGE HISTORY.................................................................................................................................................2 1.2 REVIEW AND APPROVAL HISTORY........................................................................................................................2 1.3 DOCUMENT REFERENCES .....................................................................................................................................2 2. TABLE OF CONTENTS...........................................................................................3 FUNCTIONAL TEST..................................................................................................4 2.1 INTRODUCTION/OVERALL TEST OBJECTIVES........................................................................................................4 3. LIMITATIONS/DEPENDENCIES/REQUIREMENTS.................................................5 3.1 TEST CASE LIMITATIONS.......................................................................................................................................5 3.2 TEST CASE DEPENDENCIES / ASSUMPTIONS..........................................................................................................5 3.3 DEFAULT SETUP ...................................................................................................................................................5 4. TEST CASES ........................................................................................................6 4.1 TEST CASES FOR CTODS WEB APPLICATION .....................................................................................................6 4.1.1 Configure CTODS with UPT.........................................................................................................................6 4.1.2 Log in CTODS Application............................................................................................................................7 4.1.3 Privileged User Explore/Search CTODS Data.............................................................................................7 4.1.4 Non-Privileged User Explore/Search CTODS Data.....................................................................................7 4.2 TEST CASES FOR CTODS API AND GRID SERVICE..............................................................................................8 APPENDIX: ............................................................................................................9 Page 3
  4. 4. Functional Test 2.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. Page 4
  5. 5. 3. Limitations/Dependencies/Requirements 3.1 Test Case Limitations • 3.2 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. Test Case Dependencies / Assumptions • • 3.3 CTODS web application uses UPT to provision users and data. CTODS database has data available for test purposes. Default Setup • CTODS web application default user account: lsdtestuser1/password Page 5
  6. 6. 4. Test Cases The following test cases are executed on LSD linux 64 bit machine, cbapp-s1002. 4.1 Test Cases for CTODS Web Application 4.1.1 Configure CTODS with UPT Req. ID Step Num 1. 2. Description Go to UPT web application Login as superadmin 3. Register CTODS in UPT 4. Create an admin for CTODS 5. Superadmin logout 6. Log in to CTODS application as CTODS admin Step / Action Go to htpp://cbapps1002.nci.nih.gov:39080/uptlogin Enter “superadmin” for username, “changeme” for password, and “csmupt” for application name 1. Go to “Application” Tab 2. Click on “Create new Application” link 3. Enter correct values for CTODS application in the displayed form fields 4. Click “Create” 5. Click “Test Connection” 1. Go to “User” Tab 2. Click on “Create New User” Link 3. Enter valid values for the new user form (i.e., usrname: ctodsadmin, password: ctodsadmin) 4. Go to “Application” Tab 5. Click on the “Select Existing Application” Link 6. Search for CTODS application 7. Assign ctodsadmin as the admin for CTODS (See UPT manual for details of this procedure) Click the “Log Out” Tab 1. 2. 3. 4. 7. Create CTODS users Enter “ctodsadmin” in username Enter “ctodsadmin” in password; Enter “ctods” in the application field; Click “Submit” Create users with different privileges; See details from UPT manual. Expected Results Actual Results (if different) Pass/Fail CSM UPT login page is displayed Pass UPT superadmin page is displayed Pass CTODS application is registered in UPT with correct DB information for COTDS; Database connection test passes. Pass Newly created ctodsadmin user is assigned as an admin to CTODS application. Pass Superadmin loggeg out from UPT; UPT login page is displayed UPT displays CTODS application provisioning page Comments / Issue ID Pass pass Pass End Page 6
  7. 7. 4.1.2 Req. ID Log in CTODS Application Step Num 1. 2. Description Go to CTODS web application Login as CTODS user Step / Action Go to http://cbapps1002.nci.nih.gov:44210/CTODSViewer/ 1. Enter “lsdtestuser1” in the Login Id field 2. Enter “Password” in the Password field Expected Results Actual Results (if different) CTODS web application login page is displayed User is in the CTODS application ready to explore CTODS data Pass/Fail Comments / Issue ID Pass Pass END 4.1.3 Req. ID Privileged User Explore/Search CTODS Data Step Num 1. 2. 03. Description Go to CTODS web application Login as CTODS user Explore Adverse Events Explore Protocols 04. Step / Action Go to http://cbapps1002.nci.nih.gov:44210/CTODSViewer/ 1. Enter “lsdtestuser1” in the Login Id field 2. Enter “Password” in the Password field 1. Go the “Adverse Event” tab 2. Click “Submit” 1. Go the “Protocol” tab 2. Click “Submit” Expected Results Actual Results (if different) Pass/Fail CTODS web application login page is displayed User is in the CTODS application ready to explore CTODS data Pass Complete list of Adverse Events are presented on the page Complete list of Protocols are presented on the page Comments / Issue ID Pass Pass Pass END 4.1.4 Req. ID Non-Privileged User Explore/Search CTODS Data Step Num 3. Description 03. Explore Adverse Events Go to http://cbapps1002.nci.nih.gov:44210/CTODSViewer/ 3. Enter “ctods_qa1” in the Login Id field 4. Enter “123” in the Password field 3. Go the “Adverse Event” tab 4. Click “Submit” 04. Explore Protocols 3. 4. 4. Go to CTODS web application Login as CTODS user Step / Action Expected Results Actual Results (if different) Pass/Fail CTODS web application login page is displayed User is in the CTODS application ready to explore CTODS data Pass Adverse Events are NOT presented on the page Pass Protocols are NOT presented on the page Comments / Issue ID Pass Pass The error message was not descriptive. See GF # 23919 Go the “Protocol” tab Click “Submit” Page 7
  8. 8. Req. ID 4.2 Step Num END Description Step / Action Expected Results Actual Results (if different) Pass/Fail Comments / Issue ID 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/ctods Go to software/ctods-api directory 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.default 5) 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. 2) 3) (http://gforge.nci.nih.gov/svnroot/cactus/ctods/software/ctods-api/remote%20unit%20tests%20readme.txt ) Page 8
  9. 9. Appendix: Page 9
  10. 10. Appendix: Page 9

×