Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "TPTP-Test-Tools-20080128"

(Test Automation Initiative)
Line 21: Line 21:
 
* [http://www.eclipse.org/tptp/reports/test/tests.php?source=All Test reports.]
 
* [http://www.eclipse.org/tptp/reports/test/tests.php?source=All Test reports.]
  
* All defects will require project/PMC approval. 
+
=== Where are we at? ===
  
* All fixes MUST be checked-in to both 4.4.1 (TPTP-4_1_1) and 4.5 (HEAD) streams.
+
* We are currently starting the 4.4.1 test pass (TP) for two weeks (target: February 8).
  
 
=== Testing ===
 
=== Testing ===
  
* The 4.4.1 test pass (TP) starts on next Monday (January 28) for two weeks (see [http://www.eclipse.org/tptp/home/project_info/releaseinfo/4.4.1/schedule.html Detailed Schedule]).
+
* Tony completed the Windows testing as part of his orientation.
** Tony is completing the Windows testing as part of his orientation.
+
* Lead committers have to complete multi-platform and Linux testing for the TP, including:
** Lead committers will have to complete multi-platform and Linux testing for the TP.
+
** Duwayne:
 +
***
 +
** Paul:
 +
***
 +
** Tony:
 +
***
  
 
== 4.5 ==
 
== 4.5 ==
Line 47: Line 52:
 
=== Where are we at? ===  
 
=== Where are we at? ===  
  
* We are currently in last week of development for 4.5 I5 (target: January 25).
+
* We have delayed the start of I5 testing until TP2 (target: February 11) to focus on the 4.4.1 TP.  
  
 
=== Testing ===
 
=== Testing ===
Line 56: Line 61:
 
** Complete a full test pass for 4.5 I5 TP2.
 
** Complete a full test pass for 4.5 I5 TP2.
  
* For the Test Project, we can extend I5 development to February 6 by attaching patches to the Bugzilla AFTER I5 development ends on January 25.
+
* For the Test Project, we can extend I5 development to February 6 by attaching patches to the Bugzilla.
  
 
===  Test Automation Initiative ===
 
===  Test Automation Initiative ===
Line 97: Line 102:
 
* [http://www.eclipse.org/tptp/reports/bugs/report_45.php?src=All&queryType=bugs&component=Test Queries.]
 
* [http://www.eclipse.org/tptp/reports/bugs/report_45.php?src=All&queryType=bugs&component=Test Queries.]
 
* [http://wiki.eclipse.org/TPTP_45_Weekly_Schedule Schedule].
 
* [http://wiki.eclipse.org/TPTP_45_Weekly_Schedule Schedule].
 +
 +
* Defects requiring a sizing:
 +
** Duwayne:
 +
**** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=215082 publication task problems.]
 +
**** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=216635 Running ASF through Ant requires display export.]
  
 
* Remaining I5 defects:
 
* Remaining I5 defects:

Revision as of 09:08, 28 January 2008

Attendees

  • Present:
    • Paul Slauenwhite
    • DuWayne Morris
    • Jerome Bozier
    • Tony Wang

4.4.1

Release Information

  • 4.4.1 will ship with the Europa Winter Maintenance Release (target release date: February 29, 2008).

Where are we at?

  • We are currently starting the 4.4.1 test pass (TP) for two weeks (target: February 8).

Testing

  • Tony completed the Windows testing as part of his orientation.
  • Lead committers have to complete multi-platform and Linux testing for the TP, including:
    • Duwayne:
    • Paul:
    • Tony:

4.5

Release Information

  • 4.5 will ship with the Ganymede Simultaneous Release (target release date: June 30, 2008).

Where are we at?

  • We have delayed the start of I5 testing until TP2 (target: February 11) to focus on the 4.4.1 TP.

Testing

  • Since the 4.4.1 TP overlaps with the 4.5 I5 TP1 (see 4.4.1 Detailed Schedule and 4.5 Detailed Schedule) and there have been sufficient fixes integrated into 4.4.1 to merit a full test pass, we will:
    • Not complete 4.5 I5 TP1 to focus on the 4.4.1 TP.
    • Start the 4.5 I5 TP2 when the 4.4.1 TP is complete.
    • Complete a full test pass for 4.5 I5 TP2.
  • For the Test Project, we can extend I5 development to February 6 by attaching patches to the Bugzilla.

Test Automation Initiative

Enhancements

  • Duwayne:
    • Test execution should support parallel execution of tests: See the meeting minutes for more details. Duwayne will complete this enhancement in I5/I6 development. The test cases and product documentation will be complete in I5 TPs and I6 development. This past week, Duwayne found non-thread-safe code in the Hyades execution APIs causing exceptions when extracting data from RMI calls. Will consult Joe and Scott for any history on this area of the code.

Defects

Miscellaneous

Round-table

Paul

Duwayne

Jerome

Tony

  • Last Week:
    • Reviewed TPTP processes and Testing Tools documentation.
    • Running 4.4.1 test suites on Windows.
  • This Week:
    • Complete running 4.4.1 test suites on Windows.

Action items

Jerome

Notes

News

  • Jerome was elected by the Committers and approved by the PMC as a Committer on the TPTP Testing Tools project.
    • Jerome will fill out the Member Committer Questionnaire to complete the process.
    • Jerome G. will nominate Jerome as the lead committer for the following components by sending an email to the Testing Tools mailing list:
      • Test.UI
      • Test.UI.ConfigEditors
      • Test.UI.DatapoolEditor
      • Test.UI.FrameworkEditors
      • Test.UI.TestPerspective

EclipseCon 2008

Reminders

Lead Committers

  • Continually review copyright reports and ensure files will missing copyright or incorrect copyright year are corrected.
  • Add the Original Estimate (PH) when triaging a new defect.
  • Update the Hours Worked (PH) when completing a defect.
  • Test their components or review/track testing contributed by other committers/resources.
  • Monitor the TPTP news group and answer posts specific to their Test Project components.
  • Verify that all API changes (modifications, additions, and removals) do not breech the TPTP API Contract.
  • Use the MyFoundation Portal for committer elections.

Back to the top