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.
TPTP-AG-20080414
Revision as of 09:59, 14 April 2008 by Unnamed Poltroon (Talk)
Date
- April 14, 2008
Attendees
- Present:
- Oliver Cole
- Tony Wang
- Mikhail Voronin
- Joanna Kubasta
- Joel Cayne
- Eugene Chan
- Chris Elford
Topic
- PoG and ToG
Minutes
PoG
- Advocate/Lead:
- One person leading the effort, which should be different from the Trace Project lead (e.g. Chris or Mikhail).
- Eugene would represent IBM to evaluate quality and review requirements.
- Target Audience:
- Eclipse Projects.
- Eclipse Community.
- WTP/TPTP EPP packaging:
- Joel will discuss the effort to package only the Trace components.
- How much extra testing?
- Weekly smoke testing.
- Posting weekly/iteration test results.
- Existing defects:
ToG
- Advocate/Lead:
- One person leading the effort, which should be different from the Test Project lead.
- Due to issues with staffing and skills, the lead will probably be the Test Project lead.
- Target Audience:
- Stage 1:
- TPTP.
- COSMOS.
- Stage 2:
- Eclipse Projects.
- Eclipse Community.
- Stage 1:
- Scenarios/Use Cases:
- Unit testing of local and remote Java/Eclipse applications using the JUnit/JUnit Plug-in test types.
- Performance testing of local and remote Web applications using the URL Recorder and URL test type.
- Data-driven unit testing using datapools.
- Test execution results viewing using the Test Log view.
- Test report generation using the TPTP-BIRT integration.
- Automated test execution and report generation using the Automatable Service Framework (ASF).
- Existing defects:
- Platform Project:
- Test Project:
- AGR Tests require absolute path to Equinox JAR
- Clear remote workspace launch does not work for remote test execution
- AGR Tests cannot be run with start ACServer
- Remove XMLUnit dependency and convert reporting tests to TPTP tests
- Content missing in Tabular Report
- Connection property does not deploy all dependencies
- Connection property does not allow JUnit Plug-in Tests to be executed
- ASF marshalling return value between service and client adapter does not have support for failures / exceptions
- Confusing exceptions when running automated services.
- ASF Test Execution Service races with AutoBuildJob -- can lead to unexpected test results
- ANT test results property requires trailing slash to specify location
- ANT importExistingProjects throws Exception
- More information: 4.5 Test Automation Initiative: Common Test Infrastructure
Questions/Answers
- Q:
- A: