Modify testcase collection in regards of collectionName parameter

[kmohr-soprasteria]

Currently parameter collectionName is set once for the complete collection. Would be better if this is done in each request

[kmohr-soprasteria]

• analysis of WredProfileConfiguration Validator:

  • collection info and server info is set in each request, depending on the target to which the specific testcase shall be applied
  • the target names (i.e. collectionName) are different for different test requests
  • i.e. the same collection contains testcases that are run against different servers

• NEP Basic test collection

  • all executed testcases shall be run against a single server during an execution run, not some requests against server1, and others against server2
  • therefore it's sufficient to just use the collectionName on collection level, rather than setting everything again in the requests
  • in case this would become relevant for later releases, it still could be set there

Note: some services also are offered by MATR, checking those should be possible with the same collection, however: in that case just the collectionName for the run must be changed - this could be done as an additional parameter in the loadFile (with nep being the default).

[kmohr-soprasteria]

Asked Thorsten on his feedback; in case this needs to be changed still, this will be done with spec_v1.0.1.

[kmohr-soprasteria]

Thorsten's feedback:

I only noticed later that the InterfaceValidator has to address different servers. Then of course I was happy that I had such a great, flexible structure ;) :)

I actually see this coming in all applications because:

• The applications should be tested against mocks or simulators.
• The TestCaseCollection should be supplemented based on Analysis or FriendlyUser observations
• New TestCases might require different inputs
• Other inputs are provided by other simulators
• Other simulators could mean: o Existing simulators are supplemented with additional paths o Additional simulators are placed next to them and addressed depending on the TestCase

The second variant is more flexible because the simulators can be created by different people without coordination. You don't need to change this now, but I suspect it would be better if the collectionName was set at the collection level.