Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

4.5 Test Automation Initiative

Revision as of 09:11, 31 October 2007 by Paulslau.ca.ibm.com (Talk | contribs) (Benefits)

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.

Deliver dates

  • October 31:
    • Complete the testing process, extending the existing TPTP Testing Strategy.
    • Profiler test suite automation.
  • November 14:
    • Proof of concept (PoC) for integration of ASF and TPTP builds for PMC approval and integrate with TPTP builds.
    • Presentation to TPTP committers.
    • Measure cost savings.
  • November 28:
    • Each project automates their manual test suites and converge existing automated test suites over time to leverage the test infrastructure.
    • Measure cost savings.
    • Report cost savings to PMC.

Meeting Minutes

Back to the top