Re: [Tails-dev] Automated tests specification

On 09/02/2015 11:11 AM, anonym wrote:
> Failing Scenarios:
> cucumber features/time_syncing_bridges.feature:29 # Scenario: Clock way
> in the past in bridge mode
> cucumber features/time_syncing_bridges.feature:45 # Scenario: Clock way
> in the future in bridge mode
> cucumber features/tor_stream_isolation.feature:48 # Scenario: Explicitly
> torify-wrapped applications are using the default SocksPort
> cucumber features/torified_git.feature:22 # Scenario: Cloning git
> repository over SSH
>
> 186 scenarios (4 failed, 182 passed)
> 1345 steps (4 failed, 5 skipped, 1336 passed)
> 348m33.765s

... and the run without --capture:

Failing Scenarios:
cucumber features/totem.feature:48 # Scenario: Watching a WebM video
over HTTPS, with and without the command-line
cucumber features/totem.feature:58 # Scenario: Copying video files to a
persistence and making sure that they persist

186 scenarios (2 failed, 184 passed)
1345 steps (2 failed, 10 skipped, 1333 passed)
320m10.637s

So there's an 8.9% increase. Of course, due to the failures it's hard to
draw any conclusions with any sort of confidence from this.

Cheers!