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

PDE/Testing

PDE
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse SourceProject Set File

This page will collect testing information for testing all the components of PDE.

PDE participates in the test pass before each milestone in the Eclipse Project Plan. During the test pass we try to verify any code that was changed during the previous milestone and test common scenarios for regressions.

Test Plans

3.7 End Game - May 2nd and 3rd

3.7 M6-M7 - No test plans, major issues were verified

3.7 M5 -January 26th (M5 PDE Bugs)

3.6.2 - No test plan, all bugs verified, major areas tested - January 20th (3.6.2 Bugs)

3.7 M4 - December 10th (M4 PDE Bugs)

3.7 M1-M3 - No test plans, major issues were verified

3.6 M7 - April 30th (M7 PDE Bugs)

3.6 M6 - March 12th (M6 PDE Bugs)

3.5.2 - (3.5.2 Bugs)

3.6 M5 - January 29th (M5 PDE Bugs)

3.6 M4 - December 11th (M4 PDE Bugs)

3.6 M3 - October 30th (M3 PDE Bugs)

3.6 M2 - September 18th (M2 PDE Bugs)

Test Process

  • Triage bugzilla, move unfinished bugs to a realistic milestone
  • Verify bugs fixed during the milestone
  • One day test pass testing functional areas (smoke test)
  • File bugs for any discovered issues
  • Fix significant regressions before the release

Test Documents

All Testing Tasks - A list of tasks that can be copied in to test plans

API Tools Tests - Detailed PDE API Tools tests

Test Scenarios - Detailed PDE UI test scenarios

Test Areas - A list of different areas in PDE UI that can be tested

Back to the top