TE.010 Testing Strategy

Using Quality Center Author:Paulina ContrerasCreation Date:02-MAY-2014Last Updated:13-MAY-2014Version:1.0Note: Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents. When you change any of these values, be careful not to accidentally delete the bookmark. You can make bookmarks visible by selecting Tools->OptionsView and checking the Bookmarks option in the Show region.Note: To add additional approval lines, press [Tab] from the last cell in the table above.

Document Control

Change Record

DateAuthorVersionChange Reference

13-MAY-2014Paulina Contreras1.0No Previous Document

Reviewers

NamePosition

Distribution

Copy No.NameLocation

1 Library MasterProject Library

2 Project Manager

3

4

Note: The copy numbers referenced above should be written into the Copy Number space on the cover of each distributed copy. If the document is not controlled, you can delete this table, the Note To Holders, and the Copy Number label from the cover page.

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Table of Contents

iiDocument Control

2Application Lifecycle Management Roadmap

3Requirements

3Requirements Details

4Test Coverage

5Test Plan

5Test Cases

6Test Scenarios

6Requirements Coverage

6Test Lab

7Running Tests

9Defects

9Entering Defects

10Linking Defects

11Appendix A Flowchart of Defect Process in Quality Center

Note: To update the table of contents, put the cursor anywhere in the table and press [F9]. To change the number of levels displayed, select the menu option Insert>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

Application Lifecycle Management Roadmap

In Quality Center, also known as Application Lifecycle Management (ALM), we use this roadmap for a project:

PhaseDescription

Requirement Specifications Define requirements to meet your business and testing needs. You can manage the requirements and conduct multi-dimensional traceability between requirements, tests, and defects, across multiple releases and cycles. ALM provides real-time visibility of requirements coverage and associated defects to evale quality and business risk.

Test Planning Based on the project requirements, you can build test plans and design tests. ALM provides a repository for both manual and automated tests.

Test Execution Create a subset of the tests in your project designed to achieve specific test goals. ALM supports functional, regression, performance, and advanced testing. Execute scheduled tests to diagnose and resolve problems.

Defect Tracking Submit defects and track their repair progress. Analyzing defects and defect trends helps you make effective "go/no-go" decisions. ALM supports the entire defect lifecycle - from initial problem detection through fixing the defect and verifying the fix.

Requirements

Requirements describe in detail what needs to be solved or achieved to meet the objectives of your application under development. The Requirements module enables you to define, manage and track requirements at all stages of the application lifecycle management. We start with the process flows to enter basic requirements. Requirements are not system specific.

Requirements DetailsEnter detailed information for requirements. You can use the fields ALM provides and add your own. Click on the link for the Req ID. Since we have not run any of our test scripts yet, the Direct Cover Status field has a value of No Run.

Test Coverage

It is essential that the tests in your test plan meet your original requirements. To keep track of the relationship between your requirements and tests, you add links between them. Test coverage assists you in assessing the scope of testing to achieve all of the requirements, and the impact of a change in the test or requirement. A test can cover more than one requirement.

Test PlanDeveloping a clear and concise test plan is fundamental to successful application testing. A good test plan enables you to assess the quality of your application at any point in the application management process. Outline a strategy for achieving your requirements, as defined in the Requirements module.

Test CasesTest scripts contain detailed steps on how to execute a test and evale the results.

Test Scenarios

ALM also enables you to use the same test to test different Test Scenarios. Each Test Scenario uses a different set of data. Use the Test Configurations tab to enter the data for the Test Scenarios. For example, we may execute this test script for two different test scenarios: Creating a new strategic customer and creating a new non-strategic customer.

Requirements CoverageIn the Test Plan module, you create requirements coverage by linking tests to a requirement just like in the Requirements Module. Requirement coverage assists you in assessing the impact of a change in a requirement. A test can cover more than one requirement.

Test Lab

Test Lab is where you run your test scripts. You can combine test scripts together into a test set, but each test script can be in its own test set. Test Lab also has functionality to run automated tests. Test sets can contain both manual test and automated tests. For example, suppose we want a tester to execute all the test scenarios for the Create new customer test which includes a strategic and non-strategic customer. We can combine the test scenarios into one test set. That way, only when the tester runs both scenarios in the one test set do they indicate the entire test set is passed.

Running Tests

After establishing test sets, select the Run Test Set icon in Test Lab to run a test.

Click Begin Run to start the test

Enter the actual results and indicate whether a step passes, fails, etc. You can also change the test script while running the test by inserting, removing, or changing the steps.

You can always stop a test, pause a test, start from the beginning of the current test, and start from the beginning of a new test run.When all of the steps of a test are passed, ALM updates the status of the test script to Passed. When all of the test scripts identified to cover requirements are passed , we update the status of the requirement to Passed. When all of the requirments are passed, the test plan is complete and we proceed to the Installation phase.Defects

Locating and repairing application defects efficiently is essential to the development process.

You use the Defects module to:

Create application defects for an ALM project.

Track defects until application developers and testers determine that the defects are resolved.

Defects inform members of the application development and quality assurance teams of new defects discovered by other members. As you monitor the progress of defect repair, you update the information in your project. The QA Team will work with you to track defect progress.

Entering Defects

You can enter a new defect while you are running a test, or later. Here is an example of entering a defect during a test run.

Linking Defects

It is important to link defects to test scripts so other team members can use the test script for retesting. If you create a defect while running a test, ALM automatically links the defect to the test script. If you create a defect later, you must manually link the defect to the test script.

After creating the defect, link it to the appropriate test script

Appendix A Flowchart of Defect Process in Quality Center

pg. 3Using Quality Center.doc