A test case describes the testable and verifiable behavior in a system. A test case can also describe the extent to which you will test an area of the application. Existing project artifacts, such as requirements, provide information about the application and can be used as test inputs for your test cases. TestManager provides built-in test input types, but almost any artifact can be used as a test input.
For example, here's what the following artifacts offer as test inputs:
* Requirements describe a condition or capability to which a system must conform.
* Visual models provide a graphic representation of a system's structure and interrelationships.
2. What Is the Rational Unified Process (RUP)?
RUP is a process framework for developing software that helps you:
* Coordinate the developmental responsibilities of the entire development team.
* Produce high-quality software.
* Meet the needs of your users.
* Work within a set schedule and budget.
* Leverage new technologies.
Rational Suite is a set of tools for every member of the software development team. It contains the following tools:
* Rational Unified Process
* Rational RequisitePro
* Rational ClearQuest
* Rational SoDA
* Rational ClearCase LT
* Rational TestManager
* Rational ProjectConsole
* Rational Rose
* Rational PureCoverage
* Rational Purify
* Rational Quantify
* Rational Robot
* Rational TestFactory
* Rational Process Workbench
* Rational NetDeploy
* Rational SiteLoad
Rational tools are sold with the following packages:
* Team Unifying Platform - Rational Unified Process, Rational RequisitePro, Rational ClearQuest, Rational SoDA, Rational ClearCase LT, Rational TestManager, and Rational ProjectConsole.
* Analyst Studio - Team Unifying Platform, and Rational Rose.
* DevelopmentStudio - Team Unifying Platform, Rational Rose£¬Rational PureCoverage£¬Rational Purify, and Rational Quantify.
* TestStudio - Team Unifying Platform, Rational PureCoverage£¬Rational Purify, Rational Quantify, Rational Robot, and Rational TestFactory.
* Enterprise - Team Unifying Platform, Rational Rose, Rational PureCoverage£¬Rational Purify, Rational Quantify, Rational Robot, Rational TestFactory, and Process Workbench.
* Content Studio - Team Unifying Platform, Rational NetDeploy, and Rational SiteLoad.
4. How to create or edit a custom data test?
1. Display the object for which you want to create the data test.
2. In Robot, click Tools > Object Data Test Definition.
3. Click Select to open the Select Object dialog box.
4. Select the object for which you want to create the data test in one of the following ways:
-- Drag the Object Finder tool over the object and release the mouse button. As you move the Object Finder tool over an object, the object type appears in the yellow TestTip.
-- Click Browse to open the Object List dialog box, select the object from the list, and click OK.
The Object List dialog box shows a hierarchical list of all objects on the Windows desktop, including hidden objects.
5. If the Select Object dialog box is still open, click OK to close it. The object classification of the selected object and its data tests appear in the Object Data Test Definition dialog box.
If the object is Unknown (not defined), the Define Object dialog box appears. Select an object type and click OK to open the Object Data Test Definition dialog box.
6. Do one of the following to display the Create/Edit Object Data Test dialog box:
-- To create a new test, type a name (50 characters maximum) in the Data test name box and click New.
-- To edit a custom test, select the test from the list and click Edit.
-- To copy a test and edit the copy, select the test and click Copy. Type the new name and click OK. Then, click Edit.
7. Select a property from the Property to test list. This property is the one whose values you want to capture in the data test. 8. Select the Column check box to add parameters for the vertical axis. Select the Row check box to add parameters for the horizontal axis.
9. Type an expression in the From and To boxes, or click the Expression button to the right of each box to build the expression.
An expression is a single value or property, or a combination of values, properties, and operators.
10. In the Using box (in the Create/Edit Object Data Test dialog box), type a property or select it from the list to further define the property that you are capturing and testing.
The Using box specifies what property Robot will modify to affect its iteration. For example, to iterate from row 0 to row Rows-1, Robot will set the Row property.
11. Select the check boxes under Additional parameters as needed.
12. In the Description box, type a description that indicates what the data test does.
13. Optionally, click Te s t to do the following:
--Verify the syntax of the data test before you save it.
-- If the syntax is correct, watch Robot perform the data test on the selected object.
When the test has ended, Robot opens a dialog box with the captured data. Click OK to close the dialog box.
14. Click OK to save the test and automatically verify it.
If the syntax of the expression is incorrect, the incorrect area is highlighted so you can correct it and then resave the test.
5. How to test a Java component's data?
1. Start recording in Robot.
2. Open the Java applet or application that you want to test.
3. Navigate to the page that you want to test.
4. Start creating the Object Data verification point.
5. Assign a name, wait state, and expected result for the verification point and then click OK.
6. In the Select Object dialog box, drag the Object Finder tool over the page until the component you want to test appears in the TestTip.
7. Release the mouse button.
8. If the dialog box is still open, click OK.
9. If the Object Data Tests dialog box appears, select the data test to use and click OK.
10. Complete the verification point as usual.
6. How to verify that the Java extension is loaded?
1. Start Robot.
2. Click Tools > Extension Manager.
3. Verify that Java is selected. If not, select it.
4. To improve the performance of Robot, clear the check boxes of all environments that you do not plan to test.
5. Exit Robot.
7. How to test an HTML elements properties?
1. Start recording in Robot.
2. Navigate to the Web page that contains the element to test.
3. Click the Object Properties Verification Point button on the GUI Insert toolbar.
4. Assign a name, wait state, and expected result for the verification point and then click OK,
5. Select the element to test and then click OK.
6. Click OK to insert the verification point.
8. How to Test the Destination of a Link?
1. Add an Object Data verification point.
2. With the Object Finder tool, select HTMLLink to test a text-based link.
3. Select a Contents data test to capture the URL of the destination.
4. Select the Case Sensitive verification method to test for the entire URL. Select the Find Sub String Case Sensitive verification method to test for part of the URL.
9. How to Test for Text within a Table?
1. Add an Object Data verification point.
2. Select the HTMLTable object with the Object Finder tool.
3. Select a Contents data test.
4. Select the Case Sensitive verification method to test for all of the text in the table. Select the Find Sub String Case Sensitive verification method to test for any text item with the table.
10. How to test an HTML elements data?
1. Start recording in Robot.
2. Navigate to the Web page that contains the elements to test. For example, navigate to the page that is returned after the user submits a page to be processed.
3. Click the Object Data Verification Point button on the GUI Insert toolbar.
4. Assign a name, wait state, and expected result for the verification point and then click OK.
5. In the Select Object dialog box, drag the Object Finder tool over the page until the element that you want to test appears in the TestTip.
6. Release the mouse button and click OK.
7. If the Object Data Test dialog box appears, select the data test to use and click OK.
8. Select the verification method that Robot should use to compare the baseline data captured while recording with the data captured during playback.
9. Click OK.
10. When finished, click the Stop Recording button on the GUI Record toolbar.
