Our roadmap for Q2 2021

Our roadmap for Q2 2021



Q2 2021 will be our second quarter in production and we would like to share our engineering roadmap for this quarter and see what you think of your roadmap.

Our main goal is to enhance your testing experience by offering many more features that helps you test APIs faster and easier so you should see lots of improvements by the end of this quarter.


Run tests without selecting an environment

Currently, you need to have an environment defined and be selected to run your test cases. The reality is that you don’t necessarily need an environment to run the tests, although it’s possible to have multiple environments and pick one but that shouldn’t be mandatory so we’re going to go ahead and make this potion. (Released on April 19th, 2021)


See test results while on test screen

This feature helps you to easily run tests, see the result and carry on with your TDD. No need to go back & forth between tests screen and result screen. (Released on April 26th, 2021)


Re-use random data generators and templates in different steps

Generating random data on the fly is a powerful feature, it allows you to replicate user’s behaviour and that’s why we included this feature in our V1. We’re going to extend this feature so that you can easily use a random value more than once in a test. Take for example a scenario in which you want to sign up a new user and login immediately. Using this new feature, you can add a random email in first step (sign up) and re-use the exact value (which will be calculated during test execution) as part of the login step.


Run tests before adding them to your account or saving them

Sometimes you need to run a test without adding it to your account or saving it to verify a quick change. This feature allows you to quickly run a test without storing it in your account.


Refer to values of different steps

Occasionally you need some data that are not random nor you have access them upfront. Sometimes the data you need is returned to you as response of an step. Take for example a scenario in which you add a product (step 1) and then fetch it (step 2). You need ID of the product to be able to fetch it and ID will be returned as part of step 1. Using the refer feature you can build test cases similar to this. (Released on May 17th, 2021)


Integration with CI tools & Github

This feature allows you to integrate Testfully with your CI to make sure tests continue to pass. Our goal is to provide a generic tool that can be used with many CI tools but also we’re thinking of a deep integration with Github. (Released on May 24th, 2021)


Store results of tests that are executed in browser

Using this feature, you can run tests in browser and keep the results in your account.


Re-run an executed test

This feature allows you to re-run an executed test with the same steps and payloads.


Post test execution hooks

Hooks allows you to take certain actions post test execution. We’re going to start with updating config values post execution of test.


Sign in with Google

Currently, you need to sign up using your email & password and we know not every one likes passwords so we’re planning to introduce “Sign in with Google” to Testfully. Password fans can continue to use their beloved passwords for login! (Released on April 19th, 2021)


That’s it! Plenty of feature to make it even easier to test your APIs. Don’t hestiate to reach out and share your thoughts with us about our roadmap via matt [at] testfully.io.

comments powered by Disqus

Recent Articles

blog-image
7 HTTP methods and how to use them

HTTP protocol works by clients sending requests to the servers and servers responding to the requests. We do CRUD operations (Create, Read, Update, Delete) by sending HTTP requests with different HTTP methods, sometimes called HTTP verbs.



blog-image
Introduction to API Blueprint

API blueprint is a powerful high-level API design language for web APIs. In this article, we want to dive deeper into it and learn more about how it works, the differences between API blueprint and Swagger, and what makes it unique that leads to its extensive use. But before we dig into API Blueprint, we must ensure a solid base of information about the “API first approach” concepts.

blog-image
False positive & false negative in software testing

Exports in automated software testing have borrowed false positive and false negative terms from the medical examination field. In the medical field, the purpose of a test is to determine whether the patient has a particular medical condition or not. As far as software testing is concerned, a false positive indicates a bug when there is none. Conversely, a false negative indicates no bug when there is one.