Skip to main content
Jump to: navigation, search

Difference between revisions of "Platform UI/Testing"

(Platform UI Test Plan for 3.6 M3)
 
(100 intermediate revisions by 12 users not shown)
Line 1: Line 1:
==Platform UI Test Plan for 3.6 M3==
+
{{Platform_UI}}
 +
== Platform UI Test Plan for a Eclipse ==
  
The goal of this test pass is to achieve full coverage of the SDK to get a good overall picture on the state of the build.
+
The Eclipse platform UI team constantly test the latest and greatest build. On a regular basis we also test more intensive and also ask committers to stop developing features during that test period. The goal of a test pass is to achieve full coverage of the SDK to get a good overall picture on the state of the build.
  
Verify bugs for [[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Doc&component=IDE&component=UI&target_milestone=3.6+M4&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= 3.6 M4]].
+
===Verify bugs===
  
 +
All critical bugs relevant for a build should be verified but also the overall Eclipse IDE should be tested. You can search in Bugzilla for the ''"Resolved" "Fixed"'' bugs of a particular Milestone, and verify those bugs.
 +
If you verified a bug, please put the bug into ''"Verified" "Fixed"'' state and ''add the build ID'' of the Eclipse installation you used for testing to the bug report.
  
===Checklist===
+
The following is an example query for the Eclipse 4.6 M7 milestone. Please adjust it according to your needs, changing the release and the milestone at the very end of the query.
  
* Accessibility. There have been numerous changes through the SDK in all components that could severely hamper accessibility.
+
[https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=RESOLVED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&cmdtype=doit&component=Doc&component=IDE&component=UI&component=User%20Assistance&component=Runtime&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&order=Reuse%20same%20sort%20as%20last%20time&product=Platform&query_format=advanced&resolution=FIXED&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&target_milestone=4.6%20M7&type0-0-0=noop&value0-0-0=&votes= 4.6 M7 - "Resolved" "Fixed"]
** High contrast
+
** Screen reader
+
  
* New problems, markers, bookmarks and tasks view. The problems view has been replaced and is ready for general testing. Concentrate on
+
===Checklist===
** All markers view
+
Their should also be a general functionality test of the Eclipse IDE/
** sorting and filtering
+
See the [[Platform UI/Component Area Testing|component area testing]] page for the list of items to test.
** command enablement
+
 
+
* Commands.
+
 
+
* Contributions
+
** The new Customize Perspective Dialog
+
 
+
* Decorators
+
** there have been a series of optimizations to decorator creation.
+
***Look out for disposed widgets as a result of opening and closing views
+
***confirm all decorations occur as expected
+
** files should decorate with icons for the appropriate content type.  This often will show itself with XML files.  Try defining XML files of various types and ensure that they have the correct icon.  Note any performance hits for this operation
+
 
+
* RCP - the ide now has several optional plug-ins. Try making RCP apps with the ide and no optional plug-ins.
+
 
+
* IDE - ensure that external modification followed by a refresh (F5) works as expected
+
 
+
* Progress
+
** check for multiple instances of the same job
+
** confirm canceling works
+
** confirm correct sort order
+
** run in background preference should be tied to the Always Run In Background in the Progress Dialog
+
** check the layout of all progress dialogs
+
 
+
* Graphics
+
**check for graphics that need to be updated
+
  
Also see the [[http://dev.eclipse.org/viewcvs/index.cgi/platform-ui-home/testfix/componentAreaTesting.html?view=co Component Test Areas]] plan.  The current owners of the components is actually described in [[http://www.eclipse.org/eclipse/platform-ui/componentAreas.php Component Areas]], but the suggestions of what to test are good.
+
== Operating systems and regular testers ==
 +
If you want to help testing on a regular basis, please add your name and operating system to this list.
  
==Platforms==
+
Windows 10
Mac Leopard
+
* Patrik Suzzi
* Prakash, Mike Wilson
+
Vista
+
* Eric Moffatt
+
GTK
+
* Paul Webster
+
XP
+
*Boris Bokowski, Hitesh (high contrast), Oleg Besedin
+

Latest revision as of 11:01, 26 April 2016

Platform UI Test Plan for a Eclipse

The Eclipse platform UI team constantly test the latest and greatest build. On a regular basis we also test more intensive and also ask committers to stop developing features during that test period. The goal of a test pass is to achieve full coverage of the SDK to get a good overall picture on the state of the build.

Verify bugs

All critical bugs relevant for a build should be verified but also the overall Eclipse IDE should be tested. You can search in Bugzilla for the "Resolved" "Fixed" bugs of a particular Milestone, and verify those bugs. If you verified a bug, please put the bug into "Verified" "Fixed" state and add the build ID of the Eclipse installation you used for testing to the bug report.

The following is an example query for the Eclipse 4.6 M7 milestone. Please adjust it according to your needs, changing the release and the milestone at the very end of the query.

4.6 M7 - "Resolved" "Fixed"

Checklist

Their should also be a general functionality test of the Eclipse IDE/ See the component area testing page for the list of items to test.

Operating systems and regular testers

If you want to help testing on a regular basis, please add your name and operating system to this list.

Windows 10

  • Patrik Suzzi

Back to the top