Rajeshavanthi 2700022MCX Visits (330)
For Example, look at the below screenshot where few execution states are renamed.
The generated report, for example "TSE
STEPS TO REPRODUCE:
1. Navigate to Manage Project Properties → Execution States and rename the existing Execution state Permanently Failed to Unavailable.
2. Save the Changes
3. Log out and log back in
4. Create a Test Suite with a few Test Cases
5. Run the Test Suite. Set each of the Test Case results to Unavailable
6. Browse the TCER's and verify the results are set to Unavailable
7. Run the “TSER using Test Case Count (Live)” Report".
8. Note that the column names and Graphs do not reflect the modifications done to the execution states
This behavior is identified as a product defect
Rajeshavanthi 2700022MCX Visits (854)
In a very typical scenario, To create a test, many testers currently sit at a PC and alternate between completing an action in the application under test and writing the step on a notepad. When the test is complete on paper, the tester (or in some cases an administrative assistant for the testing group) types the steps into a standard test template, frequently using either Microsoft Word or Microsoft Excel. Following this procedure, a single manual test is essentially written twice.
Eliminating the need to write each test twice can save you time for other testing.
In addition to writing tests twice, much time is spent adapting existing tests for similar new tests. For example, a tester might create a test to log into the application under test as an administrator, and then adapt that test to log into the application under test as a regular user. This adaptation typically takes one of two forms:
• Open the existing test, edit steps as needed, and save the test with a new filename.
• Open a new test template, copy steps from the existing test, edit steps as needed, and save the new test.
Reducing duplication among many tests reduces the time you spend maintaining test scripts.
Testers typically receive many new software builds during a development cycle, often at an increasingly rapid rate toward the end of the cycle.
When a build contains a new feature or a fix that requires modifying the steps of a test, all of the tests that relate to the new feature or fix must be updated to reflect the change in the application under test. Although this update process is not difficult to manage when only a few tests require updating, when dozens (or hundreds) of tests are affected by changes to a commonly used area of the application under test, such as a login screen, updating can be very time-consuming. Eliminating or reducing the work that is required to keep many tests up to date can save you time for additional testing.
As you increase the efficiency of your testing effort, you can use the saved time to conduct additional tests. Rational Quality Manager can help you work more efficiently in each of the testing activities:
• Creating tests: Rational Quality Manager helps you to manage reusable content and use it in similar tests. As a result, you spend less time authoring tests.
• Running tests: Rational Quality Manager associates text to be typed in the application under test with an execution step. Rational Quality Manager also associates verification text with a test step, and then compares the comparison. Rational Quality Manager provides test data variables so that you can define a test once and run it many times to accommodate different data input values. These features save you time typing in the application under test, comparing actual to expected results, and testing different data values.
• Reporting test results: Rational Quality Manager provides customizable reports that reflect test result data from all phases of the project. These reports save time that you would have spent manually tabulating test results for reporting.
• Maintaining tests: Rational Quality Manager reduces the amount of required test maintenance by storing reusable content only once. As a result, you spend less time updating many similar tests.
IBM Rational Quality Manager: Execution variable displays deleted when execution status is changed from Approved to re-open
Rajeshavanthi 2700022MCX Visits (466)
Under IBM Rational Quality Manager v4.0.3 , say you have added a few execution variables and these variables are assigned to Test Steps for a given Test Case.
Modified date: Mar 25, 2015 1:19:33 PM
From the UI perspective; the Execution Variables are still associated with each of the steps; however, the Execution Variables View is empty. So basically there are two issues here.
dmmckinn 1200006SCS Visits (904)
Are you planning an upgrade to a newer release of IBM Rational Team Concert (RTC), Rational Quality Manager (RQM), Rational Requirements Composer (RRC), Rational DOORS Next Generation (DNG) or your Jazz Team Server (JTS) and unsure about whether or not your clients or servers need to be upgraded together or can be upgraded separately?
AcdntlPoet 2700019V2G Visits (1170)
Stéphane Leroy (Unleash the Labs CLM, IBM Software Engineer) has created a wonderfully simple table to outline the Test Lab mana
And don't miss Stéphane's most recent posts surrounding his expertise in RTC and enterprise modernization!