Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The E2E Call Flow Validation project would validate Use Cases defined in a BP based on the standard based messages, APIs, and any other external interfaces published by the BP. This project would use emulators to simulate other necessary peer nodes to perform e2e testing of the System Under Test BP. Since current and upcoming Akraino releases are targeting Application BPs like Network Nodes, VNF, etc. it is important to test Inter Operability between them to ensure that e2e uses cases are met. This would help the end-user of these BPs to determine the functionality and maturity of a BP. Having clear validation of these kinds of call flows would increase adoption of the BP, hence increase user acceptance. Moreover, Infrastructure level KPIs collected for the BP's would be more relevant if they are done for real use case specific traffic data. This project also analyzes the execution data and generates various analytics. The analytic insights help in debugging by identifying expected/published interface specifications and actual. Some standard test cases will be provided as default by the Call flow project team, additional test cases can be developed by the BP team members very easily. The Test Case format follows the BDD principles and is based on Opensource declarative language using Gherkin (https://cucumber.io/docs/gherkin/), which is English like, hence it is understandable by anyone with some domain knowledge of the BP.

...