New here? Testkube is a Kubernetes-native testing framework for testers and developers. It acts as an executor so you can orchestrate, run, and display tests and test results for your code in a Kubernetes environment. Whether you're new to the K8s ecosystem or a seasoned pro, Testkube lets you focus on testing without having to complicate yourself, your processes, or your pipelines.
Testkube v1.10 is out! This release includes important upgrades to enhance the Test Creation process, error reporting, support for running Playwright Tests, and a revamp to our documentation. Keep reading to find out what this means for your testing journey:
Create your Kubernetes Tests easily - we updated our test creation form
The most important and major update for our dashboard in its 1.10 version is all about improving user experience during test creation. For newcomers, basic test creation can be a rather challenging task because of the multiple inputs and choices, so we decided to simplify the process by providing an overall better experience with features like Documentation links, Tooltips, Placeholders, and more.
We also changed the order of our input fields, added executor icons based on your selection, and made the Path field optional.
Test Sources Based on Test Type
When selecting a Type of Test to create (Postman, Cypress, SoapUI, etc.), you also need to select a Test Source (for example, Git). However, not every source can be used for all tools, which added noise to the test creation process.
From this release on, you’ll only be allowed to select the Test Sources that apply to your Test Type.
To improve your user experience, we added Tooltips to most of the test creation modal fields, like Path or Git repository.
These aim to provide better user guidance throughout test creation and understanding what needs to be entered in each field.
Starting now, when you select a Test Type, you will see its icon and a link to its specific documentation to read more about it.
New Executor: Run Playwright Tests with Testkube
If you are already using it, you can read our docs or follow our tutorial to start running your tests in a cloud-native way.
Merging Git Directory and Git File into One Source
Prior to this release, Testkube supported 2 types of git based content: git directories and git files. Users had to specify exactly what was stored in the git repository, which would often lead to different errors and inconsistencies.
Starting now, you can simply point that content is git based and Testkube will automatically detect if it’s a file or directory.
Merging Envs and Variables
We decided to simplify and unify usage of these approaches by merging them. As for now, we deprecated env and secret env parameters.
You should be able to achieve the required behavior by using Basic and Secret Variables.
If you expect some test to fail and you want Testkube to report that everything is going as expected, you now have the possibility to set the tests as Negative Tests - thus expecting to fail. Tests will then report a Pass status if they failed as expected, or will show Failed if the test passed.
Access Test Suite Artifacts from the CLI
You can now see all the Artifacts (output generated Test files) for your Test Suites directly from your command line tool. Instead of having to check the execution for every test that runs as part of a testsuite, just run the following command:
testkube get artifacts <testsuite-execution-name>
Reasons for Test Trigger Conditions
In our previous release, we introduced Test Trigger conditions to specify the state of Kubernetes resources you might need in order to run any particular Test or Test Suite.
Following our community requests, we enhanced this feature by supporting the definition of Reasons for the resource state. This allows you to be even more specific about triggered events.
Find out how to set and define Test Trigger conditions and reasons here.
Mounting ConfigMaps and Secrets as Files into Test Pods
Recently, one of the most popular requests from our community was on mounting ConfigMaps and Secrets into Test Pods. From this release and on, you will simply need to provide ConfigMap and Secret names in order to achieve this.
Automatic Variable Creation
Now you can also automatically create Basic and Secret Variables from ConfigMaps and Secrets - and use them in your test scripts.
We recently realized some Testkube errors were not verbose enough, and did not offer a lot of help in finding issues. Although users that are familiar with Kubernetes may be able to debug errors themselves, we decided to make error reporting more approachable.
For this release, we started wrapping Test-related errors with clear and concise messages, and will continue to work on improving the messaging on other types of errors in our upcoming versions.
Larger, More Reliable File Uploads
Running tests that require additional input files was already possible in Testkube - so in this release, we added the `--upload-timeout` flag to the `testkube create test` and the `testkube run test` commands:
--upload-timeout string timeout to use when uploading files, example: 30s
This flag increases the HTTP client timeout, so that bigger size files can be uploaded from the CLI with no timeout errors. To address this on the server-side, we also increased the default body size limit to 1 GB.
We completely revamped our documentation site to give our new and existing users a much better experience.
You can find new Guides, more specific Executor pages, and plenty of resources to get you ramped up and testing with Testkube in no time.
Check out our new site in docs.testkube.io!
Interested in seeing how it all works? Catch the Testkube team’s demo on the v1.10 release through our livestream here:
Give it a go!
Why not check it out yourself? Testkube is Open-Source and we're always looking for feedback and contributions. Check us out at https://testkube.io
If you have any questions you can join our Discord community or, if you have any ideas for other useful features, you can create the feature requests at our Github Issues page.
If you’d like more info, or just to come say ‘Hi’ – join our Discord server and follow us on Twitter @Testkube_io. You can also email our Product Leader directly at firstname.lastname@example.org. We’re looking forward to hearing from you!