Certification of SRUs
All HW devices should be re-certified on a proposed SRU , previous to the SRU being released. Any issues should gate the SRU release. However, due to the cost associated with manual testing, this blue print will only consider the execution of automated testing.
Define and Implement a process for automated trigger of testing of SRUs
Blueprint information
- Status:
- Complete
- Approver:
- Kevin Krafthefer
- Priority:
- Essential
- Drafter:
- Ronald McCollam
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for archives
- Implementation:
-
Implemented
- Milestone target:
-
may2011
- Started by
- Victor Tuson Palau
- Completed by
- Victor Tuson Palau
Related branches
Related bugs
Sprints
Whiteboard
[cert-team] run a one-off proposed kernel test and measure how long it takes: done
[cert-team] Identify what test will let us ensure the system is recoverable: done
[cert-team] to work out what is the common /minimum amount of machine - req form pitti: done
[cert-team] workout with the qa team how to validate that update manager can launch : done
[cert-team] agree a process on how/when to test proposed kernels: done
[cert-team] write dedicated SRU test suite: done
[cert-team] roll out dedicate test suite: done
[cert-team] test 50 certified systems in Lucid&Maverick: done
[cert-team] test 75 certified systems in Lucid&Maverick: done
[cert-team] test 100 certified systems in Lucid&Maverick: done
[cert-team] test all certified systems in Lucid&Maverick: carryover
