Virtual Object (VO) browser extension is a SilkTest add-on component for testing Web applications. VO browser extersion uses sophisticated pattern recognition techniques to identify browser-rendered objects. The VO extension sees Web pages as they appear visually; it does not read or recognize HTML tags in the Web application code. Instead, the VO extension sees the objects in a Web page; for example, links, tables, images and compound controls the way that you do, regardless of the technology behind them.
Home Applications Programs SilkTest
“SilkTest Interview Questions and Answers will guide us now that SilkTest is an automation tool for testing the functionality of enterprise applications in most versions of Windows, Solaris 9 and 10, and Red Hat Enterprise Linux WS 2.1 and 3.0, s learn SilkTest or get preparation for the job of SilkTest with the help of this SilkTest Interview Questions with Answers guide”
146 SilkTest Questions And Answers
2⟩ I have recently encounterd a problem using Silk Test V3. When I record selecting a Menu Item it correctly records eg. Product.File.Exit.Pick() But when I play it back it just selects the File Menu and fails to select Exit. The File Menu is not dropped, it is just highlighted. The application is written in Visual C++ and is running on NT 4. A couple if the menu items to work but that is about 2 out of 15 items. I can work around the problem using the menu short cut keys but would prefer to be simulating using the mouse in some test cases. Any ideas?
I have run into this problem before and it turned out to be a focus problem in the AUT. First, we need to understand how QAP/Silk selects menu items. It doesn't really use the mouse. It uses the key to highlight the menu bar and then arrows to the desired menu item. Try something out: Drive your application to the state before the menu selection. Now manually type F-10 or Alt and see if the menu highlights and allows you to arrow to the menu item. I'm guessing that it is probably a ChildWin or DialogBox that is really holding the focus and not passing the keyboard events to the MainWin. If this is the case, you need to explain to the developers that they need to enable this so that you can continue with your automated testing. A trick around this problem is to do a YourProduct.Click () to force the focus to the MainWin and then do the menu selection (YourProduct.File.Exit.Pick())
SilkTest Host is a SilkTest component that manages and executes test scripts. SilkTest Host usually runs on a separate machine different than the machine where AUT (Application Under Test) is running.
SilkTest is a software testing automation tool developed by Segue Software, Inc.
4Test is a test scripting language used by SilkTest to compose test scripts to perform automated tests. 4Test is an object-oriented fourth-generation language. It consists of 3 sets of functionalities:
1. A robust library of object-oriented classes and methods that specify how a testcase can interact with an application’s GUI objects.
2. A set of statements, operators and data types that you use to introduce structure and logic to a recorded testcase.
3. A library of built-in functions for performing common support tasks.
Moving from lower to higher version should not be a problem....
This is a general statement and cannot be true at all instances.
I faced problems with scripts working in 6.5 not running in 7.0 because some of the recognition patterns used each changed. And in some situations, finally landed two paths of the script to perform same action based on version.
PS: Did not encounter any problems from 6.0 to 6.5.
A SilkTest project is a collection of files that contains required information about a test project.
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.
You can use Clipboard functions. Get All the contents by Ctrl+a & ctrl+C. Then parse the List of sting ...
You meant to say one more browser window (Order Request) appearing apart from original window (Order Status)?
If Order Request window is a popup.
Following code closes the active browser window if it is a popup:
[-] !(if Browser.ComboBox("#1").exists())
[ ] Browser.SetActive()
[ ] Browser.typekeys("")
If Order Request window is a Browser window.(not a popup)
You can use the following code to close unwanted Browsers(like Order Request)
The SilkTest testplan is an outline that provides a framework for the software testing process and serves as the point of control for organizing and managing your test requirements. A testplan consists of two distinct parts: an outline, which is a formatted description of the test requirements, and statements, which are used to connect the testplan to SilkTest scripts and testcases that implement the test requirements.
1. Run SilkTest.
2. Select Basic Workflow bar.
3. Click Open Project on the Workflow bar.
4. Select New Project.
5. Double click Create Project icon in the New Project dialog box
6. One the Create Project dialog box, enter your project name, and your project description.
7. Click OK.
8. SilkTest will create a new subdirectory under SilkTest project directory, and save all files related to the new project under that subdirectory.
Segue testing methodology is a six-phase testing process:
1. Plan - Determine the testing strategy and define specific test requirements.
2. Capture - Classify the GUI objects in your application and build a framework for running your tests.
3. Create - Create automated, reusable tests. Use recording and/ or programming to build test scripts written in Segue's 4Test language.
4. Run - Select specific tests and execute them against the AUT.
5. Report - Analyze test results and generate defect reports.
6. Track - Track defects in the AUT and perform regression testing.
Document Object Model (DOM) browser extension is a SilkTest add-on component for testing Web applications. DOM browser extension communicates directly with the Web browser to recognize, categorize and manipulate objects on a Web page. It does this by working with the actual HTML code, rather than relying on the visual pattern recognition techniques currently employed by the Virtual Object (VO) extension.
SilkTest Agent is a SilkTest component that receives testing commands from the SilkTest Host and interacts with AUT (Application Under Test) directly. SilkTest Agent usually runs on the same machine where AUT is running.
A testplan file contains text lines. There are 5 types of text lines in a testplan file:
1. Comment - Marked in green color: Providing commentary information.
2. Group descriptiton - Marked in black color: Providing descriptions for groups of tests. Tests in a testplan can be grouped into multiple levels of groups.
4. Test description - Marked in blue color: Providing descriptions for individual test.
5. Testplan statement - Marked in dark red color: Providing relations to link scripts, testcases, test data, closed sub testplans or an include file to the testplan.
6. Open subplan file marker - Marked in magenda color: Providing relations to link sub testplans to be included in a master testplan.
Use GetCaption () method......
Either use "sCaption" Property or "GetCaption" Method
Syntax - ControlName.sCaption
or use GetCaption () Method
Syntax - ControlName.GetCaption ()
The DOM browser extension uses the following syntax for Web UI objects:
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.
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.
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 apge.
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.