Testkube 1.14 Release Notes

Sep 20, 2023
3 min
read
Testkube v1.14 is live! This is a huge release, with many important upgrades to Testkube’s functionalities and developer experience.
Share on Twitter
Share on LinkedIn
Share on Reddit
Share on HackerNews
Copy URL

Table of Contents

Want to learn more about this topic? Check out our Office Hours sessions!

Get Started with Testkube Pro

‍New here? Testkube is a test execution and orchestration framework for Kubernetes that works with any CI/CD system and testing tool you need, empowering teams to deliver on the promise of agile, efficient, and comprehensive testing programs by leveraging all the capabilities of K8s to eliminate CI/CD bottlenecks, perfecting your testing workflow.

Read on to find more about what this new release brings:

New Executors: Pytest and kubent

Testkube has native support for Pytest starting with 1.14. You can now effortlessly and intuitively run Pytest tests to take your testing efforts to the next level.

Read more and check out examples here.

We also added support for kubent - a great tool to check for deprecated APIs at any point for your Kubernetes APIs. Walk through our documentation to get started.

Test Execution as CRDs (powering GitOps)

Tests can now be triggered by deploying CRDs! Read more in our documentation.

Pre-run & Post-Run phases for container executors 

Previously, users were able to run pre-run and post-run scripts only for Testkube prebuilt executors. After this release, users will be able to use them for container executors with any image. We dynamically analyze Docker image metadata and prepare entrypont.sh on a fly based on Test Parameters.

TestTriggers to support probes conditions

There's a new way to trigger tests, supporting probe conditions. Check out the documentation here.

Add Test labels to pods and jobs

Starting now, foreach test we run we'll automatically add its labels to corresponding pods and jobs, so they can be analyzed using different monitoring and configuration tools.

Artifact Scraper generic artifacts storage

By default, Testkube collects test execution artifacts in a form of the zipped archive before sending it to Minio, which automatically extracts files to the bucket folder. Since not all cloud storage providers support automatic file extraction - and if you store your test reports directly in the Cloud avoiding Minio usage - you will end up with a zipped archive as a test result.

In order to improve this, we introduced the helm chart var`testkube-api.storage.compressArtifacts.If you set it false, then all files will be stored without archiving

Read more about this here.

Use environment variables in webhook payload

You can now use environment variables as part of your webhooks payload. Read more here.

UI Improvements

Improved mobile experience

Stay on top of everything on the go - Testkube’s UI is now fully responsive and the dashboard is accessible from your mobile phone!

Added post-run command fields on the dashboard

You are now able to change both the pre-run and post-run commands for the Tests through the Dashboard.

Display current kube container image and helm chart version in the dashboard

Now, you can easily check the current version for debugging purposes, by checking the “Your Testkube installation” block in general settings on the Dashboard.

Parallel tests executions

The interface for the Test Suite steps management has been redesigned, so it supports easily modifying Test Suites under a drag-and-drop interface, which even supports adding delays and steps in parallel.

Added Webhooks configuration page

You can completely manage Webhooks from the Dashboard now.

Give it a go

Why not check it out yourself? Try Testkube at https://cloud.testkube.io

If you have any questions you can join our Slack community or, if you have any ideas for other useful features, you can create the feature requests at our Github Issues page.