mardi 1 septembre 2015

Fitnesse suite initialization independance

We have a fitnesse suite that looks roughly like this

  • Suite 1
    • Suite 1a
    • Suite 1a SuiteSetup
    • Suite 1a Test 1
    • Suite 1a Test 2
    • Suite 1a SuiteTearDown
    • Suite 1b
    • Suite 1b SuiteSetup
    • Suite 1b Test 1
    • Suite 1b Test 2
    • Suite 1b SuiteTearDown
  • Suite 2
    • Suite 2 Test 1
    • Suite 2 Test 2
  • SuiteSetup
  • SuiteTearDown

Each of these suites initializes an spring context and all suites will work independently. All suites are using SLIM.

I am seeing an unusual initialization order though. A top level run will run the suites in the below order

  • SlimService initialization (outputs slim:fitnesse.slim.SlimService to the page)
  • Suite 1a SuiteSetup
  • Suite 1a Test 1
  • Suite 1a Test 2
  • Suite 1a SuiteTearDown
  • SlimService initialization
  • Suite 2 Test 1
  • Suite 2 Test 2
  • Suite 1b SuiteSetup
  • Suite 1b Test 1
  • Suite 1b Test 2
  • Suite 1b SuiteTearDown

I understand the fitnesse initialization order is not guaranteed (or even defined) but what I am not clear on is why SLIM only gets re-initialized between the finish of suite 1a and the start of suite 2.

I would expect it to either be - initialized between suite 2 and suite 1b also - only initialized at the beginning of the test run

Can anyone tell me what might be responsible for this?

Aucun commentaire:

Enregistrer un commentaire