I have a test suite suiteA that has both setup.sjs and suiteSetup.sjs. Nested within suiteA, I had a subdirectories for a related test: verify. This subdirectory had its own suiteSetup.sjs. This worked fine.
I added a new subdirectory remind that has a suiteSetup.sjs. Now when I run suiteA, tests fail because instead of running suiteA/suiteSetup.sjs, it's running suiteA/remind/suiteSetup.sjs.
The suite setup module is identified in the controller by calling test:list-from-database and taking the first module that passes is-suite-setup-module(.). It looks like the modules came back in alphabetical order (document order?) and so suiteA/suiteSetup.sjs was selected before suiteA/verify/suiteSetup.sjs, but suiteA/remind/suiteSetup.sjs messed up the order.
I have a test suite
suiteA
that has bothsetup.sjs
andsuiteSetup.sjs
. Nested withinsuiteA
, I had a subdirectories for a related test:verify
. This subdirectory had its ownsuiteSetup.sjs
. This worked fine.I added a new subdirectory
remind
that has asuiteSetup.sjs
. Now when I runsuiteA
, tests fail because instead of runningsuiteA/suiteSetup.sjs
, it's runningsuiteA/remind/suiteSetup.sjs
.The suite setup module is identified in the controller by calling
test:list-from-database
and taking the first module that passesis-suite-setup-module(.)
. It looks like the modules came back in alphabetical order (document order?) and sosuiteA/suiteSetup.sjs
was selected beforesuiteA/verify/suiteSetup.sjs
, butsuiteA/remind/suiteSetup.sjs
messed up the order.The fix may be as simple as changing the
cts:directory-query
andxdmp:directory
calls from "infinity" to "1", but I haven't tested that.