Community
Participate
Working Groups
Try any of the testcases from Test.Execution.AutoGUIRunner testsuite. The launch configuration job hangs at 50% when a manual testsuite is already launched (like Test.Execution.AutoGUIRunner). The problem might be with the underlining infrastructure.
This happens also for when the second launched testsuite is a manual testsuite, it might happen for JUnit tests also.
Marius, The test execution harness can only run one test suite at a time. Please use a different workbench to run the automated tests in.
Parallel execution of tests is proposed under enhancement https://bugs.eclipse.org/bugs/show_bug.cgi?id=162605.
Note that the execution harness used to support parallel execution of tests. That capability was removed as a broad brush attempt to address some reliability problems with test execution. I have lobbied to get this capability put back in. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=162605
I find this as a very annoying and important problem, I see it more like a bug than a feature, I would like to contribute at fixing this as soon as possible. Do we mention this behavior anywhere in our docs (user and SDK)?
(In reply to comment #5) > I find this as a very annoying and important problem, I see it more like a bug > than a feature, I would like to contribute at fixing this as soon as possible. I would like to discuss your willingness to contribute toward this feature. Can we consider this contribution in the 4.4 plan? > Do we mention this behavior anywhere in our docs (user and SDK)? No. Please open a defect.
Please use this bug to document in our user and SDK docs the limitation described above.
This doesn't really belong to an AGR/UI component. I'm changing the component to Test.Execution because it's a limitation in that component.
This is a normal defect (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html) so reducing the severity. Since we are in the last stage of 4.3 i3 and test execution has been serial since the start of the project, deferring to 4.4.
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.
Parallel test execution is supported as of TPTP 4.5.
Closing since originator's email address is no longer valid.
