TestCaseCollection Template shall be added

[openBackhaul]

It shall contain two sample test cases.
These test cases shall address /v1/bequeath-your-data-and-die.

Purposes of /v1/bequeath-your-data-and-die:

• Updating the *Client instances of NewRelease in the internal data structure
• Starting and executing the hand-over process

TC1 - Internal Data Structure properly updated?

• GET pre-test control-construct and store it
• Search UUIDs of TcpClient and HttpClient of NewRelease in pre-test control-construct
  Invent ApplicationName, ReleaseNumber, Protocol, Address and Port in such a way that it is very certainly not existing in the network
  Store invented address information
  POST /v1/bequeath-your-data-and-die with invented address information
• GET post-test ApplicationName, ReleaseNumber, Protocol, Address and Port via diverse OaM requests
  and compare with invented Input
  if ( post-test == invented ) => passed
• Search original (not pre-test!) control-construct for ApplicationName, ReleaseNumber, Protocol, Address and Port of NewRelease
  PUT original ApplicationName, ReleaseNumber, Protocol, Address and Port via diverse OaM requests

TC2 - Hand-over process executed?

• GET pre-test control-construct and store it

• Search UUIDs of TcpClient and HttpClient of NewRelease in pre-test control-construct
  Invent ApplicationName, ReleaseNumber, Protocol, Address and Port in such a way that it is very certainly not existing in the network
  Store invented address information
  POST /v1/bequeath-your-data-and-die with invented address information

• Search pre-test control-construct for UUIDs of TcpClient and HttpClient of EATL

• GET EATL://v1/list-records
  Filter list of records for ( operation-name == "/v1/bequeath-your-data-and-die" )
  Filter resulting list for ( application-name == ownApplicationName )
  Select instance with youngest timestamp from filtered list of records
  Store x-correlator from selected instance

• GET EATL://v1/list-records-of-flow for stored x-correlator
  (load new list, because further requests might have been recorded in meanwhile)
  Check, whether the list contains records of all requests required for handover at your individual application

• Search original (not pre-test!) control-construct for ApplicationName, ReleaseNumber, Protocol, Address and Port of NewRelease
  PUT original ApplicationName, ReleaseNumber, Protocol, Address and Port via diverse OaM requests

[openBackhaul]

Re-design of sample test cases addressing /v1/bequeath-your-data-and-die.

TC1 - Internal Data Structure properly updated?

• Search original control-construct for UUIDs of TcpClient and HttpClient that are indicating the NewRelease (with "-http-c-nr-" and with "-tcp-c-nr-")
  if not exactly one pair found: indicate error and jump to end of test case
  if exactly one pair found: store UUIDs of TcpClient and HttpClient of NewRelease
  Invent ApplicationName, ReleaseNumber, Protocol, Address and Port in such a way that they are very certainly not existing in the network
  Store invented address information
  POST /v1/bequeath-your-data-and-die with invented address information

• GET post-test ApplicationName, ReleaseNumber, Protocol, Address and Port via diverse OaM requests using stored UUIDs
  and compare with invented Input
  if ( post-test == invented ) => passed

• PUT original ApplicationName, ReleaseNumber, Protocol, Address and Port via diverse OaM requests

• CleanUp test case specific variables.

TC2 - Hand-over process executed?

• Search original control-construct for UUIDs of TcpClient and HttpClient that are indicating the NewRelease (with "-http-c-nr-" and with "-tcp-c-nr-")
  if not exactly one pair found: indicate error and jump to end of test case
  if exactly one pair found: store UUIDs of TcpClient and HttpClient of NewRelease
  Invent ApplicationName, ReleaseNumber, Protocol, Address and Port in such a way that they are very certainly not existing in the network
  Store invented address information
  POST /v1/bequeath-your-data-and-die with invented address information

• Search original control-construct for UUIDs of TcpClient and HttpClient of EATL (with "-http-c-eatl-" and with "-tcp-c-eatl-")
  if not exactly one pair found: indicate a warning and proceed with the pair of the highest sequence number
  store UUIDs of TcpClient and HttpClient of ExecutionAndTraceLog
  GET EATL://v1/list-records
  Filter list of records for ( operation-name == "/v1/bequeath-your-data-and-die" )
  Filter resulting list for ( application-name == ownApplicationName )
  Select instance with youngest timestamp from filtered list of records
  Store x-correlator from selected instance

• GET EATL://v1/list-records-of-flow for stored x-correlator
  (load new list, because further requests might have been recorded in meanwhile)
  Check, whether the list contains records of all requests required for handover at your individual application

• Use stored UUIDs of TcpClient and HttpClient of NewRelease for searching original ApplicationName, ReleaseNumber, Protocol, Address and Port of NewRelease
  PUT original ApplicationName, ReleaseNumber, Protocol, Address and Port via diverse OaM requests

• CleanUp test case specific variables.