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

Difference between revisions of "4.5 Test Automation Initiative"

(Meeting Minutes)
(Delivery dates)
Line 27: Line 27:
  
 
* November 14:
 
* November 14:
** Complete the first testing process document.
+
** First draft of the first testing process document for review.
 
** 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.
 +
** Status update for the PMC.
 
** Measure cost savings.
 
** Measure cost savings.
  
 
* November 21:
 
* November 21:
 +
** Review of the first testing process document.
 +
** First draft of the remaining testing process documents for review
 
** Identify and resolve bugs.
 
** 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.
+
** Final version of the the first testing process document.
 +
** Review of the remaining testing process documents for review
 +
** Status update including cost savings for the PMC.
 
** Presentation to TPTP committers.
 
** Presentation to TPTP committers.
** Report cost savings to PMC.
+
** Each project automates their manual test suites and converge existing automated test suites over time to leverage the test infrastructure.
  
 
== Documentation ==
 
== Documentation ==

Revision as of 08:48, 13 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:
    • First draft of the first testing process document for review.
    • Proof of concept (PoC) for integration of ASF and TPTP builds for PMC approval and integrate with TPTP builds.
    • Status update for the PMC.
    • Measure cost savings.
  • November 21:
    • Review of the first testing process document.
    • First draft of the remaining testing process documents for review
    • Identify and resolve bugs.
  • November 28:
    • Final version of the the first testing process document.
    • Review of the remaining testing process documents for review
    • Status update including cost savings for the PMC.
    • Presentation to TPTP committers.
    • Each project automates their manual test suites and converge existing automated test suites over time to leverage the test infrastructure.

Documentation

  • Diagram of ASF automation interaction

AsfBVT.JPG

Meeting Minutes

Back to the top