Community
Participate
Working Groups
- Create a test suite with a test case - Create a second test suite with another test case - Create a third test suite that references the first and second test suite When the third test suite is invoked it's expected for the runner to walk throught the behavior of the first and second test suite and invoke their test cases.
Planning to defer to post 4.3
Deferring to 4.4 according to Paul’s recent e-mail.
Updating original estimate based information provided by Liz.
Targeting to future since cannot be contained in 4.4.
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4. All other Test Project defects have been targeted to future. If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org). We will collectively triage and assess our resources to determine a case-by-case decision.
Correction: The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
After further consideration, this is being included in the 4.4 plan. I have changed the target and priority to reflect this.
Updating target to 4.4i3 as 4.4i2 ends 03/16/07.
Cindy, is this what you were experiencing today? If so, please note that it is included in the 4.4 plan and so it should be completed in i3. Hopefully the workaround solved your problem from tonight.
Increasing severity since this defect is impacting our users and internal test bucket.
Updated sizing as this was never implemented in the AGR.
Added test case 'TestSuiteReference' to the test suite 'Test.UI.AutoGUIRunner' in HEAD. The test suite covers the case outlined in the original description.
Created attachment 68797 [details] Patch Paul, please review this patch. Note that you need to include external Object mines when adding an external Test Suite so that the Object IDs can be found.
Updated hours worked. This took a lot of testing since there are so many cases to consider (Loops, combinations of test cases and suites etc.)
(In reply to comment #15) > Created an attachment (id=68797) [details] > Patch > > Paul, please review this patch. Note that you need to include external Object > mines when adding an external Test Suite so that the Object IDs can be found. > Patch reviewed. Please make a request to the Test Project mailing list for this defect. Once the fix is integrated, please add a comment to this defect containing the build ID of the driver used to verify the fix before marking the defect as fixed. Please make sure the copyright dates are incremented, if necessary.
(In reply to comment #15) > Note that you need to include external Object > mines when adding an external Test Suite so that the Object IDs can be found. > Would not the object minds be referenced by the invoked test suite and thus could reside in the invoked test suite?
It treats the Test suite invocation as an ExtendedTestInvocation which is associated with a 'Test' that can be either a case or a suite. I haven't pulled in Object mines automatically because of the potential for conflicts.
Patch checked in to HEAD. I will verify the fix in the next build before closing.
Fix verified in May29 build. Closing.
Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks.
Verified in the 4.4i4 TP2 driver.
Closing
(In reply to comment #17) > (In reply to comment #15) > > Created an attachment (id=68797) [details] [details] > > Patch > > > > Paul, please review this patch. Note that you need to include external Object > > mines when adding an external Test Suite so that the Object IDs can be found. > > > > Patch reviewed. Marking as reviewed.
