[Windmill-dev] JS test suite or test setup/teardown

[Matthew Eernisse]

Mikeal,

Mikeal Rogers wrote:
> To me, I think having three options for JavaScript tests that all relate 
> to each other is a bit much. That's why I wanted to keep it all in the 
> filter= option.

Having actually spend a couple of days now developing tests, I think I 
have a pretty good idea of the basic workflow now.

As I mentioned in the previous mail, there seems to be a pretty clear 
logical separation between:

1. What test or set of tests I want to run

and

2. Which parts of the cycle I want to try to run

I really think it's easier to keep the two parallel commands instead of 
trying to take the Swiss army knife approach with one. It also might 
look cleaner from the comand line:

(Namespace, run setup & test)

filter=ns:test_pim.test_unsavedChanges, phase=setup,test

(Single-test, run test only)

filter=test_pim.test_unsavedChanges.test_clickLozengeDiscard \
  phase=test

I think I like 'phase' better than 'only' -- it's clearer, and more 
descriptive.

Hope that makes sense.


Matthew