Bugs end up in production all the time, despite our collective best efforts to prevent this. Can you better prepare your DevOps team to handle this?
If your organization delivers omni-channel digital services to your customers, then you almost certainly have a CICD pipeline that includes test automation as part of your development and delivery process. However, do you have the same automation benefits for functional, integration and system testing, or as part of your user acceptance testing process? If you currently rely on a QA or testing team to perform the final leg of your testing before promoting a release to production, using manual or partly automated testing approaches that rely on mobile handsets or emulators, then this is where Inquest is able to offer you unprecedented capabilities around automating this final leg of your testing and QA pipeline – right at the point of delivery and beyond. Inquest goes further and offers Testing In Production (TIP), ideally tailored to Fintech and Telco applications.
We find that even in the most mature, modern Fintech and Telco environments today that this final step in the QA process consists of one or more of the following:
- A very time consuming manual process, which relies on processing extensive test suites as part of functional testing, system testing, integration testing. This leads to long periods of downtime while everyone waits for the test team to give the green light for promoting a release to production;
- Where it is automated, this automation has to be performed by skilled engineers, since the automation tools rely on scripting or application development processes to conduct such A/B testing or Testing in Production (TIP) after code releases. This means that testing is expensive and difficult to maintain;
- Testing is not conducted end-to-end, since the tools do not allow for it – it almost always relies on APIs or simulated processes. This results in inadequate or compromised testing outcomes.
Inquest provides testing using drag and drop user interfaces to build an easily maintainable test suite in a zero code environment, and it executes these tests end to end, using the same endpoints as end users of the service. To summarise therefore, Inquest is not just a regular testing tool, but instead serves as a part of the QA Team with its own persona, account number and live interactions with the system.
- It offers the ability to have any desired number of robots or virtual users, that execute live tests on the production, development, UAT and QA environments, simultaneously.
- These tests can be strung together as a Test Chain, or be as complex as needed by creating Test Suites that have a hybrid of all test types. Tests can be run on demand or on a schedule.
- Inquest offers a zero code implementation which means that the QA or end user harnesses the power of Inquest by point and click or drag and drop.
- Inquest is driven by an intuitive user interface with real-time dashboards, beautiful reports and baked in Business Intelligence.
WHY INQUEST IS DIFFERENT
Inquest is different from your regular test automation tools. It serves as a virtual member of the QA Team with its own persona, account number and live interactions with the system.
- Can your current test automation solution execute live Testing In Production?
Inquest’s automated testing can run against many environments concurrently, and doesn’t require any special integration since it utilises the same endpoints as real users.
- Does your test automation require development and maintenance by QA personnel with software development expertise?
Inquest uses a simple point and click, drag and drop user interface to construct test plans, schedule test runs, draw reports and so on, allowing for a flexible, full featured zero code testing platform.
- Is your current automated testing conducted end to end, including the carrier network and end user devices?
Because Inquest drives endpoint devices and interfaces, it allows for true end-to-end testing, which is not possible with traditional test automation tools, since those tools have to integrate with APIs and back end infrastructure or code, and rely on development driven testing approaches.