...
- Short Description: Open discussion on performance and robustness tests
- Detailed Description: For the moment, most of the tests are functional tests. There is no real stress or performance test. There is 1 72h long duration test (stability test executed by integration team consistsing in runningvFW use case during 72h). These tests are usually complex to setup and requires resources. This session will question the sense of such tests within ONAP context and evaluate some scenarios.
- Topic Leader: Morgan Richomme
- Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 1-15
- Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.
...
Integration - Discussion on the test strategy evolution in ONAP
- Short Description: Discussion on the test strategy evolution in ONAP based on Integration team experience.
- Detailed Description:
Very ambitious test had been announced in the past (S3P, chaos monkey). However health check still does not guarantee a good integration, verified end to end use cases are sometimes very big and hard to automate and/or to reproduce in different environments. It is today not trivial to know which components are really used/covered through existing use cases. Basic Integration tests in the target environment are missing to guarantee a good quality of the solution.
More basic tests should be provided by the components to offer a better coverage of their APIs, interfaces and features. CSIT tests are not enough as they are run on non representative target environment and robot healthcheck tests are sometimes to high level to really indicate the health of a component. This session will address the question of the test strategy in ONAP.
- Topic Leader: Morgan Richomme Krzysztof Kuzmicki Marcin Przybysz
- Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 1-15
- Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.