Advanced Whitelist Syntax for Plainbox

Registered by Brendan Donegan on 2013-04-18

Richer syntax for whitelists

- Sanity checking of requirements
 - A ‘dry run’ of the scenario to catch specific types of failures that are DOOMED to happen
- Aliasing of jobs to reduce duplication
 wireless_connection, alias: before_suspend
 suspend
 wireless_connection, alias: after_suspend

- Encoding prerequisites in a job (using plainbox requirements to differentiate the reason behind the requirement failures)
 Prerequisites: System has a 3G modem
 Requirements: System has the packages installed needed for running the 3G modem test and the correct setup to do so (e.g. config options, SIM card inserted etc)

- Marking tests as optional/greylisted
- Welcome message computed from whitelist
 - Estimated duration
Required hardware/setup (external)

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.