Specs with the same name cause thread name exceptions when using async

Description

describe("failing tests", function(){

it("will fail on the second spec due to identical spec name based thread name", function(){});

it("will fail on the second spec due to identical spec name based thread name", function(){});

}, "async", true);

Activity

Show:
Adam Tuttle
July 14, 2014, 9:52 PM

I have also found that test suites with identical names will fail for the same reason:

describe("foo", function(){});
describe("foo", function(){});

— even if they are in different Test CFCs, because the restriction is thread-name per "page" (request).

My advice would be to add a counter to the unhashed string before hashing it, or something like that.

Brad Wood
July 14, 2014, 10:56 PM

Actually, I'm wondering if there's any reason to have predictable thread names at all. It might just be better to change the thread name to a #createUUID()#

Fixed

Assignee

Luis Majano

Reporter

Adam Tuttle

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure