Bug 213622

Comment 1 Paul Slauenwhite 2008-05-27 14:31:18 EDT

The documentation for the defect tracking function is duplicated:

Help >> Help Contents >> Testing Applications >> Testing with JUnit >> Analyzing test results >> Submitting defects

Help >> Help Contents >> Testing Applications >> Testing with JUnit >> Analyzing test results >> Associating defects with a test log

Comment 2 Paul Slauenwhite 2008-05-27 21:46:22 EDT

Results from testing the 4.5-200805231847 driver:

1) Providing tests with variable data
   1. The page of 'Providing tests with variable data' contains:
      a. Creating a datapool
      b. Opening a datapool
      c. Editing a datapool

      'Datapool structure' and 'Tutorial: Accessing a datapool rom a JUnit test' should be added in that page and these two pages should contain parent page 'Providing tests with variable data'

   2. The right click screen shot(right click context menu) of datapool is not accurate in those pages:
      a. Datapool structure
      b. Creating a datapool
      c. Editing a datapool
      need a new pic for those pages

   3. 'Tutorial: Accessing a datapool rom a JUnit test' is grabbed from 'Testing plug-ins with JUnit'

   4. Do we need to add the step for clicking prompt window like 'Open test perspective' or 'Open editor'? (not only for datapool, but also for all review)

2) Testing with JUnit
   1. Creating JUnit tests-->Creating a JUnit test manually
      step 3: Source folder should be javaProject/src (by default if we create a java project named 'javaProject')
      step 5: we are not able to see parent folder(javaProject/junit/samples) by typing package 'junit.samples' in step 3. javaProject/src is good

   2. Link tree error: 
      a. Editing Junit tests
         all pages under this belongs to 'Testing plug-ins with JUnit'(that because they are sharing the same resource) we can see the link tree at the top of each page
      b. Running a test
         belongs to 'Testing plug-ins with JUnit'
      c. Analyzing test results
         all pages including this page belongs to 'Testing plug-ins with JUnit' or 'Testing manually'
      d. Generating test reports
         belongs to 'Testing plug-ins with JUnit' or 'Testing manually'

3) Testing plug-ins with JUnit
   1. Creating a JUnit plug-in test manually 
      step 3: Source folder should be pluginProject/src (by default if we create a plugin project named 'pluginProject')
   
   2. Link tree error
      a. Analyzing test results/Generating test reports
         share the place as a root with 'Testing manually' sometimes

4) Testing manually
   1. Link tree error 
      same as 3.2.a , share with Testing plug-ins with JUnit sometimes
  

5) Test performance
   1. Editing a test
      first line below the first screen shot, Bold 'General Infomation' is not exist in URL test, it should be replaced with bold 'TPTP URL Test' 

   2. Generating an executable test
      in 'TPTP URL(JUnit) Test Definition Code Generation' dialog box, the bold 'Java Project' and 'Source folder' should be replaced by 'Source Folder' and 'Package Name'
      (add 'Class Name' if needed)

   3. Link tree error
      a. Analyzing test results/Generating test reports
         belongs to 'Testing plug-ins with JUnit' or 'Testing manually

      b. Running a test
         belongs to 'Testing plug-ins with JUnit'   
      

6) All shared folders problems(Junit + Junit-plugin + manual + URL, all shared folder above with link tree error)
   1. Analyzing test result-->Viewing events-->Test Log viewer Overview page
      In 'Common Properties', we need to add the description of 'Deployment' and 'Location'

   2. Analyzing test result-->Viewing events-->Test Log viewer Events page
      In 'Event page', we have 4 parts now, they are:
      a. Events
      b. Properties
         i)test name--click to open the test suite/cases
         ii)Verdict
         iii)Time
         iv)Text
      c. Defects
         have more details under Analyzing test result-->Viewing events-->submitting defects, but this is still one part of event page
      d. Extended properties

   3. Analyzing test result-->Viewing events-->Searching a test log
      step5: 'Search only immediate descendants' does not exist in that wizard anymore..

   4. Testing plug-ins with JUnit-->Generating test reports
      Duplicate 'Test Pass Report' in the form
      
7) Test suite(in Overview page--TPTP Manual Test--Description)
   1. Test.Doc.Datapools.technical_review.Windows_IA32.testsuite
              a. Testing Applications >> Testing applications >>  delete one 
              b. Help >> Help Contents >> Testing Applications >> Testing applications >> Providing tests with variable data >> * contains for all needs in datapool
                  So delete:
                  Help >> Help Contents >> Testing Applications >> Testing applications >> Datapool structure >> *
                  Help >> Help Contents >> Testing Applications >> Testing applications >> Tutorial: Accessing a datapool from a JUnit test >> *
  
   2. Test.Doc.Deployment.technical_review.Windows_IA32.testsuite
              a. Help >> Help Contents >> Testing Applications >> Reference >> Deployment ground rules >> * does not exist.

   3. Test.Doc.General.technical_review.Windows_IA32.testsuite
              a. Help >> Help Contents >> Testing Applications >> Testing applications      doesn't make sence, may change to       Help >> Help Contents >> Testing Applications  instead

   4. Test.Doc.JUnit_Plugin.technical_review.Windows_IA32.testsuite
              a. change it to Help >> Help Contents >> Testing Applications >> Testing plug-ins with JUnit >> *

   5. Test.Doc.JUnit.technical_review.Windows_IA32.testsuite
      Good

   6. Test.Doc.Manual.technical_review.Windows_IA32.testsuite
      Good

   7. Test.Doc.Test_Log_Viewer.technical_review.Windows_IA32.testsuite
              a. Help >> Help Contents >> Testing Applications >> Reference >> Test Log viewer Overview page >> *
                  Help >> Help Contents >> Testing Applications >> Reference >> Test Log viewer Events page >> *
                  do not exist any more, they have been moved to Analyzing test results-->Viewing events
                 
              b. because of the problem in 7.7.a, i'm thinking if i can change
                  Help >> Help Contents >> Testing Applications >> Testing Performance/Testing with JUnit/Testing JUnit Pluins/Testing Manually >> Analyzing test results >> Opening a test log/Viewing events/Test log viewer overview page
                  to
                  Help >> Help Contents >> Testing Applications >> Testing Performance/Testing with JUnit/Testing JUnit Pluins/Testing Manually >> Analyzing test results >>*

Comment 3 Paul Slauenwhite 2008-05-30 10:20:07 EDT

*** Bug 164175 has been marked as a duplicate of this bug. ***

Comment 4 Paul Slauenwhite 2008-05-30 10:20:27 EDT

In addition, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=164175.

Comment 5 Paul Slauenwhite 2008-05-30 10:56:33 EDT

> 3. 'Tutorial: Accessing a datapool rom a JUnit test' is grabbed from
> 'Testing plug-ins with JUnit'

Covered under https://bugs.eclipse.org/bugs/show_bug.cgi?id=220876.

Comment 6 Paul Slauenwhite 2008-05-30 11:11:31 EDT

> 4. Do we need to add the step for clicking prompt window like 'Open test
> perspective' or 'Open editor'? (not only for datapool, but also for all review)

Open Test Perspective is no longer supported.  I have added a step for opening the editor.

Comment 7 Paul Slauenwhite 2008-05-30 12:04:06 EDT

(In reply to comment #2)

>    2. Link tree error: 
>       a. Editing Junit tests
>          all pages under this belongs to 'Testing plug-ins with JUnit'(that
> because they are sharing the same resource) we can see the link tree at the top
> of each page
>       b. Running a test
>          belongs to 'Testing plug-ins with JUnit'
>       c. Analyzing test results
>          all pages including this page belongs to 'Testing plug-ins with JUnit'
> or 'Testing manually'
>       d. Generating test reports
>          belongs to 'Testing plug-ins with JUnit' or 'Testing manually'

Covered under https://bugs.eclipse.org/bugs/show_bug.cgi?id=234878.

Comment 8 Paul Slauenwhite 2008-05-30 12:39:25 EDT

(In reply to comment #7)
> (In reply to comment #2)
> 
> >    2. Link tree error: 
> >       a. Editing Junit tests
> >          all pages under this belongs to 'Testing plug-ins with JUnit'(that
> > because they are sharing the same resource) we can see the link tree at the top
> > of each page
> >       b. Running a test
> >          belongs to 'Testing plug-ins with JUnit'
> >       c. Analyzing test results
> >          all pages including this page belongs to 'Testing plug-ins with JUnit'
> > or 'Testing manually'
> >       d. Generating test reports
> >          belongs to 'Testing plug-ins with JUnit' or 'Testing manually'
> 
> Covered under https://bugs.eclipse.org/bugs/show_bug.cgi?id=234878.
> 

And https://bugs.eclipse.org/bugs/show_bug.cgi?id=234878#c2.

Comment 9 Paul Slauenwhite 2008-05-30 12:47:57 EDT

Created attachment 102903 [details]
Patch.

Comment 10 Paul Slauenwhite 2008-05-30 12:48:20 EDT

Hours worked to create and test the patch.

Duwayne, please review the patch.

Comment 11 Paul Slauenwhite 2008-05-30 13:31:26 EDT

The following test suites have been updated:

/org.eclipse.tptp.test.doc.user/manual/Doc/Test.Doc.Datapools.technical_review.Windows_IA32.testsuite
/org.eclipse.tptp.test.doc.user/manual/Doc/Test.Doc.Deployment.technical_review.Windows_IA32.testsuite
/org.eclipse.tptp.test.doc.user/manual/Doc/Test.Doc.General.technical_review.Windows_IA32.testsuite
/org.eclipse.tptp.test.doc.user/manual/Doc/Test.Doc.JUnit_Plugin.technical_review.Windows_IA32.testsuite
/org.eclipse.tptp.test.doc.user/manual/Doc/Test.Doc.Test_Log_Viewer.technical_review.Windows_IA32.testsuite

Comment 12 Paul Slauenwhite 2008-05-30 14:24:37 EDT

Patch approved and checked in to CVS (HEAD).

Comment 13 Paul Slauenwhite 2008-06-10 11:01:08 EDT

Verified in TPTP-4.5.0RC3-200806031051.  Closing.

Comment 14 Paul Slauenwhite 2008-11-27 19:29:07 EST

Approval request(s) no longer required.