Explore topic-wise InterviewSolutions in .

1. By Content - to verify that the recorded values EXIST during playback.
2. By LOCATION - to verify that the recorded values exist in the same locations during playback.
3. By TITLE - to verify that the recorded values remain with their titles (NAMES of menus or columns) during playback, even though the columns may have changed locations.
4. By Key/Value - to verify that the recorded values in a row remain the same during playback.

1. Right-click the verification point in the Asset (left) pane and click Copy.
2. In the same script or in a different script (in the same PROJECT), right-click Verification Points in the Asset pane.
3. Click Paste to paste a copy of the verification point and its associated files into the project. If a verification point with that NAME already EXISTS, ROBOT appends a unique number to the name. You can also copy and paste by dragging the verification point to Verification Points in the Asset pane.
4. Click the top of the Script (right) pane of the original script.
5. Click Edit > FIND and locate the line with the verification point name that you just copied.
6. Select the entire line, which starts with Result=.
7. Click Edit > Copy.
8. Return to the script that you used in step 2. Click the location in the script where you want to paste the line. Click Edit > Paste.
9. Change the name of the verification point to match the name in the Asset pane.

Rational TestManager is the one place to manage all TESTING ACTIVITIES--planning, design, implementation, execution, and analysis. TestManager ties testing with the rest of the development effort, joining your testing assets and tools to PROVIDE a single point from which to understand the exact state of your project.

Test MANAGER supports five testing activities:

1. Plan Test.
2. Design Test.
3. Implement Test.
4. Execute Tests.
5. EVALUATE Tests.

Rational TestManager is the one place to manage all testing activities--planning, design, implementation, execution, and analysis. TestManager ties testing with the rest of the development effort, joining your testing assets and tools to provide a single point from which to understand the exact state of your project.

Test Manager supports five testing activities:

Test REQUIREMENTS are defined in the Requirement Hierarchy in TestManager. The requirements hierarchy is a graphical outline of requirements and nested child requirements.

Requirements are stored in the requisite PRO database. Requisite Pro is a tool that HELPS project teams control the development process by managing and tracking the changes of requirements.

TestManager includes a baseline version of Requisite Pro. The full version with more features and customizations is available in the RATIONAL Suite TestStudio.

Test requirements are defined in the Requirement Hierarchy in TestManager. The requirements hierarchy is a graphical outline of requirements and nested child requirements.

Requirements are stored in the requisite pro database. Requisite Pro is a tool that helps project teams control the development process by managing and tracking the changes of requirements.

TestManager includes a baseline version of Requisite Pro. The full version with more features and customizations is available in the Rational Suite TestStudio.

When a robot scripts runs the OUTPUT creates a test LOG. Test logs are managed now is the TestManager application. RATIONAL now allows you to organize your logs into any type of format you need.

You can create a directory structures that suites your need Create build names for each build version (or development) Create FOLDERS in which to put the build in.

When a robot scripts runs the output creates a test log. Test logs are managed now is the TestManager application. Rational now allows you to organize your logs into any type of format you need.

You can create a directory structures that suites your need Create build names for each build version (or development) Create folders in which to put the build in.

Rational ClearQuest is a change-request management tool that tracks and manages defects and change requests throughout the development process. With ClearQuest, you can MANAGE every type of change activity ASSOCIATED with software development, including ENHANCEMENT requests, defect reports, and DOCUMENTATION modifications.

With Robot and ClearQuest, you can:

• Submit defects directly from the TestManager log or SiteCheck.
• Modify and track defects and change requests.
• Analyze project progress by running queries, CHARTS, and reports.

Rational ClearQuest is a change-request management tool that tracks and manages defects and change requests throughout the development process. With ClearQuest, you can manage every type of change activity associated with software development, including enhancement requests, defect reports, and documentation modifications.

With Robot and ClearQuest, you can:

• Click Tools > General Options, and then click the Object MAPPING tab.
• From the Object type list, select the standard object type that is associated with the object class name. Robot DISPLAYS the class NAMES already available for that object type in the Object classes list.
• From the Object classes list, select the name to modify or DELETE.
• Do one of the following:
• To modify the class name, click Modify. Change the name and click OK.
• To delete the object class mapping, click Delete. Click OK at the confirmation PROMPT.
• Click OK.

• In an ASCII editor, create an empty TEXT file with the extension .ord.
• Save the file in the Dat folder of the project.
• Click Tools > GUI RECORD Options .
• Click the Object Recognition Order tab.
• From the Object order preferences list, SELECT the name of the file you created.
• Change the method order to customize your preferences.

1. OPEN the GUI RECORD Options dialog BOX.
2. Click the Object Recognition Order tab.
3. Select a preference in the Object order preference LIST.
4. Click OK or CHANGE other options.

• Open the GUI Record Options dialog box by doing one of the following:
• Before you START RECORDING, click Tools > GUI Record Options.
• Start recording by clicking the Record GUI Script BUTTON on the TOOLBAR.

In the Record GUI dialog box, click Options.

• SET the options on each tab.
• Click OK.

In the Record GUI dialog box, click Options.

Use the Rational diagnostic tools to perform runtime error checking, profile application performance, and analyze code coverage during playback of a ROBOT script.

• Rational Purify is a comprehensive C/C++ run-time error checking tool that automatically pinpoints run-time errors and memory leaks in all components of an application, INCLUDING third-party libraries, ensuring that code is reliable.
• Rational Quantify is an advanced performance profiler that PROVIDES application performance analysis, ENABLING developers to quickly find, prioritize and eliminate performance bottlenecks within an application.
• Rational PureCoverage is a CUSTOMIZABLE code coverage analysis tool that provides detailed application analysis and ensures that all code has been exercised, preventing untested code from reaching the end-user.

Use the Rational diagnostic tools to perform runtime error checking, profile application performance, and analyze code coverage during playback of a Robot script.

RATIONAL Testmanager is a sophisticated tool that can be used for automating performance tests on client/server systems. A client/server system includes client applications accessing a DATABASE or APPLICATION server, and browsers accessing a Web server.

Performance testing USES Rational Robot and Rational TestManager. Use Robot to record client/server conversations and store them in SCRIPTS. Use TestManager to schedule and play back the scripts. During playback, TestManager can emulate hundreds, even thousands, of users placing heavy loads and stress on your database and Web servers.

Rational Testmanager is a sophisticated tool that can be used for automating performance tests on client/server systems. A client/server system includes client applications accessing a database or application server, and browsers accessing a Web server.

Performance testing uses Rational Robot and Rational TestManager. Use Robot to record client/server conversations and store them in scripts. Use TestManager to schedule and play back the scripts. During playback, TestManager can emulate hundreds, even thousands, of users placing heavy loads and stress on your database and Web servers.

RATIONAL RequisitePro is a requirements management tool that HELPS project teams control the development process. RequisitePro ORGANIZES your requirements by linking Microsoft Word to a requirements repository and providing traceability and CHANGE management throughout the project lifecycle.

Rational RequisitePro is a requirements management tool that helps project teams control the development process. RequisitePro organizes your requirements by linking Microsoft Word to a requirements repository and providing traceability and change management throughout the project lifecycle.

To set the GUI RECORDING options:

1. Open the GUI Record Options DIALOG box by doing one of the following: . Before you start recording, CLICK Tools > GUI Record Options. . Start recording by clicking the Record GUI Script button on the TOOLBAR. In the Record GUI dialog box, click Options.
2. Set the options on each tab.
3. Click OK.

To set the GUI recording options:

• Open the GUI Record Options dialog box.
• In the GENERAL tab, do one of the following:
• Select Define unknown objects as type Generic to have ROBOT automatically ASSOCIATE unknown objects encountered while RECORDING with the Generic object type.
• Clear Define unknown objects as type Generic to have Robot suspend recording and open the Define Object dialog box if it encounters an unknown object during recording. Use this dialog box to associate the object with an object type.
• CLICK OK or change other options.

• Identify the class name of the window that CORRESPONDS to the object. You can use the Spy++ utility in Visual C++ to identify the class name. You can also use the Robot Inspector tool by clicking TOOLS > Inspector.
• In Robot, click Tools > General OPTIONS, and then click the Object Mapping TAB.
• From the Object type list, select the standard object type to be ASSOCIATED with the new object class name.
• Robot displays the class names already available for that object type in the Object classes list box.
• Click Add.
• Type the class name you identified in step 1 and click OK.
• Click OK.

• CLICK Tools > General Options, and then click the Object Mapping tab.
• From the Object type list, select the standard object type that is associated with the object class name.
• Robot displays the class NAMES already available for that object type in the Object classes list.
• From the Object classes list, select the name to modify or delete.
• Do one of the following:

• To modify the class name, click Modify. CHANGE the name and click OK.
• To delete the object class mapping, click Delete. Click OK at the CONFIRMATION PROMPT.
• Click OK.

When ROBOT is minimized or is HIDDEN behind other windows during recording, you can bring it to the foreground in any of the following ways:

• Click the OPEN Robot WINDOW button on the GUI Record toolbar.
• Click the Robot button on the Windows taskbar.
• Use the hot key COMBINATION CTRL+SHIFT+F to display the window and CTRL+SHIFT+H to hide the window.

When Robot is minimized or is hidden behind other windows during recording, you can bring it to the foreground in any of the following ways:

• OPEN the GUI Record Options dialog BOX.
• In the General tab, type a PREFIX in the Prefix box.
• Clear the box if you do not want a prefix. If the box is cleared, you will need to type a name each time you record a new script.
• Click OK or CHANGE other options.

The next time you record a new script, the prefix and a number APPEAR in the Name box of the Record GUI dialog box.

The next time you record a new script, the prefix and a number appear in the Name box of the Record GUI dialog box.

1. Open the GUI Record Options DIALOG box.
2. Click the Object Recognition ORDER TAB.
3. SELECT a preference in the Object order preference list. If you will be testing C++ applications, change the object order preference to C++ Recognition Order.
4. From the Object type list, select the object type to modify. The fixed set of recognition methods for the selected object type appears in the Recognition method order list in its last saved order.
5. Select an object recognition method in the list, and then click Move Up or Move Down. Changes made to the recognition method order take place immediately, and cannot be undone by the Cancel button. To restore the original DEFAULT order, click Default.
6. Click OK.

1. Identify the CLASS name of the window that corresponds to the object. You can use the Spy++ UTILITY in Visual C++ to identify the class name. You can also use the Robot Inspector tool by clicking Tools > Inspector.
2. In Robot, click Tools < General Options, and then click the Object Mapping tab.
3. From the Object type list, select the standard object type to be associated with the new object class name. Robot displays the class names already available for that object type in the Object classes list box.
4. Click ADD.
5. Type the class name you identified in step 1 and click OK.
6. Click OK.

To pause RECORDING:

• Click the Pause button on the GUI Record TOOLBAR. Robot indicates a paused state by:
• DEPRESSING the Pause button.
• Displaying Recording Suspended in the status bar.
• Displaying a check mark next to the Record > Pause command.

To resume recording:

• Click Pause again.
• ALWAYS resume recording with the application-under-test in the same state that it was in when you paused.

To pause recording:

To resume recording:

CLICK the STOP RECORDING BUTTON on the GUI Record toolbar.

Click the Stop Recording button on the GUI Record toolbar.

•  Do ONE of the following:
• . If the SCRIPT is open, click File &GT; Properties.
• . If the script is not open, click File > Open > Script. Select the script and click the Properties button.
• In the Script Properties dialog box, define the properties. For detailed information about an item, click the question mark NEAR the upper-right CORNER of the dialog box, and then click the item.
• Click OK.

• In ROBOT, click File > New > SCRIPT.
• Type a script name (40 CHARACTERS maximum) and, optionally, a description of the script.
• Click GUI.
• Click OK. Robot CREATES an empty script with the following lines:

SUB Main
Dim Result As Integer
'Initially Recorded: 01/17/05 14:55:53
'Script Name: GUI Script
End Sub

• Begin coding the GUI script.

Sub Main
Dim Result As Integer
'Initially Recorded: 01/17/05 14:55:53
'Script Name: GUI Script
End Sub

1. If necessary, open the SCRIPT by clicking File > Open > Script.
2. If you are currently debugging, click Debug > Stop.
3. In the Script window, click where you want to insert the new actions. Make sure that the application-under-test is in the appropriate state to begin recording at the text cursor position.
4. Click the Insert Recording button on the STANDARD toolbar. The Robot window minimizes by DEFAULT, or behaves as specified in the GUI Record Options dialog BOX.
5. Continue working with the application-under-test as you NORMALLY do when recording a script.

• If necessary, open the script by clicking File > Open > Script.
• If you are currently debugging, click Debug > Stop.
• In the Script window, click where you want to insert the feature. Make sure that the application-under-test is in the appropriate STATE to insert the feature at the text cursor position.
• Do ONE of the following:
• To add the feature without going into recording mode, click the Display GUI Insert Toolbar button on the Standard toolbar. The Robot Script window remains open.
• To start recording and add the feature, click the Insert Recording button on the Standard toolbar. The Robot window minimizes by default, or BEHAVES as specified in the GUI RECORD Options dialog box. Click the Display GUI Insert Toolbar button on the GUI Record toolbar.
• Click the appropriate button on the GUI Insert toolbar.
• Continue adding the feature as usual.

• If necessary, open a script by clicking File > Open> Script.
• Place the pointer on the line where you want to set a new breakpoint or clear an existing breakpoint. You can only place a breakpoint on a line where an SQABasic command is EXECUTED. BREAKPOINTS on comments, labels, and BLANK lines are not supported. Also, there are a very few commands that do not support breakpoints (for example, Dim and Sub).
• Click once to insert a BLINKING text cursor. (You can also highlight the entire line or any part of the line.)
• Click Debug > Set or Clear Breakpoint. If you set a breakpoint, Robot inserts a solid red circle in the left margin or highlights the line. If you clear a breakpoint, Robot removes the circle or highlighting.
• If you set a breakpoint, click Debug > Go. Robot executes as far as the breakpoint, and then DISPLAYS a yellow arrow in the left margin of that line or highlights the line.

Do one of the following:

• If RECORDING, click the Display GUI Insert Toolbar button on the GUI RECORD toolbar. . If editing, position the pointer in the script and click the Display GUI Insert Toolbar button on the Standard toolbar.
• Click the Start TIMER button on the GUI Insert toolbar.
• Type a timer NAME (40 characters maximum) and click OK. If you start more than one timer, make sure you give each timer a DIFFERENT name.
• Perform the timed activity.
• Immediately after performing the timed activity, click the Stop Timer button on the GUI Insert toolbar.
• Select a timer name from the list of timers you started and click OK.

Do one of the following:

• Do one of the following:
• If recording, click the Display GUI Insert TOOLBAR button on the GUI Record toolbar.
• If editing, position the pointer in the SCRIPT and click the Display GUI Insert Toolbar button on the STANDARD toolbar.
• Click the Write to Log button on the GUI Insert toolbar.
• After PLAYBACK, you can view logs and messages using TestManager.

• Click Tools Tools Tools Tools > Session Record Options Session Record Options Session Record Options Session Record Options.
• Click the Method Method Method Method tab, and click Network recording Network recording Network recording Network recording.
• Optionally, click the Method:Network Method:Network Method:Network Method:Network tab, and select the client/server pair that you will record. The default is to record all of the network TRAFFIC to and from your computer.
• Optionally, click the GENERATOR Filtering Generator Filtering Generator Filtering Generator Filtering tab to specify the network protocols to include in the SCRIPT that ROBOT GENERATES.

• Start Robot on the proxy computer.
• In the Proxy Administration dialog box, match up the proxy computer and PORT with each server to be used in the test.
• In the Method:Proxy Method:Proxy Method:Proxy Method:Proxy tab of the Session Record Options dialog box, match up each client with the server it will send requests to. Be sure to specify the actual server and not the proxy computer.
• Configure each client to send requests to the proxy computer, not to the server. For example, if the client will be sending requests to an Oracle database, use the Oracle client configuration software to specify the proxy computer’s ADDRESS and port NUMBER, not the server’s.
• On each client computer, a tester should start the client application and navigate to the POINT where RECORDING will begin.
• On the proxy computer, enable recording (File File File File > Record Session Record Session Record Session Record Session).
• With recording enabled, each tester at each client computer performs the transactions to record.
• When all transactions are complete, stop recording on the proxy computer.

If you are using network or proxy recording, and the computer that you want to use is not listed in the Method Network and Method Proxy tabs, you can add it to the list.

• Click Tools > Session Record Options
• Click the Method:Network tab or Method:Proxy tab, depending on WHETHER you are adding a computer for network or proxy recording.
• Click Manage Computers.
• Click New.
• In the Name BOX of the Computers group, type a name to associate with the network name of the computer that you are adding. You can assign any name up to 40 characters.
• Type the computer’s network name.
• Optionally, click Ping to make sure that the network name you just typed is CORRECT. If it is correct, -Successful Ping of network name- appears in the status bar.
• Select Client System to list this computer as a client. Select Server System to list this computer as a server. You can select both choices.
• Click Add.
• Take the following steps to use a port number with the network name. A port number is required for servers used in proxy recording:
• In the Ports Ports Ports Ports group, type a name to associate with the port number that you are adding. You can assign any name up to 40 characters.
• Type the port number to use with the computer’s network name.
• Click Apply, then OK .
• Click Close Close Close Close.

If you are using network or proxy recording, and the computer that you want to use is not listed in the Method Network and Method Proxy tabs, you can add it to the list.

• In ROBOT, click the Record Session button. Alternatively, click File > Record Session, or press CTRL+SHIFT+R.
• Ty p e t h e session name (40 characters maximum), or accept the default name. You will specify the script name when you finish recording the script. If you have not yet set your session recording options, do so now by clicking Options.
• Click OK in the Record Session - Enter Session Name dialog box. The following events occur:
• Robot is minimized (default behavior).
• The Session Record floating toolbar appears (default behavior). You can use this toolbar to stop recording, redisplay Robot, SPLIT a script, and insert features into a script.
• The Session Recorder icon appears on the taskbar. The icon blinks as Robot captures requests and responses.
• If the Start Application dialog box is displayed, provide the following information, and click OK:
• The path of the executable file for the browser or database application.
• Optionally, the working directory for any components (such as DLLs) that the client application NEEDS at runtime.
• Optionally, any arguments that you want to pass to the client application. The Start Application dialog box appears only if you are performing API recording, or if you are performing network or proxy recording and selected Prompt for application name on start recording in the General tab of the Session Record Options dialog box.
• Perform the transactions that you want to record. As the application sends requests to the server, notice the activity in the Session Recorder window. Progress bars and request statistics appear in the top of the window.
• If there is no activity in the Session Recorder window (or if the Session Recorder icon never blinks), there is a problem with the recording. Stop recording and try to find the cause of the problem.
• Optionally, insert features such as blocks and TIMERS through the Session Insert floating toolbar or through the Robot Insert menu.
•  Optionally, when you finish recording transactions, close the client application. With API recording, when you close the client, Robot ASKS whether you want to stop recording. If so, click Yes, and either name the session or click to ignore the recorded information in the Generating Scripts dialog box.
• Click the Stop Recording button on the Session Record floating toolbar.

• Click the Stop Recording BUTTON on the SESSION Record floating toolbar.
• In the Name of the just-recorded script BOX, type or select a name for the script that you just finished recording, or accept the default name.
• Click OK.

The error message appears in the status bar of the Generating Scripts dialog BOX like this: "Completed with warnings and/or errors"

To see the LIST of errors, click Details. If the TEXT of an error is truncated, you can either:

• Double-click the text to see the entire message.
• PRESS CTRL+C to COPY the text to the Clipboard.

The error message appears in the status bar of the Generating Scripts dialog box like this: "Completed with warnings and/or errors"

To see the list of errors, click Details. If the text of an error is truncated, you can either:

1. During RECORDING, click the Stop button on the Session RECORD floating toolbar.
2. In the Stop Recording dialog box, click IGNORE just-recorded INFORMATION.
3. Click OK in the Stop Recording dialog box.
4. Click OK to acknowledge that the session is being deleted.

If quick script development time is a PRIORITY - PERHAPS because TESTABLE builds are DEVELOPED daily, or because web content is UPDATED daily.

If quick script development time is a priority - perhaps because testable builds are developed daily, or because web content is updated daily.

• During recording, at the point where you want to end one script and begin a new one, click the Split Script BUTTON on the Session Record floating toolbar.
• Enter a NAME for the script that you are ending, or accept the DEFAULT name.
• Click OK.
• Repeat the previous steps as many TIMES as needed to end one script and begin another. 5. After you click the STOP Recording button to end the recording session, type or select a name for the last script you recorded, or accept the default name.

1. In ROBOT, CLICK Tools > Regenerate TEST Scripts from Session.
2. Click the name of the session to use.
3. Click OK to acknowledge that the regeneration operation is complete.

1. Start the TIMER (click Insert--Start Timer) just before you click the button to SEND the QUERY. This action inserts the VU emulation command start_time into the script.
2. Stop the timer (click Insert --Stop Timer) as soon as the results APPEAR. This action inserts the VU emulation command stop_time into the script.

A block is a set of CONTIGUOUS lines of CODE that you want to MAKE distinct from the REST of the script.

A block is a set of contiguous lines of code that you want to make distinct from the rest of the script.

A block begins with the comment. In the VU language, a block begins like this:

/* Start_Block "BlockName" */

•  ROBOT automatically starts a timer at the start of the block. In the VU language, the timer LOOKS like this:

start_time ["BlockName"] _fs_ts;

Typically, the start_time emulation command is INSERTED after the first action, but with an argument to use a read-only variable that refers to the start of the first action.

•  The ID of EVERY emulation command in a block is constructed the same way that is, by the block name followed by a unique, three-digit autonumber. For example, in the VU language:

http_header_recv ["BlockName002"] 200;

When you end a block, command IDs are constructed as they were before you started the block. For example, if the last command ID before the block was Script025, the next command ID after the block will be Script026.

•  A block ends with a stop_time command plus a comment. For example, in the VU language:

stop_time ["BlockName"]; /* Stop_Block */

A block begins with the comment. In the VU language, a block begins like this:

/* Start_Block "BlockName" */

start_time ["BlockName"] _fs_ts;

Typically, the start_time emulation command is inserted after the first action, but with an argument to use a read-only variable that refers to the start of the first action.

http_header_recv ["BlockName002"] 200;

When you end a block, command IDs are constructed as they were before you started the block. For example, if the last command ID before the block was Script025, the next command ID after the block will be Script026.

stop_time ["BlockName"]; /* Stop_Block */

• To associate the block and timer names with the emulation command that performs the transaction.
• To include the block name in TestManager REPORTS, thus ENABLING you to filter the reports with the block name.
• To make the script EASIER to read, and to provide an immediate context for a LINE within the block through command IDs.

1. If the Session INSERT floating toolbar is not already displayed, click the Insert button on the Session Record floating toolbar.
2. Click the Start Block button at that point in the script where you want the block to begin for example, just before you start to record a transaction.
3. Type the block name. Robot uses this name as the prefix for all command IDs in the block. The maximum number of characters for a command ID prefix is SEVEN.
4. Click OK.
5. Record all of the CLIENT REQUESTS in the block.
6. Click the Stop Block button to end the current block, and click OK.
7. Continue recording the other sections of the script. When you start and stop a block during recording, the commands are reported as annotations in the Annotations window.

A synchronization POINT lets you coordinate the ACTIVITIES of a number of virtual testers by PAUSING the execution of each tester at a PARTICULAR point

A synchronization point lets you coordinate the activities of a number of virtual testers by pausing the execution of each tester at a particular point

By synchronizing virtual TESTERS to perform the same activity at the same time, you can make that activity occur at some particular point of interest in your test. Typically, synchronization points that you INSERT into SCRIPTS are used in CONJUNCTION with timers to DETERMINE the effect of varying workload on the timed activity.

By synchronizing virtual testers to perform the same activity at the same time, you can make that activity occur at some particular point of interest in your test. Typically, synchronization points that you insert into scripts are used in conjunction with timers to determine the effect of varying workload on the timed activity.

1. FUNCTIONAL TESTING.
2. SESSIONS for PERFORMANCE testing.

When creating a DATAPOOL, you specify the kinds of DATA (called data types) that the script will send for example, customer names, addresses, and unique order numbers or product names. When you finish DEFINING the datapool, TestManager automatically generates the number of rows of data that you specify.

When creating a datapool, you specify the kinds of data (called data types) that the script will send for example, customer names, addresses, and unique order numbers or product names. When you finish defining the datapool, TestManager automatically generates the number of rows of data that you specify.

Rational SiteCheck to test the structural integrity of your intranet or World Wide Web site.SiteCheck is designed to help you view, track, and maintain your rapidly changing site.

Use SiteCheck to:

• Visualize the structure of your Web site and display the relationship between each page and the rest of the site.
• Identify and analyze Web pages with active content, such as forms, JAVA, JavaScript, ActiveX, and Visual Basic Script (VBScript).
• Filter information so that you can inspect specific file types and defects, including broken LINKS.
• Examine and edit the source code for any Web page, with color-coded text.
• Update and repair files using the integrated editor, or configure your favorite HTML editor to perform MODIFICATIONS to HTML files.
• Perform comprehensive testing of secure Web sites. SiteCheck provides Secure Socket LAYER (SSL) support, proxy server configuration, and support for multiple password realms.

Rational SiteCheck to test the structural integrity of your intranet or World Wide Web site.SiteCheck is designed to help you view, track, and maintain your rapidly changing site.

Use SiteCheck to: