GitLab

In such a case we are clicking on the clone.
If the mouse is not on hovering the clone there is no reason for its name
to appear in the infoline. And the hovering is already tested.

There is no guarantee on the version. Fix #3695

#3699 must be solved first

Can we let watir guess what the browser is?

In Chrome we have some cases where the element is not ready yet as we test it.
Thus we prefer using the until function to make sure the element is as expected within
a short amount of time

There was a deprecated warning because we tested the wait_until on
a variable that may change over time. The code has now be changed so that
the element is retrieved each time we test it.
Moreove the until() function may be useful elsewhere

This cannot be properly tested in test_segmenter_page_errors.rb as we don't have a menu there

See #3722 and #3701.

tests/launch_functional_tests: select browsers from environment variable or from 'tested-browser' file

Partially revert 02ca0a24.
We want both to agnostically use 'launch_functional_tests', but also to be able to follow in a versioned file
the supported browsers.

link to #2876

Remove the html <pre> of functions and add it to the opener window function call
link to 2876

Add 'pre' to the getted string.
Link to #2876

See #3759

link to #3689

link to #3697

link to #3697

Not the correct method for the selection. 
Link to #1292

This will be useful for watir.
Link to #1292

link to #1292

Closes #3701.

The code didn't use shortcuts from VidjilBrowser.
Also the tests were calling set_browser each time which had
as en effect to start a new browser each time which had a strange
behaviour with the new Watir version.

For some reason with this version of Watir both titles are empty.
Thus we have to match on the URL.

This test was disabled since 9acc7e10. But since #2565 is fixed we re-enable it.

It depends on the client configuration

Use latest Ruby version and Watir instead of watir-webdriver.
This will make it easier to install it on recent OS and it
will also allow us to test on recent Firefox versions.

Some changes in the syntax:
- visible? is deprecated → present?
- wait_until_* are deprecated → wait_until(&: *)
- some way of specifying timeouts

Watir also seems to be quicker thus the need to add
some waits or some sleeps

link to #2632

link to #2632

link to #2632

link to #2632