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.
4.5 Test Automation Initiative
Revision as of 14:15, 30 October 2007 by Unnamed Poltroon (Talk) (New page: == Members == * Paul Slauenwhite (Lead) * Alan Haggarty (Lead) * Joel Cayne * Jonathan West * Joanna Kubasta * Kiryl Kazakevich == Goals == * Consolidation of our testing process, and ...)
Contents
Members
- Paul Slauenwhite (Lead)
- Alan Haggarty (Lead)
- Joel Cayne
- Jonathan West
- Joanna Kubasta
- Kiryl Kazakevich
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.