[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[platform-text-dev] Fw: [jdt-ui-dev] 3.3 M4 Testpass

----- Forwarded by Daniel Megert/Zurich/IBM on 12.12.2006 09:40 -----
             h/IBM@IBMCH                                                To 
             Sent by:                  "Eclipse JDT UI developers list."   
             jdt-ui-dev-bounce         <jdt-ui-dev@xxxxxxxxxxx>            
             s@xxxxxxxxxxx                                              cc 
             12.12.2006 09:29          [jdt-ui-dev] 3.3 M4 Testpass        
             Please respond to                                             
              "Eclipse JDT UI                                              
             developers list."                                             

Hi All

This is the final version of the test grid for today's 3.3 M4 test pass for
JDT UI/Text and Platform Text/Platform Search.

As always, testers from the community are highly welcome and encouraged to
participate in the test pass to provide feedback.


(See attached file: M4_Test_Plan.html)(See attached file:
jdt-ui-dev mailing list
Title: 3.3 M4 Test Plan

3.3 M4 Test Plan

Test day: Tuesday, 2006-12-12
Test Build: I20061212-0010
Components: Platform Search, Platform Text, JDT Text and JDT UI
Testers: Benno, Dani, Markus, Martin


Test New Functionality

First test all those items where you are listed as first tester.

Test showing of invisible characters (Benno, Martin - FAQ: Dani)

Spell checking in Text, Properties and CU editors (Markus, Benno - FAQ: Dani)

for each:

verify new F3 behavior which only uses caret location (instead of selection) (Martin, Markus - FAQ: Dani)

quick fix & quick assist: (Dani, Markus - FAQ: Martin)

package explorer (Markus, Benno - FAQ: Martin)

build path dialog (Benno, Dani - FAQ: Martin)

organize import (Dani, Markus - FAQ: Martin)

code formatter dialog (Markus, Benno - FAQ: Martin)

new JUnit API: (Benno, Dani - FAQ: Martin)

Undo Delete Refactorings: (Dani, Martin - FAQ: Markus)

For the next two items, just test a representative selection of refactoring and source actions:

Refactor without saving editors: (Benno, Dani - FAQ: Markus)

Refactor derived files: (Martin, Benno - FAQ: Markus)

Bug Verification

There are 12 bugs meaning that everyone has to verify 3 bugs. Before starting to verify a bug add a comment indicating that you are about to verify it.