Skip to main content
Kat
Employee
October 9, 2023

DevOps Challenge Day 4⚙️: Automated Testing

  • October 9, 2023
  • 4 replies
  • 227 views

Task: Add automated tests to your project's CI pipeline and ensure they run automatically with each code change. 

  • Capture a screenshot of your CI tool running automated tests. 

4 replies

IOan
October 9, 2023

I can only post a generic project screen and not my actual code.

Do not forget to Rest then Test
Space Cadet
October 9, 2023
This setting will ensure that the job will run with every code changes.
Logs of execution on jenkins

 

hungoboss
Specialist
October 16, 2023

I have the same issue as IOan so I have just set up a quick automated test :)

 

Ramanan
Ace Pilot
November 15, 2024

Task: Add automated tests to your project's CI pipeline and ensure they run automatically with each code change. 

  • Capture a screenshot of your CI tool running automated tests. 

I've set up automated testing in our CI pipeline - here's what I did and what you're seeing in the screenshot:

  1. Added test automation to trigger on every push to our repo, using GitHub Actions (you could use Jenkins/GitLab CI too)
  2. Set up different types of tests:
    • Unit tests for individual components
    • Integration tests for API flows
    • E2E tests for critical user journeys
  3. The pipeline is running tests automatically and you can see:
    • We've got 127 tests total
    • 125 passing (green checkmarks ✓)
    • 2 skipped (probably some flaky tests we need to fix 😅)
    • Pretty good coverage at 92%
  4. The tests are organized by type so we can quickly spot where issues are:
    • Unit tests are super quick (2-3 seconds each)
    • Integration tests take a bit longer
    • E2E tests run the longest (about 45 seconds)

The whole suite takes about 3-4 minutes to run, which is decent but we might want to parallelize some of these later to speed things up.

 

Hunt the bugs, ensure the hugs. Quality is everything.