Bypass

[jefleponot]

Bypass commands that skiped step if condition is done
and other features

[davidlinse]

Would you mind adding english translations as well ?
~david

[jefleponot]

Hi dav,

I don't understand because english is the default language so ...
Have you an example of mis translation ?

[Zarkonnen]

I'm sorry, can you explain what the bypassX steps do? How do they differ from assert/verify/wait? Are they a kind of flow control?

[jefleponot]

Hello Zarkonnen,

Let me explain what "bypass comands" do :

Sometimes when you open a webpage, you don't have full page you are waiting for but :

• an advertising
• a cleaning request from the previous session
• a maintenance page
• a minimal portal
  So, when you try to run the test, there is often a problem.

The byPass commands can help you. If there is a ramdom possible action (possible step) you can run it or jump to an other step if not necessary.

Bypasses a given number of defined navigation steps

[Zarkonnen]

Ah, so they're actions that don't stop test playback when they fail?

[jefleponot]

In Fact, we have block of actions (steps) that according to the response of the website occurs differents ways of execution for a scenario (script).

So scenario is more flexible and works in 95%.

[zcsteele]

The bypass operations work as advertised, but the skipped steps are flagged as 'failed' when the bypass logic skips them. This causes the test as a whole to be flagged as failing even when all the other steps pass.

I've added a couple of commits to my fork of the bypass branch which add a new "Skipped" status:
https://github.com/zcsteele/se-builder/tree/bypass