Note: This page is for discussion and aims to define the possible requirements for a simulator wrapper within pythonsdk-tests
Andreas Geissler Michał Jagiełło Illia Halych Krzysztof Kuzmicki
When we launch E2E tests, we sometimes need to launch third party simulator (e.g. pnf-simulator).
It would be a cool feature if we could have a wrappers within the pythonsdk-test to be able to start/stop/configure/launch REST API as a prerequisite steps.
It obviously depends of the simulators...and their ability to be controled and offer a REST API for the test.
We may however imagine to define an API that will allow the pythonsdk-test to consume such simulators.
Any simulator
- shall be hosted in dedicated repository (do one thing and do it well)
- shall include a docker build chain and be runnable trough a docker run command
- shall be available in the ONAP Nexus
Though the docker standard command, it shall be able to
- start the simulator
- start with specific configuration
- stop the simulator
If the feature is available, a REST API shall be available to reconfigure/trigger workflow.
The wrapper step within the pythonsdk-tests shall
- detect if the simulator is available or not (if not test shall fail immediately exception simulatorNotAvailable)
- launch the simulator
- get the simulator status
- stop the simulator
- exchange with the simulator if an API available
Open questions
use of submodule from pythonsdk to know the available simulators? customize configuration?