Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Table Of Contents


Addresses  CPS-188 - Getting issue details... STATUS


Overview

CSIT (Continuous System and Integration Testing) is expected to be a part of automated verification procedure invoked on review and merge stages.

The tests are executed as a Jenkins jobs which performs following:

  • Builds an image within a local docker (no publishing)
  • Executes the integration testing using shell script which 
    • on startup stage - creates and starts the docker containers based on image built together with other containers required (using docker-compose),
      ensures the application is initialized
    • on test execution stage - executes integration test suites using Robot framework
    • on tear down stage  - stops and removes containers
  • Collects the Robot framework reports

More details on flow: Project-specific CSIT structure

CSIT Migration Notes

Previously all the CSIT tests for all the ONAP projects were allocated in a same repository  integration/csit

Using shared repository did cause organisational difficulties (review approval etc) maintaining the tests, so it was decided to store CSIT tests on a per project basis.

More details: Moving CSIT to project repositories


Implementation approach

Test resources


Jenkins jobs


Resources


  • No labels