Rajeshavanthi 2700022MCX Visits (595)
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.
AcdntlPoet 2700019V2G Visits (1502)
Have you found a technote that helped you solve an issue without having to open a PMR? Let us know by rating and leaving feedback on that content using the "Rate this page" stars on the top right of the content or the box of the same name at the bottom of each technote! Your feedback is highly valuable to us as we work to improve the quality of solutions and help you sole issues more effectively and efficiently.
Last month the following technotes were the most heavily reused when closing PMRs opened by you, our clients. Hot off the presses is the top content reused during October to help solve your Rational Focal Point, Rational Change, or Rational Quality Manager issues. We hope that highlighting them here will help others encountering the same or similar issues also find quick resolution:
Rational Focal Point
Rational Quality Manager
AcdntlPoet 2700019V2G Visits (1502)
Here are three examples (the last is also embedded in this post) of playlists to get you started and show the value of following the playlists specific to the product you care about:
Over the past week, and particularly this past weekend, a few new downloads made their way through our tweet stream and Facebook wall. Seeing as these were posted during typically 'off' hours for most of us, we thought it would be of some benefit to highlight those recent releases here, to raise visibility in the case that you may have missed and need one or more of these downloads:
Want to make sure you never miss notifications like the ones listed above again? Then check out "MyNotifications" and setup a free subscription to receive only the products and document types which YOU are interested in, and in the manner you desire (RSS, web page, or direct daily/weekly emails)!
IBM Rational Quality Manager: Execution variable displays deleted when execution status is changed from Approved to re-open
Rajeshavanthi 2700022MCX Visits (352)
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.