Allow user to specify whether to run random, controlled or both types of tests globally about openactive-test-suite HOT 5 CLOSED

This is a global setting.

There is currently a useRandomOpportunities setting, this however only prevents deleting events rather than determining which tests to run.

Work needs doing to make this option used to determine which test suites need running.

from openactive-test-suite.

@nickevansuk Do we need a both option for this or just random and just controlled options?

from openactive-test-suite.

Suggest one or the other

from openactive-test-suite.

Additionally suggest a further improvement for the "controlled" version: just pass the case name to the "createOpportunity" test harness endpoint, instead of the full OpenActive model for the event (so just the name rather than the event from here).

This means they'd just need to create a switch statement inside the test endpoint to create the relevant type of event in the relevant state, instead of building a parser for an event in the OpenActive opportunity model, which they don't need anywhere else.

Especially as most elements of the parser would only be used once per test (as each test covers different properties), and otherwise the parser itself would need testing.

This should also mean that the "case" interface on the microservice can be identical to the "createOpportunity" test harness endpoint - passing both an opportunity type and a case name in both cases, and returning the ID of an opportunity in both cases. So the test harness endpoint will be modelled off this endpoint with an extra name query parameter - which should make it easy to use either the "random" microservice or the "controlled" test harness endpoints depending on the mode, as they will work identically.

This also means that we wouldn't need to separate "random" and "controlled" tests, as both could run in either case - which should simplify the design overall.

We can ensure that the .NET deployment does this in advance of the work.

from openactive-test-suite.

useRandomOpportunities config setting achieves this by utilising the standard test interface.

Only allows running controlled or random, not both, for simplicity. Both can be achieved by simply running the test suite twice, as per:

from openactive-test-suite.