Difference between revisions of "4.5 Test Automation Initiative"

Revision as of 08:25, 12 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).
• Integrate EMMA with the build and test process for generating code coverage reports for all manual and automated testing.

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.

Documentation

• Diagram of ASF automation interaction

Meeting Minutes

• September 24, 2007
• October 22, 2007
• November 6, 2007
• November 12, 2007