Testing Interview Questions

1. How to create a verification point?

1. Do one of the following: . If recording, click the display GUI Insert Toolbar on the GUI Record toolbar.
. If editing, postion the pointer in the script and click the display GUI Insert Toobar button on the standard toolbar.
2. Click a verification point button on the GUI Insert toolbar.
3. In the verification point name dialog box, edit the name as appropriate. The name can be a maximum of 20 characters.
4. Optionally, set the wait state options. For information, see the next section, setting a wait state for a verification point.
5. Optionally, set the expected result option.
6. Click OK.

2. How to add a wait state when creating a verification point?

1. Start to create the verification point.
2. In the verification point name dialog box, select apply wait state to verification point.
3. Type values for the following options:Retry every - how often Robot retries the verification point during playback. Robot retries until the verification point passes or until the timeout limit is reached.
Timeout after - The maximum amount of time that Robot waits for the verification point to pass before it times out. If the timeout limit is reached and the verification point has not passed, Robot enters a failure in the log. The script playback either continues or stops based on the setting in the Error Recovery tab of the GUI Playback Options dialog box.

3. How to set the expected result when creating a verification point?

1. Start to create a verification point.
2. In the verification point name dialog box, click Pass or Fail.

4. What are two verification points for use with web sites?

1. Use the web site scan verification point to check the content of your web site with every revision and ensure that changes have not resulted in defects.
2. Use the web site compare verification point to capture a baseline of your web site and compare it to the web site at another point in time.

5. How to select the object to test?

1. Start creating the verification point.
2. In the verification point name dialog box, type a name and click OK to open the select object dialog box.
3. Do one of the following:
.select automatically close dialog box after object selection to have the select object dialog box close after you select the object to test.
.Clear automatically close dialog box after object selection to have the select object dialog box reappear after you select the object to test. You will need to click ok to close the dialog box. To select a visible object directly from the application, continue with step 4. To select an object from the list of all objects on the desktop, skip to step 5.
4. To select a visible object directly from the application, drag the object Finder tool over the object and release the mouse button.
5. To select a visible or hidden object from a list of all objects on the windows desktop, click Browse to open the object List dialog box. Select the object from the list and click OK.

1. How to create a datapool?

When creating a datapool, you specify the kinds of data (called datatypes) 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.

2. How to analyz results in the log and comparators?

You use Testmanager to view the logs that are created when you run scripts and schedules.

Use the log to:
View the results of running a script, including verification point failures, procedural failures, aborts and any additional playback information. Reviewing the results in the log reveals whether each scripts and verification point passed or failed.

Analyze the results of verification points to determine why a script may have failed.

Robot includes 4 comparators:

.Object Properties Comparator
.Text Comparator
.Grid Comparator
.Image Comparator

Rational Sitecheck

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.

3. What is a verification point?

A verification point is a point in a script that you create to confirm the state of an object across builds of the application-under-test.

Verification point type

1. Alphanumeric:
Captures and tests alphanumetric data in windows objects that contain text, such as edit boxes, check boxes, labels, push buttons, radio buttons, toolbars, and windows (captions).
2. Clipboard:
Captures and compares alphanumetric data that has been copied to the clipboard.
3. File Comparison:
Compares two specified files during playback.
4. File Existence:
Verifies the existence of a specified file during playback.
5. Menu:
Captures and compares the menu titile, menu items, shortcut keys, and the state of selected menus.
6. Module Existence: Verifies whether a specified module is loaded into a specified context (process), or is loaded anywhere in memory.
7. Object data: Captures and compares the data inside standard windows objects.
8. Object properties : Captures and compares the properties of standard windows objects.
9. Region Image: Captures a region of the screen as a bitmap.
10. Website compare: Captures a baseline of a web site and compares it to the web site at another point in time.
11. Website scan: Checks the contents of a web site with every revision and ensures that changes have not resulted in defects.
12. Window Existence: Verifies the existence and status of a specified window during playback.
13. Window Image: Captures a window as a bitmap.

1. What is Rational Robot?

Rational Robot is a complete set of components for automating the testing of Microsoft Windows client/server and internet applications. The main component of Robot lets you start recording tests in as few as two mouse clicks. After recording, Robot plays back the tests in a fraction of the time it would take to repeat the actions manually.

2. Which products does Rational Robot Installs with?

Clear Quest - Change-Request management tool that tracks and manages defects and change requests through the development process.
Rational Log Viewer and Comparators - are the tools you use to view logs and test results created when you playback scripts.
Rational Robot - is the tool that you used to develop both GUI and VU (Virtual user) scripts.
SQL Anywhere - A database product to help create, maintain and run your Rational repositories.
Rational Test Manager - is the component that you use to plan your tests, manage your test cases, and run queries and reports.
Rational Administrator - Is the component that you use to create and manage repositories.
Rational Site Check - Is the component that you use to test the structural integrity of your intranet or WWW site.
Additional Rational Products available only with Rational Suite Test Studio or Performance Studio.
Test factory - Component based testing tool that automatically generates Test Factory scripts according to the applications navigational structure.

Diagnostic Tools

Rational Purify - Is a comprehensive C/C++ run time error checking tool.
Rational Visual Quantify - Is an performance prolofier that provides performance analysis of a product, to aid in improving performance of the code.
Rational Visual Pure Coverage - Is a customizable code coverage analysis tool that provides detailed application analysis and ensure that all code has been exercised.
Performance Studio - Tools used for automating performance tests on client/server systems.
Rational Synchronize - Tool used to share data from rational rose, require pro and rational robot.
Requisite Pro - Create, define requirements for your development process. The baseline version is incorporated into Rational Team Test. The full version in Rational Studio Test Suite allows you to customize requirements databases, and additional features like traceability, change notification and attribute management.

3. What is Rational Administrator?

Use the Rational Administrator to:
1. create and manage projects.
2. create a project under configuration management.
3. create a project outside of configuration management.
4. Connect to a project.
5. See projects that are not on your machine (register a project)
6. Delete a project.
7. Create and manage users and groups for a Rational Test datastore.
8. Create and manage projects containing Rational Requisite Pro Projects and Rational Rose models.
9. Manage security privileges for the entire Rational project.
10. Configure a SQL anywhere database server.

4. What two kind of GUI scripts using Rational Robot?

1. Functional testing
2. Sessions for performing testing.

I. Perform full functional testing. Record and play back scripts that navigate through your application and test the state of objects through verifications points.

II. Perform full performance testing. Use Robot and Test Manager together to record and play back sessions that help you determine whether a multi-client system is performing within user-defined standards under varying loads.

III. Create and edit scripts using the SQA Basic and VU scripting environments. The Robot editor provides color-coded commands with keyword help for powerful integrated programming during script development. (VU scripting is used with sessions in performance testing.)

IV. Test applications developed with IDEs such as Java, HTML, Visual Basic, Oracle Forms, Delphi and PowerBuilder. You can test objects even if they are not visible in the application’s interface.

Collect diagnostic information about an application during scripts playback. Robot is integerated with Rational Purify, Rational Quantify, and Rational Pure Coverage. You can play back scripts under a diagnostic tool and see the results in the log.

5. What is datapool?

A datapool is a source of variable test data that scripts can draw from during playback.

1. How to run a test case from a test script file?

A test script file can store multiple test cases. You can run a testcase from a test script file:
1. Open the test script file.
2. Select the test case in the test file.
3. Click Run/Testcase menu. the Run testcase dialog box shows up.
4. Click the run button. Silk test starts to run the test case.
5. Do not touch mouse or keyword, to avoid interrupting the test case execution.
6. Silk test finishes executing the testcase. the Result window shows up with the execution result.
7. Review the execution result.

2. How to run a test case from a testplan file?

If a testcase is linked to a testplan, you can run it from the testplan:

1. open the testplan.
2. Select the test description line which has the testcase linked.
3. Click Run/Testcase menu. The Run Testcase dialog box shows up.
4. Click the Run button. Silk test starts to run the test case.
5. Do not touch mouse or Keyword, to avoid interrupting the test case execution.
6. Silk test finishes executing the testcase. The results window show up with the execution result.
7. Review the execution result.

3. How to run all test cases in a test plan?

1. Open the testplan
2. Click Run/Run All Tests menu. Silk test starts to run all the test cases in the testplan.
3. Do not touch mouse or keyboard, to avoid interrupting the test case execution.
4. Silk test finishes executing the testcase. The Results window shows up with the execution result.
5. review the execution result.

4. How to select a group of testcases in a testplan to run?

Usually, a testplan contains a big number of test cases. For some reason, you don’t want to run all test cases in the testplan. You want to select a group of test cases and run them:

1. Open the testplan.
2. Select the test description line(linked to the testcase) to mark.
3. Click Testplan/mark menu. the selected test description line is marked.
4. Repeat this process to select more linked testcases.
5. Click the Run/Run Marked Tests menu. Silk test runs all the marked testcases.
6. Do not touch mouse or keyboard, to avoid interrupting the test case execution.
7. Silk test finishes executing the testcase. The results window shows up with the execution result.
8. Review the execution result.

1. What is DefaultBaseState?

The DefaultBaseState is a starting point of test project from which the Recovery System can automatically restart your test cases when cases fail to continue.

2. How to test your DefaultBaseState?

1. Close your Web application and other Web browsers.
2. make sure your test frame is open.
3. Click Run/Application State menu. The Run Application State dialog box shows up with a list of states. One of them should be defaultBaseState.
4. Select DefaultBaseState.
5. Click Run button. The Runtime status dialog box shows up. And the Results File dialog box shows up too.
6. You should see no error message in the results file.

3. What are the important aspects of a test case?

1. Each test case must be independent of other test cases.
2. Each test case have a single test purpose.
3. Each test case should start from a base state and returning to the same base time.

4. What is the standard flow of execution of a test case?

1. Starting from the base state.
2. Drive the application to the state where the expected result should occur.
3. Verify the actual result against the expected result.
4. Declare the test case as passed or failed.
5. Return to the base state.

5. How to record a test case?

1. Run Silk Test.
2. Click Option/Runtime menu. the Runtime options dialog box shows up.
3. edit the use files field to include your test frame file and the explorer.inc file. For example: ….\HomeFrame.inc, extend\explorer.inc.
4. Make sure IE 5.x DOM is selected.
5. Click OK to close the Runtime Options dialog box.
6. Open your test project.
7. Click Record/Testcase menu. The record testcase dialog box shows up.
8. Name your test case. For example: LoginTest.
9. Select DefaultBasestate in the Application State dropdown list.
10 Click start Recording button. The Record Testcase dialog box closes. Your Web application will be automatically started by Silk test, based on the information in test frame file. Silk test Editor window closes. The Record status dialog box shows up.
11. Continue to use your web application. Silk test records everything you did on your application.
12. Click the “Done” button on the Recording status dialog box to stop recording. The Recording status dialog box closes. the Record Testcase dialog box shows up again.
13. Click paste to Editor. Silk Test will insert the recorded activities as 4test statements into a script file. The Record Testcase dialog closes.
14. Click File/Save Menuto save the script file. You can enter a script file name. For example, LoginTest.t.

6. How to include a test case into a testplan?

1. Make sure your test plan is open.
2. Enter a test description into your testplan. For example, “Test login process”.
3. Select this test description.
4. Click Testplan/detail menu. The testplan detail dialog box shows up.
5. Click the test execution tag on the testplan detail dialog box.
6. Click the “scripts” button to browse and select a testcase script file. For example, LoginTest.t
7. Click the “Testcases” button, to select a testcase recorded in the specified script file.
8. Click OK to close the Testplan Detail box.

7. How record a test case into a testplan automatically?

Test cases can recorded first without a testplan, then included into a testplan later. Test cases can also be recorded into a testplan directly:
1. Make sure your testplan is open.
2. Enter a test description into your testplan. For example, “Test change password”.
3. Select this test description.
4. Click Record/Testcase menu.
5. Enter a name for the script file.
6. Click open. the Record Testcase dialog box shows up.
7. Enter a testcase name in the Testcase Name field.
8. Select defaultbasestate in the application state dropdown list.
9. Click start recording button. The record Testcase dialog box closes. Your web application will be automatically sarted by silk test, based on the information in test frame file. Silk test editor window cloases. the record status dialog box shows up.
10. Continue to use your web application. Silk test records everything you did on your application.
11. Click the “Done” button on the Recording status dialog box to stop recording. The recording status dialog box closes. The record testcase dialog box shows up again.
12. Click Paste to Editor. Silk test will insert the recorded activities as 4Test statements into a script file. The record Testcase dialog closes.
13. Click File/Save menu to save the script file. You can enter a script file name. For example, changePaswordTest.t.

8. How to define an object verification in a test case?

While recording a test case, you can define verification points to verify UI objects:

1. Make sure you are in the process of recording a testcase.
2. make sure the Record status dialog box is on the screen.
3. Make sure your recording reached the web page that has the UI object you want to verify.
4. Click the background(blank area) of the web page. Do not click any objects on the page.
5. Press Ctrl-Alt. The verify window dialog box shows up. All the objects on the current web page are listed on the verify window dialog box.
6. Select the object to be verified in the object list. Un-select all other objects.
7. Select the property to be verified in the property list. Un-select all other properties.
8. Click OK to close the verify window dialog box.
9. Continue your recordings.