TENNCARE ORACLE TESTING PROCESS

The TennCare Oracle Testing Leads role is to facilitate the testing process during different testing cycles (Unit, Link, Regression, and System), understand the testing deliverables and requirements, and coordinate all efforts / deliverables required by the client / EDS account. Key to this role is good organization and communication skills. GETTING STARTED Maintain List of Test Scripts (for internal tracking, monitoring, and reporting): Identify business processes for each functional area and determine individual steps for these processes, which could become individual test scripts Gather list of Unit Test cases for scenarios (a single instance of the process) from Functional Consultants Gather list of Unit Test cases for technical specifications from Technical Developers Consolidate items above into two master lists of test scripts: one for Accounting (AP and GL) and one for Premium (AR) o Label each test script with an ID (from PWB, see next deliverable) o Tie each test script with a process that is listed in PWB for the respective functional area o Associate each test script to a specific RFP Requirement (Functional Consultant will need to provide this information) o Estimate when test script will be run during System Testing o Determine who will be responsible for running the test script during System Testing o Monitor who is responsible for writing the scripts, whether or not actual test script has been written, and if it has been moved to eRoom for electronic storage Create Test Scripts in PWB (Doco Tool Database -- contractually required by EDS Base Account Note: these can be done by DDI Testing Team): Enter new test script to obtain Test Case ID (this will need to be updated on the master spreadsheets for each test script and will become the ongoing tracking identifier) Create a brief description for the test script (limited to xxx characters) Provide more detailed description for the test script Associate each test script to (Tested Objects): o Change Order (Technical Consultant will need to provide this information) o Report (Technical Consultant will need to provide this information) o Window (Technical Consultant will need to provide this information) o Other Object (Technical Consultant will need to provide this information) Associate each test script to Requirements (Tested Requirements) (Functional Consultant will need to provide this information) Set up Tester as Marguerite Bogle for all test scripts (Participants) Assign initial status of all test scripts to Identified by Marguerite Bogle (Status) In appropriate Notebook (Accounting Phase II [Record 107] and Premium Phase II [Record 108]), add all test scripts for each business process (NOTE: Accounting Phase I is Record 69 and Premium Phase I is Record 70) In appropriate Release (SAK Release Number 25 = July 23, 2003), add all test scripts with initial status of Test Data Identified Create Test Scripts:

Date Printed: 8/23/2011

Page 1 of 4

TENNCARE ORACLE TESTING PROCESS

Create a separate Word document for each test script Name test script with 2-character module (AP, AR, or GL) followed by the Test Case ID assigned by PWB Title on script will be test script name with brief description Test Scenario Description explains why this test needs to be run Purpose describes what is being tested Process associates the PWB process for the module that this script is categorized into (and which Notebook in Doco Tool this script is associated with) Prod / Release should always be 11i (11.5.8) List individual steps (increment by 10 in case more steps must be inserted later) List the Responsibility the user must enter into to perform the functions listed List the Navigation Path the user must follow to perform the functions listed List the Action that the user must take once in the form Explain the Expected Results from each step If the user must enter Data, list the required fields and actual data in each step Describe any additional functionality, options, etc. in the Notes section for each step

Save the electronic version of the test script in eRoom (save in eRoom [http://collaborate5.coe.eds.com/eRoom/facility003/EDSERMTOP/] under Test Cases / Phase II / Test Scripts) Print test script and file into correct place in binders to be executed later Update the master spreadsheet to indicate that that script is written, filed in eRoom, and ready for review / testing (there are formulas built into the spreadsheet that will help monitor the test script completion stats for reporting to management) PRE-SYSTEM TESTING NOTES

EXECUTING TESTS Organize all printed copies of scripts into binders (I recommend filing them by Test Script ID to help in finding them) with the master spreadsheets used as check-out sheets Ensure all electronic copies of the Test Scripts are written, in the appropriate eRoom location, accurately named, and that anyone can access and update them Have testers come to the Testing Leads desk and actually check out the scripts they want to run on the master spreadsheets and take the printed copies from the binders As tests are successfully run, the scripts should be updated and placed (with the results files attached) in the Test Scripts Completed Successfully basket on the Testing Leads desk and the tester should check the script back in on the master spreadsheets and change the status of the Test Script to Passed. In addition, the test scripts and their resulting files should be placed in the appropriate eRoom location (Test Cases / Phase II Test Case Packets). If a test results in a defect, the tester fills out an electronic copy of the Defect Log and supplies backup documentation for defect. The tester then emails this to Srini

Date Printed: 8/23/2011

Page 2 of 4

TENNCARE ORACLE TESTING PROCESS

Ravikanti and the Testing Lead. Srini assigns a developer to work on defect. The Testing Lead captures the defect on the master spreadsheet, files the electronic copies in eRoom, and forwards email to Vickie Angell to track in PWB / Doco Tool. The tester should also place printed copies of the Defect Log and backup in the Test Scripts Defective basket on the Testing Leads desk. These will be attached to the completed Test Scripts when they are completed later for documentation purposes. Every afternoon, the Testing Lead should use the marked up master spreadsheets and update the electronic version of it, then make the appropriate changes in PWB / Doco Tool (or request that the DDI Testing Team make these updates): Change the status of the test case to: o Test Case in Work when the script has been checked out and not returned yet o Passed in Model when the script has been checked back in and was marked as Passed o Defect Identified if the tester submitted a defect log for the test script Update the test case status in the Release database when the script has Passed Ensure all changes on the master spreadsheets have been captured in PWB / Doco Tool before Martha Terry runs the stats report every evening (during Phase I, we compared the results from her query and the master spreadsheets to ensure they agreed, or made any necessary changes usually to PWB / Doco Tool to make them match) Make an additional copy of all documentation (the State requires one set and the DDI Testing Team requires an additional copy for their records). Take the second copy to the DDI for filing into their books. Organize the completed Test Scripts into processes (as reflected on the master spreadsheets) and ensure they are completed correctly (ensure the status is Passed, there are Start and Completion Dates, the last page reflects the results filenames and the testers name). If these have to be updated, ensure the electronic copy is updated on eRoom as well. After updating the master spreadsheets, the Testing Lead must ensure that the electronic files (test scripts and their results files) are in the correct eRoom location (Test Cases / Phase II Test Case Packets) and named correctly, then copy them to a temporary drive on his / her hard drive to be copied to the appropriate PWB / Web Folders (or send them to the DDI Testing Team), copy them to another eRoom location (Test Cases / Phase II / Already Moved to PWB), then remove them from the Test Cases / Phase II Test Case Packets eRoom location. In PWB / Web Folders, each test case has its own folder under the appropriate functional area (Accounting or Premium) and all specific script information must be placed into each folder: http://pwb.tnxix.hcg.eds.com/tennessee/Subsystem/Accounting/Testing/Test Cases/ http://pwb.tnxix.hcg.eds.com/tennessee/Subsystem/Premium/Testing/Test Cases/ Placing the Test Script and the resulting files into these individual script folders enables a PWB user to click on the test script and see links to these files

Date Printed: 8/23/2011

Page 3 of 4

TENNCARE ORACLE TESTING PROCESS

Date Printed: 8/23/2011

Page 4 of 4