Print Page | Close Window

exception handling in Silk Test

Printed From: One Stop Testing
Category: Testing Tools @ OneStopTesting
Forum Name: SilkTest @ OneStopTesting
Forum Discription: SilkTest is an automation tool for testing the functionality of enterprise applications in most versions of Windows, Sun Solaris 9 & 10, and Red Hat Enterprise Linux WS 2.1 & 3.0.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=663
Printed Date: 29Apr2024 at 4:01pm


Topic: exception handling in Silk Test
Posted By: Rupa
Subject: exception handling in Silk Test
Date Posted: 04Apr2007 at 5:27am
When ever you execute any Testcase in Automation 2 things are always mandatory.Prevalidation or v...



Replies:
Posted By: ram7vasu
Date Posted: 08Jan2008 at 3:11am

If a testcase fails during the test execution (for ex, if the expected value doesn't match the actual value in the verification statement), SilkTest by default calls its built-in recovery system, which:

> Terminates the testcase

> Logs the error in the results file

> Restores your application to its default base state in preparation for te next test case.

Commands:

Using do...except

Raise Command

In addition to use buil-in exceptions, you can define your own exceptions and generate them using the raise statement

Reraise Command

You can also use do...except to perform some custom error handling, then use the reraise statement to pass control to te recovery system as usual

When ever you execute any Testcase in Automation 2 things are always mandatory.

  1. Prevalidation or verification for the exsisting Window/browser.
  2. Post validation or verification of Next Window/Browser.

Now during execution any other window/ browser is poping up etc, then those are called exception's, and that needs ur attention.

And that can be handled by DO EXCEPT

-------------
RAM SAKSOFT


Posted By: ram7vasu
Date Posted: 08Jan2008 at 3:12am

If a testcase fails during the test execution (for ex, if the expected value doesn't match the actual value in the verification statement), SilkTest by default calls its built-in recovery system, which:

> Terminates the testcase

> Logs the error in the results file

> Restores your application to its default base state in preparation for te next test case.

Commands:

Using do...except

Raise Command

In addition to use buil-in exceptions, you can define your own exceptions and generate them using the raise statement

Reraise Command

You can also use do...except to perform some custom error handling, then use the reraise statement to pass control to te recovery system as usual

When ever you execute any Testcase in Automation 2 things are always mandatory.

  1. Prevalidation or verification for the exsisting Window/browser.
  2. Post validation or verification of Next Window/Browser.

Now during execution any other window/ browser is poping up etc, then those are called exception's, and that needs ur attention.

And that can be handled by DO EXCEPT  Smile

-------------
RAM SAKSOFT



Print Page | Close Window