just the facts

Frequently Asked Questions

You can find the most frequently asked questions here. We have categorised them into general and product-based FAQs.
If you have any further questions feel free to reach out to us, either via the contact button or chat – our team will assist you.

General FAQs

We know it is difficult where to choose from when you have so many options. TESTIFI enables businesses to deliver higher quality software with confidence by incorporating testing throughout the entire software development cycle through its unique testing tools.
We want to democratise testing within all levels of every business so that you don’t have to choose between speed of your release cycles and the quality of your software.


  • CAST (Complete Automation System Test)
    A highly flexible tool designed to enable full stack testing of both front and back-end systems through the building maintaining of automated tests in one central hub. It deeply integrates with the CI toolchain, including Jira and Xray, and supports web, desktop, mobile applications, backends and APIs.
  • Pulse
    A labour-free and AI-powered testing tool which measures the health of your APIs through code validation and improvement – and this in no time. Reduce your cycle times without compromising on quality. This is AI-powered automation at its best.


  • Training and enablement
    The process of adopting automation within a business means using a new tool and potentially adopting new processes.
    So that businesses get the most value out of automation, TESTIFI enables its users through a personalized onboarding journey based on the business’ specific needs designed to maximise the learning curve. This is realised through training courses and interactive workshops led by our Onboarding Specialist and Customer Success Manager.
  • Our consultancy and expertise
    As your success is important to us, we believe in accompanying you throughout this journey so that you can find the value you are looking for and grow successful in doing so. Our team of experts have (almost) seen it all, and so the sharing of knowledge becomes all the more crucial.
Different types of tests
  • End-to-end 
  • Unit 
  • Integration
  • Functional 
  • UI/UX 
Your tech stack
  • APIs
  • Windows, web, desktop applications
  • Mobile applications (including mobile behaviour emulation)
  • Databases

The process of using special software tools or scripts to perform testing tasks such as entering data, executing the test steps and comparing the results, etc. is known as automation testing.

Test automation is the process of putting automated tests inside of the CI pipeline to be run continuously every time a new line of code is committed.

TESTIFI:CAST enables the creation of domain-specific languages (DSL) for any applications and makes automated testing an accessible job function, even to those who do not have any programming knowledge. With CAST, setting up tests for automation becomes a quick process, and the interface is designed to make it user-friendly, unlike similar DSL tools.

As we want to build a tool that is most valuable to our users, we encourage any and all feedback provided, so that we can make their lives easier by making test automation a collaborative exercise.

Test automation is the first step of the journey leading to software excellence. Because this can be quite challenging along the way, our team of experts, as well as our dedicated Customer Success Manager, are there to enable you throughout that journey with regular collaboration meetings, workshops, trainings, and quarterly business review meetings.

Our goal is for you to succeed in delivering the best software quality out there, with shorter release cycles and through a test-first approach.

Please contact us via our chat or support info and we will provide you with all the other details you need.

Pulse FAQs

It is an automatic API test generator.

It analyses the API documentation, generates API tests according to details in the documentation and best testing practices, analyses and presents the results in easily consumable manner.

No coding and no implementation knowledge is required. The schema URL/file, server URL and authentication details are enough to start Pulsing.

It is possible but not mandatory to upload test data for some or all endpoints. Note that only positive examples needed to be added to generate a successful response, Pulse covers the negative examples by default. You can upload your test data file in the second step. The test data file should be structured according to the template which can be downloaded with the link in that same step. Another way the users can add the values as an example in the schema.

For more information to add the example values, please check Adding Examples (swagger.io). Pulse reads the values in the schema and creates the requests.

Constant values for Pulse refer to the value being kept constant while generating many of the requests. Users can add the constant values as a single Enum value shown as Enums (swagger.io) in the schema.

First register to Pulse, then whitelist https://pulse.testifi.io and if necessary.
You can now start testing your API by submitting your schema URL/file, the URL of the server and the necessary credentials for accessing your API. An email will be sent to you from Pulse once the test is complete.

First register to Pulse, then whitelist https://pulse.testifi.io and if necessary.
You can now start testing your API by submitting your schema URL/file, the URL of the server and the necessary credentials for accessing your API. An email will be sent to you from Pulse once the test is complete.

All tests are analysed by Pulse and the redundant tests are removed. Tests that represent characteristics (both intended functionalities and unintended implementations/bugs) of your application are displayed in a dashboard view and enable you to easily access the results.

Pulse tries to create appropriate data for each parameter. However, it may not be enough to have full coverage since some special values might be required for some endpoints. Entering sample values in example fields in the schema, at least in endpoints where records are created, will help Pulse have bigger coverage.
Using components and adding tags to the schema also improves the response code coverage.

Pulse creates the payload by itself by following various techniques to produce data comparable to human testers. It also analyses the dependencies between endpoints and organises execution orders and payload content accordingly.
Moreover, Pulse analyses the results to identify various errors in the responses and presents the results in an intuitive and visually-appealing manner.

Yes and no. We do not analyse the code to generate tests, but the API documentation provides an array of useful information to Pulse in order to generate tests.

Yes. Rest API is publicly accessible, and the necessary endpoints can be called into your pipeline.

Very soon. We are working on it.