Introduction We are working on a series of improvements to our platform. These consists of Improving support for parallel test runs Better job distribution Support for multi-agent tests Test handoff Improving parallelism stems from the need to shorten execution times. In end-to-end tests, execution times are often very long. In a tool where test creation is fast (such as Boozang), long execution times dictate the upper limit of test coverage. […]
In this article we do a deep-dive on Team work support in Boozang. We talk about why web-based solutions are ideal for team collaboration, and discuss best-practices around access policy.
This article explains how to use GitHub as a repository for Cucumber feature files, and how to synchronize these with Boozang.
This article explains how to use branch and merge functionality in Boozang, and how to align your test automation work in a software project running on several branches at once.
In this example, we look at how we can auto-generate API tests from UI tests in Boozang using “Generate API” play mode.
In this example, we use the great json-server from Typicode to demonstrate the API testing functionality of Boozang.
Boozang takes an object-oriented approach to testing. Just like your application can be divided into modules and sub-modules, so can your tests.
Complementing Boozang’s excellent data handling capabilities is now the ability to use data from external sources.
In order to facilitate CI server integration and being able to run tests from command line we have built a client-side test runner based on the excellent Google Puppeteer.
Codeless testing that works. No credit card or commitment required.
