3 Years in making, over 100 releases so far...

We’ve updated Testfully CLI to version 1.9.0. This release includes the following changes:

Support for $.request.skip() and $.setNextRequest() APIs

Last week we introduced two new APIs to the JavaScript API that you can use in your scripts: $.request.skip() and $.setNextRequest(). These APIs are now supported in Testfully CLI. You can use these APIs in your scripts to skip a request or set the next request to be executed in a folder run. For any skipped requests, Testfully CLI now includes an entry in the JUnit reporter and displays the skipped request in the logs.

High-Performance Verbose Mode in Testfully CLI

We’ve re-engineered the verbose mode in Testfully CLI to perform better under heavy load and to display detailed logs for each request in a more readable format.

Order of Execution in Testfully CLI

We’ve improved the order of execution in Testfully CLI to ensure that requests are executed in the correct order. This is useful when you have dependencies between requests and you want to ensure that requests are executed in the correct order. Also, the JUnit reporter now includes requests based on the order of execution.

We’ve updated Testfully Desktop and Testfully Web to version 1.129.0. This release includes the following changes:

Copy as cURL

You can now copy a request as a cURL command. This is useful when you want to share a request with someone else or when you want to run the request from the command line. To copy a request as a cURL command, hover over the request in the sidebar and click the ”..” button, then click “Copy as cURL”. The “Copy as cURL” option offers the following features:

• Variables (global, environment or folder) are replaced with their values so that the cURL command is ready to run.
• The cURL command includes the request method, URL, headers, cookies, params and body. To generate a cURL command for a single request, you only need a valid URL. Other request details are optional.
• Authorization settings are included in the cURL command, so you don’t need to worry about authentication. This feature is available for all types of authentication supported by Testfully.
• Shared headers and params (via the parent folder) are included in the cURL command.
• If you work with multi-step requests, each step is included in the cURL command.

Terminate a Folder Run in Progress

Sometimes we need to stop a folder run in progress. For example, if a folder run is taking too long or if we realize that we made a mistake in the folder run configuration. Now you can terminate a folder run in progress by clicking the “Cancel” button in the folder run progress bar. When you terminate a folder run, the folder run stops immediately and the results are saved up to that point.

$.request.skip() and $.setNextRequest() APIs

We’ve added two new APIs to the JavaScript API that you can use in your scripts:

• $.request.skip(): This API allows you to skip the current request, it works when you send a single request via the “Send” button or when a request is executed as part of running a folder. This is useful when you want to skip a request based on a condition. If you’re coming from Postman, you will be pleased to know that pm.execution.skipRequest() is also supported. The $.request.skip() API is available in the before-request phase and won’t have any effect in the after-request phase.

• $.setNextRequest(requestName): This API allows you to set the next request to be executed in a folder run. This is useful when you want to dynamically change the order of requests in a folder run based on the results of the current request. The $.setNextRequest() API is available in both the before-script and after-request phases of a request. To terminate a folder run, you can use $.setNextRequest(null). If you’re coming from Postman, you will be pleased to know that postman.setNextRequest(requestName) is also supported with the same behavior.

Inspect skipped requests

When a request is skipped, you can now inspect the request details and any available logs. This is useful when you want to understand why a request was skipped or when you want to debug your scripts.

Improved Basic, Bearer and API Key Authentication

We’ve improved the way Basic, Bearer and API Key authentication is handled in Testfully. Now, when you set up Basic, Bearer or API Key authentication, there will be a default value for header names, which you can change if needed. This makes it easier to set up authentication for your requests.

Bug Fixes

• Fixed an issue where some of the requests that were created in earlier versions of Testfully could not be duplicated.
• Fixed an issue where an invalid AWS Signature V4 token was generated when the request had one or more query parameters.

We’ve updated Testfully Desktop and Testfully Web to version 1.128.0 and Testfully CLI to 1.8.0. This release includes the following changes:

Disable SSL Certificate Validation in Testfully CLI

Testfully CLI now supports disabling SSL certificate validation for requests and folders, so if you have a self-signed certificate, you can now use Testfully CLI without any issues.

Improvements

• The default mode for running tests in Testfully Web and Testfully Desktop is now Serial instead of Parallel. If you want to run tests in parallel, you can change the mode in the settings.

Bug Fixes

• Fixed an issue where the Testfully Desktop would timeout after 30 seconds when trying to connect to an API that was taking longer to respond, even though the timeout was set to a higher value. You can now set the timeout value to any value you want, and Testfully Desktop will wait for the response.
• Fixed an issue where Testfully Offline (Windows) would not be able to import large collections of requests.
• Testfully Offline now correctly imports requests without a parent folder. Previously, requests without a folder would be imported into the root folder, but now they are imported under the correct parent folder.

We’ve updated Testfully CLI to 1.7.0. This release includes the following changes:

Test Reports

Testfully CLI can now generate test reports in JUnit format. You can generate test reports by using the --reporters option with the run command. For example, you can generate test reports using the testfully run rick-and-morty.json --reporters junit command. If you want to specify the directory/file path to export the JUnit report, you can use the --reporter-junit-export option. For example, you can use the testfully run rick-and-morty.json --reporters junit --reporter-junit-export ~/Downloads/junit-report.xml command. To learn more about the --reporters option, see the Testfully CLI documentation.

We’ve updated Testfully CLI to 1.6.0. This release includes the following changes:

The --globals and -g options for the run command

The --globals or -g option allows you to provide a JSON file that contains global variables to use in your requests. The global variables are available in all requests in the file. If you provide global variables in the environment file, the global variables in the environment file take precedence over the global variables in the globals file. To learn more about the --globals option, see the Testfully CLI documentation.

Default command for Testfully CLI

We’ve added the run command as the default command for Testfully CLI. You can now run requests without specifying the run command. For example, you can run requests using the testfully rick-and-morty.json command.

To update Testfully CLI to the latest version, run the npm install -g @testfully/cli@latest command. To verify the version, run the testfully --version command. At the time of writing, the latest version is 1.6.0.

We’ve updated Testfully Desktop and Testfully Web to version 1.127.0. This release includes the following changes:

Export & Import Workspace Globals

• Workspace globals are now available for export in the desktop and web apps. This feature allows you to export workspace globals to a JSON file and import them into another workspace.
• You can now import a JSON file containing workspace globals into a workspace.
• When exporting a workspace to a JSON file, you can now choose to include or exclude workspace globals.

We’ve updated Testfully CLI to version 1.5.0. This release includes the following changes:

New Features

• The latest Testfully CLI update (version 1.5.0) now includes a useful --environment option. This feature allows you to specify a path to an environment file. Testfully will then utilize this file to load various variables and settings. For detailed information on how to make the most of the Testfully CLI and the new --environment option, please visit our Testfully CLI reference documentation.

We’ve updated Testfully Desktop and Testfully Web to version 1.126.0. This release includes the following changes:

Improvements

• Testfully Offline comes with a brand-new import engine. It’s now faster and more reliable than ever before to import your data from other systems.

We’ve updated Testfully Desktop and Testfully Web to version 1.124.0. This release includes the following changes:

New Features

• Text fields in a multipart/form-data request body now support custom content types. Previously, this was only possible with file fields.
• You can now have multiple multipart/form-data text or file fields with the same name. This is useful when you need to send multiple files with the same name in a single request or when you need to send multiple values with the same name in a single request.

We’ve updated Testfully Desktop and Testfully Web to version 1.123.0 and Testfully CLI to 1.4.0. This release includes the following changes:

Improvements

• Testfully Web, Desktop and CLI now support a global object called globals. This object can be used to access current global variables in your before/after scripts. Primarily, this is useful for folks who are switching from Postman to Testfully and have a lot of scripts that rely on the globals variable. $.globals.toObject() is a superior way to access global variables in your scripts.

• Testfully Web, Desktop and CLI now support the pm.info variable. Folks who are switching from Postman to Testfully and have a lot of scripts that rely on the pm.info can now use this object.

Fixed

• Fixed an issue with Testfully CLI where an After Script was erroring out when response headers contained a Set-Cookie header.

We’ve updated Testfully Desktop and Testfully Web to version 1.122.0. This release includes the following changes:

Improvements

• Testfully Cloud & Offline users can now disable SSL verification at the folder-level. Previously, this option was available for each request or for an environment.

We’ve updated Testfully Desktop and Testfully Web to version 1.121.0 and Testfully CLI to version 1.3.0. This release includes the following changes:

Improvements

• Testfully Cloud and Offline users can specify a delay between requests in a collection/folder run using a new delay field in the collection/folder settings. This is useful when you want to simulate a real user’s behavior, or when you want to avoid overloading your server with too many requests at once.

• Testfully CLI now honors the new delay field in the collection/folder settings when running a collection/folder.

• Testfully CLI offers a new --request-delay option to specify a delay between requests when running a collection/folder. This option takes precedence over the delay field in the collection/folder settings.

• Schema Validation (contract testing) now supports iterating over an array of primitive values or objects and validating each object against a schema. Previously, you could only validate the first element in the array. Also, you can now validate API responses that contain a root-level array.

• Testfully CLI was updated to the latest version to support the new schema validation features.

• Testfully CLI now supports signing requests using the AWS Signature Version 4 signing process.

• We’ve upgraded the engine behind our API monitoring feature to support schema validation.

• Environment-based authorization is now available for API monitoring. This means you can now set up different authorization settings for each environment in your API monitoring configuration.

We’ve updated Testfully Desktop and Testfully Web to version 1.120.0. This release includes the following changes:

Improvements

• Testfully Cloud and Offline users can now authenticate API requests using the AWS Signature Version 4 signing process. This is useful when you want to access AWS services using Testfully.

• AWS Signature Version 4 signing is now available for folder-based or environment-based authorization.

We’ve updated Testfully Desktop and Testfully Web to version 1.118.0. This release includes the following changes:

New Features

• Testfully Desktop now supports cookies. You can now view, add, edit, and delete cookies in the Cookies tab of the request editor. This is useful when you want to test how your application behaves when cookies are present or when you want to test your application’s security features.

• Cookies are automatically captured and sent with requests using Testfully’s new Cookie Manager (jar).

We’ve updated Testfully Desktop and Testfully Web to version 1.116.0 and Testfully CLI to version 1.2.0. This release includes the following changes:

Improvements

• Testfully Desktop users can now set a custom callback URL for their OAuth2 authorization flow. Previously, the callback URL was fixed to https://app.testfully.io/oauth2/callback. We’ve received feedback from users that their organization prefers to not use the Testfully callback URL. Web users should continue to use the Testfully callback URL as it’s the only supported option right now.

• When activating a new license, things should be a bit smoother now, with fewer errors and more helpful messages.

• Testfully CLI supports legacy Postman API and can import npm packages.

Bug Fixes

• Fixed a bug where the Testfully Desktop app would be unable to get the OAuth2 token for some users and would show an Internal Error message.

Introducing NPM package imports

We’ve added support for importing NPM packages directly into your code. This is a great way to use existing libraries in your code to implement things like encryption, hashing, validation etc. This feature is avaialble via a Plus or Premium subscription or a Testfully Offline Pro license.

To learn more, please check out the Using npm packages documentation.

Today, we released Testfully 1.111.0 for all users. This release includes a bunch of bug fixes and improvements.

Improvements

• Testfully now remembers the last selected tab for a request, an environment, a folder or the response widget. This means that when you switch between requests, environments, folders or response widgets, Testfully will remember the last selected tab and will automatically select it for you. This is a small improvement but it will save you a lot of time when you are working with multiple tabs.

• Response widget now remembers the last selected tab for a previous request and uses it for the next request.

• Available ID Token for OAuth2 authorization requests is now displayed in the authorization tab.

• Testfully now supports a range of Postman legacy scripting APIs including postman.setEnvironmentVariable, postman.getEnvironmentVariable, postman.clearEnvironmentVariable, postman.setGlobalVariable, postman.getGlobalVariable, postman.clearGlobalValue, postman.getResponseHeader, responseCode, responseHeaders and tests object for automated testing.

Bug Fixes

• Fixed an issue where the response widget was not displaying the response body in Firefox.

We’ve released Testfully Desktop and Testfully Web 1.105.0 with the following improvements and bug fixes.

Improvements

• We’ve introduced a new global variable to Testfully Scripts called responseBody to make it easier for folks who are switching from Postman to Testfully to have fully working scripts. The responseBody variable is a string representation of the response body. We recommend using the $.response.body instead of responseBody in your scripts as it’s more explicit and easier to understand.

Bug Fixes

• Curl commands with escaped quotes in the request body are now correctly imported into Testfully.
• Some Postman Collection 2.0 and 2.1 requests with Url-encoded payload were not imported into Testfully due to a bug in the Postman Collection parser. This issue has been fixed.
• Fixed a bug where Form-data requests with empty files were not imported into Testfully from Postman.
• Testfully Offline users could not save changes to their multi-step requests. This issue has been fixed.
• Menu for a multi-step request was not fully visible when the request payload tab was selected. This issue has been fixed.

Work with XML & SOAP API Endpoints in Testfully

XML support is finally here! You can now work with XML API endpoints in Testfully and inspect the response body using a dedicated XML inspector. We’ve also added support for Yaml, HTML, Javascript, and plain text responses and request bodies. This means you can now work with any API endpoint in Testfully, regardless of the response type.

A brand new Response Inspector

Building the XML support allowed us to rethink the response inspector in Testfully and offer a better experience. The new experience is available for all response types and allows you to:

• View syntax-highlighted responses for JSON, XML, YAML, HTML, Javascript, and plain text responses.
• Collapse and expand any node in the response body.
• Search for any node in the response body using the search bar (CMD/CTRL+F).
• Copy and paste the response using CTRL/CMD+C and CTRL/CMD+V.

Testfully CLI

We’re excited to announce that we have released a brand-new Testfully CLI, compatible with both Testfully Cloud and Testfully Offline workspaces. It’s a privacy-first, robust, and cloud-free CLI that allows you to run your tests from your local machine, or your CI/CD pipeline. Running your tests is as simple as exporting your data, and running a single command. The CLI is available for Windows, macOS, and Linux, and can be installed via npm.

To learn more about Testfully CLI, check out our documentation.

Other Improvements & Bug Fixes

• Easily import Open API Spec 3.0 and 3.1 files into Testfully, available in both Testfully Cloud and Testfully Offline workspaces.
• Testfully imports XML, HTML, YAML, Plain Text, and Javascript responses and request bodies from Postman and Insomnia.
• We fixed a bug that caused Testfully not to import multi-line cUrl commands.
• We fixed a bug that caused Testfully to not be able to import an exported Testfully folder.
• Relocating a request to a different folder wouldn’t result in using the folder variables of the new folder. We fixed this bug and now Testfully uses the folder variables of the new folder when relocating a request immediately.

Work with folder variables in your scripts

Variables (environment, folder, collection, global) are a great way to store and reuse values across your requests. $.globals and $.environment enabled our users to work with global and environment variables via code. Starting today, you can leverage $.parentFolder.variables and $.rootFolder.variables to work with folder variables.

With the addition of these APIs, you have programmatic access to all variables (global, environment, folder, collection) in your Testfully scripts. To learn more about the new APIs, check out our documentation.

BDD-Style Testing in Javascript Now Available in Our API Client

Two new APIs, endless possibilities. You can now use the BDD-style API Testing to write your API tests in Javascript using test and expect APIs. This allows you to write your tests in a more human-readable way, making it easier to understand what your tests are doing.

If you’re coming from Postman, you’ll feel right at home because the syntax is not only identical but also we support pm.expect and pm.test APIs.

To learn more about API testing and other Testfully Scripts capabilities, check out our documentation.

Import cURL commands

cURL is the de facto standard for sharing API requests. To help you get started with the API, we’ve added the ability to import cURL commands into Testfully. To learn more, check out our documentation.

Request Timeout Settings

You can now configure the timeout setting for requests. This is useful if you have a slow connection to the API or if you are using a proxy that has a timeout. The default timeout is 30 seconds. This release offers the following features:

• Adjust Request Timeout settings for a request, folder or environment. Learn More.
• Exporting and importing Testfully folders, requests or environments include the timeout settings.
• The sendRequest function in the Testfully API now accepts a timeout parameter. Learn More

Before & After Request Scripts

Being able to run custom Javascript code before or after a request was by far the most requested feature in the last few months. We’re excited to share that this feature is now available for both Testfully Cloud and Testfully Offline. Starting today, you can enhance your request, automate repetitive tasks, and implement custom workflows using Javascript.

We have designed this feature to be compatible with Postman’s pre-request and test scripts. If you’re migrating from Postman, you can easily import your Postman collection to Testfully and your scripts will work as expected.

To learn more about this feature, please check out our documentation.

Export & Import Testfully Environments

Testfully Cloud and Offline users can export & import Testfully environments. To learn more, please read this article.

• Fixed: We’ve resolved an issue related to missing header name when exporting requests or folders with Basic Authorization scheme.

• Export Testfully Offline Workspace Data: Similar to Testfully Cloud workspaces, Testfully Offline workspace data can be exported and imported. To learn more, please read this article.

• Import Postman Environments You can now import your Postman environment files through the API Client interface. Additionally, Testfully now supports importing environments directly from Postman Backup files.
• We’ve resolved an issue related to not being able to add or update global values in some edge cases.
• We’ve fixed an issue related to importing Insomnia files with variables using the {{ _.['variable-name']}} format.

• Import a Postman backup (dump) file The latest version of Testfully supports Postman Backup (dump) files in JSON format. You can use this feature to import multiple collections, folders, and requests in one go. If you have a .zip file, please extract and upload files individually.

• We’ve resolved an issue related to some of the requests not being imported due to the long request title.

• Testfully Offline, your cloud-free API client is HERE! Download the latest version of Testfully Desktop Apps via the download page to start using Testfully Offline.

• We’ve resolved an issue related to receiving You don't have access to the workspace when switching between two Testfully accounts.

• We’ve resolved an issue related to tabs constantly switching between themselves.

• Audience for all OAuth2 grant types When doing OAuth2 authentication, you can use the “Audience” field for all grant types. Previously, this field was only available for the Client Credentials grant type.
• We’ve resolved an issue with the desktop version of Testfully where it was incorrectly sorting fields within JSON request payload fields alphabetically instead of preserving the user-provided order.

• HTTP Proxy is here! You can now send HTTP requests via your HTTP proxy of choice. To learn more, please read this article.

• We have introduced a new editor for the JSON fields. It makes the editing experience of JSON input values much more pleasant and offers a range of new features including search, auto-format, code indention, and find & replace.
• Fixed an issue related to using the OAuth2 authorization feature for getting a valid token from a Microsoft Azure AD tenant.

• Fixed an issue related to unsubscribing from our mailing list via the provided link in the What’s New in Testfully newsletter. We have also unsubscribed users who could not unsubscribe from the newsletter due to this issue.

• Rather than showing Access Denied error when a user accesses restricted areas (for example, user management), we no longer show unavailable menu options to the user.
• We have rolled out a series of changes related to our infrastructure to improve the performace of both desktop and web apps.
• Desktop app no longer rejects invalid JSON payloads, allowing testing of API behavior with invalid input data.
• Fixed issue with Testfully rejecting requests with {{}} in the payload, improving app flexibility.
• Issue resolved: saving requests with {{}} in the payload is now possible in the app.
• A visual bug related to the navbar in Firefox is now fixed.

• Easily export your folders and requests by clicking a few buttons starting today. Find more information in the How to export your data article.
• Utilize Testfully’s Importer tool to import the data you have exported using our Export tool.
• We have fixed an issue related to processing Postman Collection 2.0 files that were exported using old versions of Postman.

• Testfully supports Postman Collection V2.0 as well as V2.1.
• When importing Postman collections, Testfully brings collection variables & auth settings, folder auth settings and request auth settings.
• Import collections to the root of your workspace by clicking on the ”+” icon, and selecting “Import”.
• We have improved the overall UX of our Import tool to ask fewer questions from the end-user, and offer a better experience when importing data goes wrong.