AcdntlPoet 2700019V2G Visits (537)
Last week saw the release of version 6.0 for a few different products... here's three blog posts from the Jazz team blog covering what's new in DOORS Next generation, Rational Quality Manager, and Reporting for Collaborative Lifecycle Management!
What’s new in DOORS Next Generation 6.0? - This release could well be introducing the most fundamental function into a requirements management tool since RM systems began. While we continue our drive with usability and productivity we are also providing support for requirements configuration management, built from the ground up as part of the native tool, rather than simply integrating to an external CM system. [Read more]
What’s new in Rational Quality Manager 6.0? - IBM Rational Quality Manager (RQM) 6.0 brings both incremental improvements over v5 and a completely new dimension to managing test artifacts. On the incremental improvements front, the team has done a great job to continue to work closely with our customers to further improve the user experience on specific areas such as dashboard widgets or collaboration. At the same time, v6.0 introduces the support of configuration management for test artifacts, linked to other domains such as requirements or design, and contributing to the notion of global configurations across our Collaborative Lifecycle Management (CLM) solution. This version marks the beginning of a completely new set of capabilities that empower users to do parallel development and test, and to reuse artifacts in an effective way. [Read more]
What’s new in Reporting for Collaborative Lifecycle Management 6.0 - It’s been an exciting time here for us in the Reporting team and we’re especially proud of the tremendous progress that’s been made to provide you with an easy-to-use, cross-project, cross-tool reporting solution. We’ve built on the foundation of the Jazz Reporting Service and Data Collection component in 5.0 that many of you have helped shape to bring several new advancements in reporting in Collaborative Lifecycle Management (CLM) 6.0. I encourage you to give the latest release a try and give us feedback! [Read more]
Rajeshavanthi 2700022MCX Visits (442)
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 (910)
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 (506)
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.
AcdntlPoet 2700019V2G Visits (847)
IBM® Rational® Quality Manager provides extensible APIs that enable test-automation tools from various industries to be integrated into the Rational Collaborative Lifecycle Management (CLM) environment. These APIs make the automation tools' capabilities available in Rational Quality Manager, providing a rich user experience. After an integration is built, it goes through a rigorous validation process and then is available to users.
ETAS LABCAR-AUTOMATION (LCA), an automated testing tool widely used in the automotive industry, now integrates with Rational Quality Manager through these extensible APIs. MicroGenesis, an IBM business partner, built this one-of-a-kind integration, enabling users from the systems space to leverage the power of collaboration and the enhanced traceability of the CLM environment. (All copyrights and trademarks related to LABC