Establish acceptance testing criteria for LAVA deployments and infrastructure changes
To ensure the reliability of LAVA itself, we should establish some integrated testing scenarios to validate LAVA. Some version of these tests should be executed whenever major infrastructure changes are made, but also before a new release. The testing should not take more than one person, and should not take more than an hour to perform.
Blueprint information
- Status:
- Not started
- Approver:
- Paul Larson
- Priority:
- Undefined
- Drafter:
- Dave Pigott
- Direction:
- Needs approval
- Assignee:
- Dave Pigott
- Definition:
- New
- Series goal:
- Accepted for trunk
- Implementation:
- Unknown
- Milestone target:
- backlog
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
[dpigott, 2012-07-02] Has this BP been overtaken by the lab health checks, or is there another point that I'm missing?
[doanac, 2012-07-02] Between health checks and a staging server, I think we are mostly there. However, we should probably update https:/
Headline:
Acceptance:
Work Items
Work items:
Draft blueprint: TODO