Explore topic-wise InterviewSolutions in .

It really depends on what you are testing. For complex web sites (pages not static, multiple browser windows, JavaScript), I would say SILKTEST works MUCH better, In general, Visual Test is new to the web browser game. If it is a Win32 app that you are testing. VT is *much* faster than Silk and the CODE compiles down to a binary file that can easily be put on different test systems. This is a *big* plus for Visual Test. SilkTest will make the declaration file for you, so this saves allot of time. In VT, you have to make the declarations yourself but if the product isn’t huge, this isn’t a big deal. SilkTest also is great a capturing text on a page (either web or Win32 based). VT, last 1 CHECKED, lacked this function. It is a useful function for verification.

SilkTest also has a nice verification function that it makes (a few keystokes and it’s done). Real easy to change some of the hardcoded data here with data from a text file or other place. Nice for doing report verification where the layout is the same, but the data is different. COST is another big issue. SilkTest is low in price, Silk quite high. So, again, it depends on your needs, what and how you will be testing it.

It really depends on what you are testing. For complex web sites (pages not static, multiple browser windows, JavaScript), I would say SilkTest works much better, In general, Visual Test is new to the web browser game. If it is a Win32 app that you are testing. VT is *much* faster than Silk and the code compiles down to a binary file that can easily be put on different test systems. This is a *big* plus for Visual Test. SilkTest will make the declaration file for you, so this saves allot of time. In VT, you have to make the declarations yourself but if the product isn’t huge, this isn’t a big deal. SilkTest also is great a capturing text on a page (either web or Win32 based). VT, last 1 checked, lacked this function. It is a useful function for verification.

SilkTest also has a nice verification function that it makes (a few keystokes and it’s done). Real easy to change some of the hardcoded data here with data from a text file or other place. Nice for doing report verification where the layout is the same, but the data is different. Cost is another big issue. SilkTest is low in price, Silk quite high. So, again, it depends on your needs, what and how you will be testing it.

For automating a web based APPLICATION using JSP, there is a search textbox, a “Search BUTTON, a listbox, a “OK” button, and a “Cancel” button. The “OK’ button remains disabled by default. I NEED to enter a value in search textbox. CLICK on search button, select the resultant value in the listbox and then the “OK” button is enabled. Problem: When all this is automated. SILKTEST finds the OK button still disabled after selecting the resultant value, though the button is enabled Put one statement before clicking on save button BrowserPage.flushcache( ).

For automating a web based application using JSP, there is a search textbox, a “Search button, a listbox, a “OK” button, and a “Cancel” button. The “OK’ button remains disabled by default. I need to enter a value in search textbox. click on search button, select the resultant value in the listbox and then the “OK” button is enabled. Problem: When all this is automated. Silktest finds the OK button still disabled after selecting the resultant value, though the button is enabled Put one statement before clicking on save button BrowserPage.flushcache( ).

It may be programming error, since DB next is USED to go the next DATA in the table, MAYBE it is getting to the LAST VALUE, and not getting any value there.

It may be programming error, since DB next is used to go the next data in the table, maybe it is getting to the last value, and not getting any value there.

SILK cannot be INTEGRATED with QUALITY CENTRE.

Silk cannot be integrated with Quality centre.

1. Try to declare the tag with prior text.
2. Try to declare the tag with LOCATION ... meaning #3 (This MEANS that this is the 3rd dynamic text in the page).
3. You can try to GetText( )

1. if you are TALKING about WEBPAGES, you can USE BrowserPage.FlushCache( ) METHOD.
2. You can use multitag CONCEPT

You don’t as there are no free downloadable SilkTest TRIAL versions. You MUST contact Segue sales and they will SET you up with an account after you can demonstrate both need and desire to purchase, or at least evaluate. You then download SilkTest USING that account.

You don’t as there are no free downloadable SilkTest trial versions. You must contact Segue sales and they will set you up with an account after you can demonstrate both need and desire to purchase, or at least evaluate. You then download SilkTest using that account.

Share the FOLDER containing the script very SIMPLE. You can run the script from your machine and target MAY be some other machine USING connect( ).But somebody else cannot access unless you share or TRY other options.

Share the folder containing the script very simple. You can run the script from your machine and target may be some other machine using connect( ).But somebody else cannot access unless you share or try other options.

.opt file is used to SET the options
Say in your script you set the option

For few options you can set in your script If you are going to set more number of options, it is better to set in an opt file and USE that opt file.
The above example is for Agent option. There are other options E,g GENERAL, Runtime etc which you have to set in the .opt file.

.opt file is used to set the options
Say in your script you set the option

For few options you can set in your script If you are going to set more number of options, it is better to set in an opt file and use that opt file.
The above example is for Agent option. There are other options e,g General, Runtime etc which you have to set in the .opt file.

.VTP files are PROJECT files HELP tells EXTENSIVELY on it.

.vtp files are project files help tells extensively on it.

You can, but there are a few steps that need to be done.
You need to USE Organizer to do this. There you can re-run the same testcases but at the top open a different opt (options) FILE. You have to SAVE these 2 opt files though after you set the runtime with Netscape, save the 1ST ONE and save another after you set it up with IE.

You can, but there are a few steps that need to be done.
You need to use Organizer to do this. There you can re-run the same testcases but at the top open a different opt (options) file. You have to save these 2 opt files though after you set the runtime with Netscape, save the 1st one and save another after you set it up with IE.

YES you can, but the location may vary from 1 system to another from one resolution to another. You can use the .GetRect( ) method. Or you can use the VERIFY properties (HOLD ctrl-shift while recording testcases) and select the location for a property.

Yes you can, but the location may vary from 1 system to another from one resolution to another. You can use the .GetRect( ) method. Or you can use the verify properties (hold ctrl-shift while recording testcases) and select the location for a property.

1. MAKE sure the Result window is open with result file.
2. Click Results/Pass/Fail REPORT. The Pass/Fail Report dialog box shows up.
3. SELECT an attribute on which you want the report to be BASED on. For example: Component.
4. Click the Generate button.
5. SilkTest GENERATES a report in the Pass/Fail Report dialog box.
6. You can print or export the report.
7. Click the Close button to close the Pass/Fail Report dialog box.

You can use the following

You need to do some trickery to parse and get the IP string.

You can use the following

You need to do some trickery to parse and get the IP string.

1. use ENVIRONMENT VARIABLE as suggested by another member of this GROUP.
2. copy the variable to the clipboard, every automation TOOL has a way to write and read content from clipboard which does not affect scope of the SCRIPT.

In your TestCaseExit( ) FUNCTION you can incorporate like

In your TestCaseExit( ) function you can incorporate like

1. IDENTIFY the PROCESS HANDLE and
2. kill it First child and then the MainWindow.

USE GetCaption( ) METHOD

Use GetCaption( ) method

In Automation: creating TEST scripts involves basically two step:

1. Creating Test Data for all test CASES.
2. Writing scripts for automating the test cases.

The first steps, is the outcome of analysis of what all data is required for all of your TESTCASES to be executed. These all should be COLLECTED and scripts to be WRITTEN so that TEST DATA is ready.
The second steps, is basically the test case execution steps automation.

In Automation: creating test scripts involves basically two step:

The first steps, is the outcome of analysis of what all data is required for all of your testcases to be executed. These all should be collected and scripts to be written so that TEST DATA is ready.
The second steps, is basically the test case execution steps automation.

You can USE Clipboard functions. Get All the contents by Ctrl+a & ctrl+C. Then PARSE the LIST of STRING.

You can use Clipboard functions. Get All the contents by Ctrl+a & ctrl+C. Then parse the List of string.

DBTester is a testing tool that allows you to access a database server directly through ODBC DRIVERS. If your APPLICATION is a database driven application, you can perform a test through the application UI, and verify data changes in the database with DBTester without using the application UI.

DBTester is a testing tool that allows you to access a database server directly through ODBC drivers. If your application is a database driven application, you can perform a test through the application UI, and verify data changes in the database with DBTester without using the application UI.

DB_Connect (con_string).

DB_Connect (con_string).

ANSWER : Agent.SetOption (OPT_VERIFY_EXPOSED, TRUE)
Do your CLICK EVENT
Agent.SetOption (OPT_VERIFY_EXPOSED, FALSE)

Very EASILY FOUND in the online help under:

1. LINE BREAKS in code
2. line continuation CHARACTER

Very easily found in the online help under:

Answer : BrowserPage. SetActive ( )
Clipboard.SetText ( )
BrowserPage. TypeKeys (“<Ctrl-a>”)
BrowserPage.TypeKeys (“<.Ctrl-c>”)
LIST of string lsText =Clipboard.GetTet ( ) //holds the BROWSER page content

Automation Framework is a discipline and should have proper design/architecture. You can understand and implement. Automation Framework should have some of following things.

1. AUT Specific libraries
2. Tool wrapper function libraries.
3. Execution Engine (Script Execution should be DERIVED based on given test data) - Data DRIVEN
4. Results reporting mechanisms (PASS & FAIL for each testcases/procedures and compiled results for all. It would be better, if it captured AUT’s snapshots)
5. Planning for long term automation.
6. Keeping GUI objects info/declarations dynamically or static.
7. Planned approach of unattended execution.

Also framework design differs by tool, scripting LANGUAGES and type of AUT etc,. Now a days, people are using PERL, PYTHON, TCL/TK for CLI automation. This design will vary much from GUI specific tool automation’s design (QTP, WIN runner, Silktest,Robot and QARun etc).

Automation Framework is a discipline and should have proper design/architecture. You can understand and implement. Automation Framework should have some of following things.

Also framework design differs by tool, scripting languages and type of AUT etc,. Now a days, people are using PERL, PYTHON, TCL/TK for CLI automation. This design will vary much from GUI specific tool automation’s design (QTP, Win runner, Silktest,Robot and QARun etc).

Same script can be used. Only URLs need to be UPDATED. MIGHT be some TAGS ALSO but you can manage them USING wild characters or multi-tag.

Same script can be used. Only URLs need to be updated. Might be some tags also but you can manage them using wild characters or multi-tag.

SILKTEST is not a load testing tool - it is a functional testing tool. You could do a crude load test by having SILK on multiple boxes and then running each one at the same time - but that is very crude.
You need Silk PERFORMER or Load Runner or some other load testing tool for doing load testing.

SilkTest is not a load testing tool - it is a functional testing tool. You could do a crude load test by having Silk on multiple boxes and then running each one at the same time - but that is very crude.
You need Silk Performer or Load Runner or some other load testing tool for doing load testing.

YES, you can Except that you will need MAC RUNTIME for JAVA (MRJ).

Yes, you can Except that you will need Mac Runtime for Java (MRJ).

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. SilkTest runs all the marked testcases.
6. Do not touch mouse or keyboard, to avoid interrupting the test case execution.
7. SilkTest finishes executing the testcase. The Results window shows up with the execution result.
8. Review the execution result.

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. Click Run/Run All TESTS menu. SilkTest 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. SilkTest finishes executing the testcase. The Results WINDOW shows up with the execution result.
5. Review the execution result.

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. SilkTest starts to run the test CASE.
5. Do not touch mouse or keyboard, to avoid interrupting the test case execution.
6. SilkTest finishes executing the testcase. The Results window shows up with the execution result.
7. Review the execution result.

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

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. SilkTest starts to run the test case.
5. Do not touch mouse or keyboard, to avoid interrupting the test case execution.
6. SilkTest finishes executing the testcase. The Results window shows up with the execution result.
7. Review the execution result.

A test script file can store multiple test cases. You can run a testcase from a test script file:

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 objets.
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 recording.

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

1. Make SURE your testplan 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 test case script file. For example, LoginTest.t.
7. Click the “Testcases” button, to select a testcase recored in the specified script file.
8. Click OK to close the Testplan Detail dialog box.

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.

1. Each test case MUST be INDEPENDENT of other test cases.
2. Each test case has a SINGLE test purpose.
3. Each test case should START from a BASE state and returning to the same base state.

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.

The DefaultBaseState is a starting point of TEST project from which the Recovery SYSTEM can AUTOMATICALLY restart your test cases when test cases FAIL to continue.

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

1. RUN SilkTest.
2. Open Internet Explorer (IE).
3. Enter the URL of the Web application.
4. Leave the IE WINDOW with the Web application. Don’t minimize the IE window.
5. To BACK to SilkTest window.
6. SELECT Basic Workflow bar.
7. Click Enable Externsions on the Workflow bar.
8. The Enable Extensions dialog will show up. Your Web application running in the IE window will LISTED in the dialog box.
9. Select your Web application and click Select.
10. The Extension Settings dialog will show up. Click OK to enable the DOM browser extension.

If your Web application has PAGES other than the home page, you should also record their page objects into the test frame:

1. Make sure your Web browser is active and showing another page of your Web application.
2. Make sure SilkTest is RUNNING.
3. Click File/Open menu.
4. Select your test frame file. For example: HomeFrame.inc.
5. Click OK to open the test frame.
6. Click Record/Window DECLARATIONS menu. The Record Window Declarations dialog box shows up.
7. Click your Web application window. Web page objects are RECORDED in the Record Window Declarations dialog box.
8. Press Ctrl+Alt to pause the recording.
9. Click “Paste to Editor” button. All recorded objects will be inserted into the test frame.
10. Repeat this for other Web pages, if NEEDED.

If your Web application has pages other than the home page, you should also record their page objects into the test frame:

Multi-tagging is a technique used by the DOM browser extension to IDENTIFY a Web page UI object. WHENEVER possible, DOM extension inserts more than one TAG into the object identifier in following FORMAT:
Browser.BrowserChild(“page_title”).html_class(“caption_tag|#index_tag|window_tag”)

1. “caption_tag” is the CAPTION of the HTML element.
2. “#index_tag” is the index of this HTML element, counting from the beginning of this page of the same class of HTML elements.
3. “window_tag” is the window identifier.

Multi-tagging is a technique used by the DOM browser extension to identify a Web page UI object. Whenever possible, DOM extension inserts more than one tag into the object identifier in following format:
Browser.BrowserChild(“page_title”).html_class(“caption_tag|#index_tag|window_tag”)

The DOM browser extension uses the FOLLOWING syntax for WEB UI objects:
Browser.BrowserChild(“page_title”).html_class(“object_tag”)

1.  “page_title” is the TITLE of the Web page, DEFINED by the HTML “TITLE” tag.
2.  “object_tag” is the label of the HTML element. How a HTML element is labeled depending on the type of HTML element.

The DOM browser extension uses the following syntax for Web UI objects:
Browser.BrowserChild(“page_title”).html_class(“object_tag”)

A test frame is a text file, which records the following types of information for a Web application:

1. Comment: Commentary information.
2. wMainWindow: A string constant to identify your application’s home page.
3. Home page WINDOW: An object of CLASS BrowserChild window that holds application home page.
4. sLocation: The URL of the your application’s home page.
5. sUserName and dPassword: User name and password if needed to LOGIN to your Web application.
6. BrowserSize: A pair of values to INDICATE the size of the browser window.
7. Home page objects: A LIST of all objects on the home page, such as HtmlImage, HtmlText, HtmlLinks, etc.

A test frame is a text file, which records the following types of information for a Web application:

1. Make sure your Web browser is active and showing your Web application HOME page. Do not minimize this Web page window.
2. Make sure your test project is OPEN.
3. Click File/New menu. The New dialog box shows up.
4. Select the Test Frame radio button.
5.  Click OK. The New Test Frame dialog box shows up with a list all active Web applications.
6. Select your Web application.
7. Enter a test frame NAME. For EXAMPLE: HomeFrame.inc.
8. REVIEW the window name. It should be the HTML title your Web application. You can rename it, if needed.
9. Click OK to close the New Test Frame dialog box.
10. Click File/Save menu.

A test frame is a file that contains information about the application you are TESTING. Information stored in a test frame will be used as references when SilkTest RECORDS and EXECUTES testcases. A test frame is stored in an include file with file EXTENSION .inc.

A test frame is a file that contains information about the application you are testing. Information stored in a test frame will be used as references when SilkTest records and executes testcases. A test frame is stored in an include file with file extension .inc.

1. Make sure your TESTPLAN is open.
2. Click on the test case for which you want to assign an attribute value.
3. Click Testplan/Detail menu. The Testplan Details dialog box SHOWS up.
4. Click the Test Attribute tab.
5. Click the COMPONENT field. The dropdown list shows up with all values of “Component”.
6. Select ONE of the values in the dropdown list.
7. Click OK.

TESTPLAN attributes are stored in the testplan initialization file, testplan.ini, in SilkTest installation DIRECTORY.

Testplan attributes are stored in the testplan initialization file, testplan.ini, in SilkTest installation directory.

You must define values for a testplan before using it:

1. Make sure your TEST project is open.
2. Click Testplan/Define Attributes menu. The Define Attributes dialog box SHOWS up. You should see predefined default attributes and other attributes DEFINED by yourself.
3. Select an attribute. For example, “Component”. The Values box should be empty.
4. Enter a value in Add box. For example, “Catalog”.
5. Click Add. Value “Catalog” should be inserted into the Values box.
6. Repeat the last TWO steps to add more values.

You must define values for a testplan before using it:

SilkTest offers you 3 PREDEFINED default ATTRIBUTES:

1. Category: The type of testcase or group of testcases. For example, you can use this attributes to CATEGORIZE your test groups as “Boundary VALUE tests”, “Navigation tests”, etc.
2. Component: The name of the application MODULES to be tested.
3. Developer: The name of the QA engineer assigned to develop the testcase or group of testcases.

SilkTest offers you 3 predefined default attributes: