Our latest release introduces powerful new features like customizable test data generation, exportable playbook runs, and parallel test execution for playlists. You can now resize step editors, view playbook progress per test, and test web browser requests with ease. With improved workflows and new random functions, this update is designed to streamline your testing—download it now!
Setup a maximum number of tests to be run in parallel and even add a ramp-up as an interval before any next test is executed! This is adjustable per playlist in a playbook.
You can now view the progress of each test case in the upgraded playbook screen.
Do you want to test if the frontend sends the correct messages to the backend? It is now possible to capture this traffic and validate the API request and response in JOSF using the API actions.
Use specific filters to collect the captured network traffic to use them in your test.
After capturing a specific request, you can execute API Call actions against it, like the validating response body
Click and hold the left side of the step drawer change the width of the panel. Double click resets it to the default size and draging it al the way to the right side will trigger a minimized menu! This size is maintained across JOSF.
Upon opening a step, you can drag the width of the test step table to create more space for your test step editor. This width will be stored and used for each test step table. Double click the drag bar to restore its original width.
The Faker library adds a lot of randomly generated data to your test case.
Most functions are now dot (.) separated and during the autocomplete on functions, this is now visible.
After pressing the ‘export run’ button, you can print the report to a PDF or a printer!
Show only failed tests or collapse all test tables and add management summary before printing!
Say goodbye to the Object and Data fields! The required fields for actions are now labled by what is expected. For example, all the verification actions now have a ‘Expected’ and ‘Actual’ field, in stead of the object and data fields.
Sometimes you need to skip a test case during a playbook run. This toggle keeps your test in the playbook, but does not execute it and mark it as SKIP. Enabling this toggle requires you to fill in a Skip reason, to easily keep track of the reason this test case is skipped.
On the test case details, you are now able to add an issue tracker link or comment.
Previously, conditional groups based on test steps, would mark the executed step as FAIL or ERROR, when false. Now it will mark it warning (yellow)
Is your license almost expired? You will receive a notification in JOSF of how many days until expiry.