Overview

  • The application test service provides a detection function for the application package and can be published to the applied commercial city only by using the test case of the application test service.

  • The application testing service is divided into the front and back platforms, atp is the background part, providing the main function interface for the foreground or other three-way system to call, atp-fe is the foreground part, providing the interface display.

  • Application testing services are currently divided into management functions and user functions. The management functions include the management of test scenarios, the management of test suites, the management of test cases, the batch import of model models, the management of test tasks, and the management of contributions, among which contribution management The menu for is only visible to the administrator. Administrators can dynamically add test scenarios, test suites and test cases on the management plane, modify the status of manual use cases in test tasks, and download test cases contributed by script types. For reasonable use cases, they will be added to the platform’s use case set . User interface functions include selecting scenarios to be tested, visualizing the testing process, displaying test reports, and contributing test cases. At present, the functions of the user plane are mainly integrated in the developer platform and the application store, and the generated application package is tested.

  • At present, the test cases cover security test (vulnerability scanning, signature verification, port scanning, virus scanning, etc.), compliance test (application package structure verification), Sandbox test (application deployment, MEP platform service registration update, etc.) and performance test (delay, CPU occupancy, memory occupancy, etc.)

Overall framework description

The EdgeGallery overall framework flow is as follows, the application test platform’s main corresponding graph in the authentication test section.

  • ATP-fe: Developer Platform foreground framework, developed using VUE.

  • ATP: Developer Platform Backstage Framework, developed using SpringBot + ServiceComb.(For ServiceComb, please refer to this: https://servicecomb.apache.org/cn/)

  • ATP DB: Backstage relies on Postgres database.

correspondence relationship between test suites, test scenarios, and test cases