How-To: Jikken and CI/CD

Published on 2024-11-01 by Cameron Besse

So you’ve installed Jikken, tried it out, and written yourself a nice little stack of tests.

…now what?

Wouldn’t it be nice if those tests could just run automatically, every time a code change was merged? Then you would know immediately if a new bug was introduced, or if a regression reared its ugly head yet again.

Well, you’re in luck, because they can, and we’re here to show you how!

In our latest documentation article, we delve into what’s needed to enable Jikken test execution in your existing CI/CD pipeline. (Spoiler alert, it couldn’t be easier!) We review installation methods, discuss environment variables and secrets, and provide basic examples of what your configuration could look like if you use GitHub Actions, CircleCI, or Jenkins to deploy your application.

So go check out our new CI/CD integration guide, and get your automated Jikken test machine up and running today! 🤖

Psst… Did you know that Jikken also offers a web platform? There, you can review your test results, track your sessions and performance over time, and configure alerts so you’ll be notified via Slack or email when any test fails!

Check out our pricing page to sign up for access to these features (and more!).