Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "4.5 Test Automation Initiative"
(→Goals) |
(→Deliver dates) |
||
Line 23: | Line 23: | ||
* Decrease testing overlap by a) localizing test executing and reporting to one group and b) using code coverage statistics. | * Decrease testing overlap by a) localizing test executing and reporting to one group and b) using code coverage statistics. | ||
− | == | + | == Delivery dates == |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
* November 14: | * November 14: | ||
+ | ** Complete the first testing process document. | ||
** Proof of concept (PoC) for integration of ASF and TPTP builds for PMC approval and integrate with TPTP builds. | ** Proof of concept (PoC) for integration of ASF and TPTP builds for PMC approval and integrate with TPTP builds. | ||
− | |||
** Measure cost savings. | ** Measure cost savings. | ||
+ | |||
+ | * November 21: | ||
+ | ** Identify and resolve bugs. | ||
* November 28: | * November 28: | ||
** Each project automates their manual test suites and converge existing automated test suites over time to leverage the test infrastructure. | ** Each project automates their manual test suites and converge existing automated test suites over time to leverage the test infrastructure. | ||
− | ** | + | ** Presentation to TPTP committers. |
** Report cost savings to PMC. | ** Report cost savings to PMC. | ||
Revision as of 17:04, 6 November 2007
Members
- Paul Slauenwhite (IBM)
- Alan Haggarty (IBM)
- Joel Cayne (IBM)
- Jonathan West (IBM)
- Joanna Kubasta (IBM)
- Kiryl Kazakevich (Intel)
Goals
- Consolidation of our testing process and infrastructure.
- Consolidation of custom test frameworks (Test Dashboard, AC/Profiler test server, variants).
- Reuse of Test Project framework (ASF, reporting, etc.) and tools (AGR, JUnit, etc.).
- Automatic test execution and report generation with every build (BVT).
Benefits
- Specialization of testing skills (e.g. builds).
- Provide an infrastructure that makes it easy for committers to contribute automated test cases/suites.
- Manual labor savings by using automated tests, which are automatically executed with every build.
- Decrease time/cost to resolve defects since uncovered earlier in the code-test-build cycle.
- Decrease testing overlap by a) localizing test executing and reporting to one group and b) using code coverage statistics.
Delivery dates
- November 14:
- Complete the first testing process document.
- Proof of concept (PoC) for integration of ASF and TPTP builds for PMC approval and integrate with TPTP builds.
- Measure cost savings.
- November 21:
- Identify and resolve bugs.
- November 28:
- Each project automates their manual test suites and converge existing automated test suites over time to leverage the test infrastructure.
- Presentation to TPTP committers.
- Report cost savings to PMC.