Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumTesting Tools @ OneStopTestingSilkTest @ OneStopTesting

Message Icon Topic: exception handling in Silk Test

Post Reply Post New Topic
Author Message
Rupa
Newbie
Newbie
Avatar

Joined: 04Apr2007
Online Status: Offline
Posts: 1
Quote Rupa Replybullet Topic: exception handling in Silk Test
    Posted: 04Apr2007 at 5:27am
When ever you execute any Testcase in Automation 2 things are always mandatory.Prevalidation or v...



Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
ram7vasu
Newbie
Newbie
Avatar

Joined: 22Nov2007
Location: India
Online Status: Offline
Posts: 29
Quote ram7vasu Replybullet 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
IP IP Logged
ram7vasu
Newbie
Newbie
Avatar

Joined: 22Nov2007
Location: India
Online Status: Offline
Posts: 29
Quote ram7vasu Replybullet 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
IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.484 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting