Continue after ERROR in WPM

We have a big environment with a large variety of products. Each of these products can be supported by 50 to 100 servers.

Currently, with WPM, there is no way to tell it that you want it to continue on errors. So, say I have one test that is checking the availability of 10 different servers, if the first server in that list is down, it sends an alert and stops the test. I've no way of knowing the status of the other 9 servers.

We can of course create 10 separate tests, one for each server, but this creates a ton of additional work and maintenance. Each of those tests would have to login to the product, navigate to a particular page and log out.

Having the option to continue after a failure would mean that we only have to login to the product once, go directly to a particular URL on each node for testing and then log out once.

If the password were changed for our test account, it would only have to be updated in 1 test vs 10 (or in reality, 100).

This is a big deal for us and will prevent us from migrating completely to WPM, allowing us to get rid of another product which we are really hoping to do eventually.

Work flow of what we would like to see one day in WPM:

* Login to https://yada.com

* web1 URLOK

* web2 URLOK

* web3 URLOK

* web4 URLERR - generates alert

* web5 URLOK

* Logout of https://yada.com

So, one test vs having to have 5 different tests. This of course will also mean we can monitor our environment with far fewer players. With the current version of WPM, we will need 25+ players to support our environment. With this desired change, we would only need 5.

Find more posts tagged with

prodfr

feature_request

wpm

Status: None

Comments

netlogix

I also need this (maybe different reason) - here is my scenario:

1) sign on to the page

2) list documents available

a) look for specific words in page

3) list available 3rd party SSO links (if 3rd party is down, link wont show up)

a) look for specific words in page

4) list historical activity and look for activity

a) look for specific words in page

5) log out

The issue is that if step 2a/3a/4a fails, it doesn't continue on. If one of those word searches fails, it gives me information, but the page/site is still operational and I want the rest of it checked out and reported on - maybe set the step to critical, warning, or failed, but not the whole transaction to failed. Kinda like SAM can have one failed service, but it still checks the rest of them.

(maybe similar but worded differently - not sure of romeyde's complete meaning)

fikish

I'm having the same problem.

I want to test a few different items with a lot of web portals we provide clients BUT I don't want it to stop after failing one.

Did anyone find a solution to this?

emarksrpi86

I can also use this functionality. In may cases I run the same website for multiple clients. I would like to be able to run through all clients and know which are up and which are not. Currently, we only find the first one that is down.

romeyde

Option to continue playback after step failure.309476

The version 2.1.0 change log states that we can now continue playback after failure based on the fixed issues.

Web Performance Monitor 2.0 Release Notes

But the changes listed don't seem to suggest this is possible?

I hadn't had a chance to install 2.1 yet on my dev, hope to do this sometime this or next week.

But, is this true? If one step 10 fails on a 20 step test, the test can be told to continue running and it will still generate an alert at the end telling us which steps failed?

If true, than this by far the biggest change in this new version that will help us.

peter.kruty

You can make now some actions optional, that means if they will fail transaction execution will continue. Best is to try it!

dnerdahl

This is still functionality that appears to be needed. I have attempted to use the optional action, however, optional actions never change from an "up" status. Thus I have no way to use them in an alert.

dnerdahl

Optional actions also do not lend to to the duration of a step. For me, optional actions do not meet the criteria for this feature request because there is no recorded error... that I can find.

dcota

Great idea and is an absolute must have for the product. Most UI automation tools have the ability to continue on processing the script if there is an error. (ie. QTP, and SilkTest Workbench). Within a Transaction you should be able to group steps together into something called a "Test". Then you should have the ability to choose if you want the transaction to stop if a "Test" fails or continue on starting on the next "Test".

Being able to record a single transaction that tests multiple URLs is something would be the top priority for my company. Its a maintenance problem to have to have separate transactions for related applications and then configure alerts to handle all of those transactions rather than having a single transaction.

Please consider implementing this in a coming release as this is very important to many customers.