Feature #10237

Refactor and clean up the automated test suite

Added by anonym 2015-09-23 09:09:49 . Updated 2016-01-19 15:04:42 .

Status:
Confirmed
Priority:
Normal
Assignee:
anonym
Category:
Test suite
Target version:
Start date:
2015-03-07
Due date:
% Done:

3%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Some stuff was done in Feature #6543, but there’s a lot left to do to prevent it from becoming a crazy mess.

Subtasks

Feature #9030: Encapsulate our test suite helper functions inside a module Confirmed anonym

0
Feature #9040: Encapsulate config.rb into TestSuiteConfig class Confirmed anonym

0
Bug #9223: Improve the semantics of try_for In Progress anonym

0
Feature #5847: Improve how we pass data between steps Confirmed

10
Feature #10283: Use external snapshots in the automated test suite Confirmed anonym

0
Feature #10328: Clean up features with Scenario Outlines Confirmed anonym

0
Feature #10329: Improve gherkin in our features Confirmed anonym

0
Feature #10341: Describe checkpoints in .feature files Confirmed anonym

0
Bug #10429: Code cleverness vs gherkin explicitness in our feature files Confirmed anonym

0
Feature #10864: Refactor vm_helper XML parsing code Confirmed anonym

0
Feature #10974: Always use internal snapshots In Progress anonym

20
Feature #11376: Remove @check_tor_leaks tag and always look for leaks Confirmed anonym

0

Related issues

Blocked by Tails - Feature #6094: Test suite: background snapshot improvements Resolved 2015-10-15

History

#1 Updated by anonym 2015-09-23 09:10:36

  • blocked by Feature #6094: Test suite: background snapshot improvements added

#2 Updated by anonym 2015-09-23 09:16:32

A bit part of the work will be to reorganize/refactor/rethink/redisgn the helper classes, in particular how they are coupled and the objects lifetimes. Not filing any tickets for this yet.

#3 Updated by anonym 2015-09-23 09:22:19

Another interesting part would be to rid ourselves of the shell wrapper and do everything “in Ruby”. In particular, I think we will eventually need to invoke Cucumber through Ruby if we want to use the up-coming Cucumber “Suites” feature mentioned in Bug #7233#note-16.