DOCUMENT OUTPUT Raltus Sample Ouput AX-OQ-006 REV B Siebel Raltus Test Acer America Test Script :- Creator: Robbie McConnell Category: Run Date: Number of Steps: Current Status: Signed By 04 Oct 2012 15:52 17 FAILED Date of Signature Role 04 Oct 2012 15:44 Approver Signature Verified Mark Murray Digitally Signed Microsoft Dynamics AX 2009 ERP System Control # 214-YYZZ. 1. Responsibilities 1.1. Owner - Responsible for organizing the validation and/or implementation effort. Approves test script changes once the test protocols are approved 1.2. Tester - Executes the test protocol, marks the realized test results, documents the actual result when it differs and seeks approval when deviations to the protocol are necessary 1.3. Reviewer - Reviews the executed test protocol, review proof of execution data, assures compliance to good documentation practices, and marks the overall test case result. 1.4. Quality Assurance - Responsible for approving protocol deviations 2. Materials/Equipment Used 2.1. Raltus Procedure Capture® software was used to capture and run all OQ test protocols. 3. Procedure The execution methodology used to run the test protocols is defined below. The “Test Corrections”, “Tester” and “Reviewer” sections are included in all test protocols. 3.1. Protocol 3.1.1. Test Corrections - Minor test inconsistencies such as typo’s, spelling errors, obvious omissions shall be corrected and initialled and dated before completing the test. A comment as to why the correction was made can be added to the “Comments” sections at the end of the test case. 3.1.2. Tester - For each test case below, the tester shall execute the test steps using Raltus Procedure Capture® as written. When the “Expected Results” are realized for the test step, the tester will circle the “P” in the “Result” column and go on to the next step. When the “Expected Results” are not realized for a test step, the tester shall circle the “F” in the result column, note the actual result in the “Result if Failed” column, and then consult with the Project Lead to determine whether execution of this procedure (and others) will be suspended, and if so when it may be resumed or restarted. 3.1.3. Reviewer - The reviewer will review the executed test cases once protocol execution is complete. The test case results at each test step and all test documentation shall be reviewed. The reviewer is to confirm that all results are properly marked and that all documentation complies with Good Documentation Practices. After reviewing all test steps for the test case, the Reviewer shall mark “Pass” in the “Test Status” box if all test steps passed, or mark “Fail” if any test step did not pass, sign in the “Review Section” and enter the date the review occurred. 3.2. Test Case Standards Copyright (c) Raltus Limited 2012, All Rights Reserved. Page 2 of 14 Printed On : 04 Oct 2012 15:56 Microsoft Dynamics AX 2009 ERP System Control # 214-YYZZ. The following paragraphs below define the set of standards developed to assist in ensuring complete test coverage and consistency in test case creation. The test case standards are documented here. 3.2.1. All requirements will map to tests 3.2.2. N/A maybe used in the Req ID column if the test step is not verifying the actual requirement, but is necessary to create a state the requirement under test can be examined 3.2.3. Each requirement will have positive and negative tests when applicable 3.2.4. Field limits will be tested when noted in the requirements 3.2.5. Test data will be prepared and entered into the database before testing begins 3.2.6. Test data will be documented and provided to the test case originator for use in the creation of test scripts 3.2.7. Terminology will be used as defined by the module owner. Each test protocol will document standard definitions in the definitions section of the protocol 3.2.8. Test Cases are to be stand alone when ever possible. If a prior test is required to be executed before the next test case can begin the test case must state that in the first step of the test case. 3.2.9. All tests will contain an expected result. 3.2.10. All test cases will be executed on the test system before they are finalized and check into Agile. (This is part of the beta testing activity)The System shall have an IQ/OQ. 3.2.11. All test protocols have been reviewed and are approved in Agile 3.2.12. All requirements are frozen and approved in Agile… 3.2.13. SOP's and WI's being used during validation and/or implementation are approved in Agile. 3.2.14. Records are retained in accordance with 800176-001 Control of Quality Records. 3.3. Test Case Corrections, Deviations, and Documentation The purpose of this section is to describe the general requirements that must be adhered to during the test case execution. 3.3.1. Test Corrections - Minor test inconsistencies such as typo’s, spelling errors, and obvious omissions shall be corrected and initialed and dated before completing the test. A comment as to why the correction was made is added to the “Comments” section at the end of the test case. 3.3.2. Test Deviations - Non trivial errors in test steps require a Deviation. When a test deviation is necessary, the tester will work with the product owner and management to document the deviation in the “Deviation Section” at the end of the test case. The product owner and management will then review the deviation Copyright (c) Raltus Limited 2012, All Rights Reserved. Page 3 of 14 Printed On : 04 Oct 2012 15:56 Microsoft Dynamics AX 2009 ERP System Control # 214-YYZZ. the test case. The product owner and management will then review the deviation section before the test is resumed and sign and date the Deviation. Deviations can include, but are not limited to test failures that have an acceptable work around, test that do not follow the required sequence, and incorrect expected results. 3.3.3. Test Documentation - All test execution activities shall be documented by the tester and signed and dated. Hardcopy documents (such as screen prints or reports) that are attached as evidence of execution shall comply with WI, Data Recording Requirements (800286001). For comments, observations, statements, that are written anywhere on any part of a protocol, for any reason, the tester's initials and date shall be included immediately following the written text or notes. 3.4. Test Cross Reference Each test case in the test protocol demonstrates compliance to defined behavior as identified within the User Requirements Specification # 200-9813.01/002. Copyright (c) Raltus Limited 2012, All Rights Reserved. Page 4 of 14 Printed On : 04 Oct 2012 15:56 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Left Click PASS 1 Screen Check PASS Check that the Service Request application is loaded 2 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 5 of 14 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Screen Check PASS Check that the Calendar is there 3 Left Click PASS 4 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 6 of 14 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Left Click PASS 5 Left Click PASS 6 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 7 of 14 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Screen Check PASS Check that the global icons are there 7 Left Click PASS 8 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 8 of 14 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Type Acer America PASS 9 Left Click PASS 10 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 9 of 14 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Offset Click PASS 11 Left Click PASS 12 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 10 of 14 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Offset Click PASS 13 Screen Check PASS Ensure that the Status is Open 14 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 11 of 14 Microsoft Dynamics AX 2009 ERP System # Action Control # 214-YYZZ. Expected Screen Actual Screen Pass Screen Check FAIL Ensure that the Substatus is Resolved 15 Left Click PASS 16 Copyright (c) Raltus Limited 2012, All Rights Reserved. Printed On : 04 October 2012 15:55 Page 12 of 14 Microsoft Dynamics AX 2009 ERP System Control # 214-YYZZ. 4. Overall Test Result Pass / Fail Status: Signed By FAILED Date of Signature Role Signature Verified 04 Oct 2012 15:52 Executor Digitally Signed 04 Oct 2012 15:55 Manager Digitally Signed Robbie McConnell Ann Devine Copyright (c) Raltus Limited 2012, All Rights Reserved. Page 13 of 14 Printed On : 04 Oct 2012 15:56 Microsoft Dynamics AX 2009 ERP System Control # 214-YYZZ. 5. Deviations / Errors # Error Details 15 Unable to find image on screen.(FoundNone) Runtime Image Recorded Image Runtime Screen Recorded Screen Copyright (c) Raltus Limited 2012, All Rights Reserved. Page 14 of 14 Printed On : 04 October 2012 15:56
© Copyright 2024