Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: 3.7.5
-
Fix Version/s: 3.7.5
-
Component/s: Core
-
Labels:None
-
Environment:Hide$ mvn --version
Apache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600)
Maven home: /usr/share/maven
Java version: 1.6.0_51, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"Show$ mvn --version Apache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600) Maven home: /usr/share/maven Java version: 1.6.0_51, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
-
Number of attachments :
Description
When running several multithreaded JUnitStories, the tests run in multiple threads as intended but do not run concurrently. This is evident because when they're run and the steps are printed on the screen, all of them are separated by story and the test time isn't any faster than when one thread is run. When I ran the threads example from jbehave.org in multiple threads, I could easily tell all of the steps from the tests were running concurrently because different scenarios from different tests were all jumbled together when the test ran, but this is not the case when I run my tests.
Is there a specific reason my tests are not running in concurrency even though they are running in multiple threads?
Activity
Paul Clark
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Not A Bug [ 6 ] |
Actually was running stories in concurrency