Integrate UP9 into CI/CD Workflows

UP9 generates skeleton test-code immediately on the first pass of a new workflow. The more traffic observed by UP9, the more accurate the test-code becomes. Test-code becomes CI-ready once a high level of confidence is achieved.

Once you have installed and deployed UP9, generate traffic so UP9 can build skeleton test code. The more traffic, the more reliable and CI-ready the test code becomes.


The hands-off approach to create CI-ready test code is using a sidecar. The sidecar acts as a 'TCP dump' agent using the open source PCAP library. The traffic is being stored as a HAR file (JSON representation of traffic) and then processed by the UP9 modeler. As a result of the observed traffic, skeleton test code is created. The more traffic observed by UP9, the more accurate the test code becomes. Test code becomes CI-ready once a high confidence level is achieved. Generated test code represents user behaviors observed in service-traffic.

However, sometimes you will want to influence the test code and guide UP9 what to test and how.

You can influence the test code creation process in two ways:


When you would like to add specific workflows (e.g. edge-cases), you can use UP9's Puppeteer function to open a Chromium browser window and observe the traffic in that window. Go through the required Workflow using your Webapp in the Chromium browser window, and test code will be created following the session. New test code can be added and augment an existing test suite, or it can be added to a new test suite.


UP9 not only generates new test code, it also updates the test code every time a service architecture change is detected (e.g. a new API or a changed API). New test code is committed to Git and the test code is ready to run as part of your CI.


For support, feel free to use any one of the three: