InstantQA was created to remove the friction from test automation. No recorder. No manual scripting. No coding grind. Just upload test cases, generate executable Playwright scripts, and move from intent to automation faster than legacy tools ever allowed. With the release of InstantQA 1.1.0, the platform takes another major step forward. This release adds scheduled …
InstantQA was created to remove the friction from test automation. No recorder. No manual scripting. No coding grind. Just upload test cases, generate executable Playwright scripts, and move from intent to automation faster than legacy tools ever allowed.
With the release of InstantQA 1.1.0, the platform takes another major step forward. This release adds scheduled scenario execution, TestRail integration, SSO authentication, white label branding, AIQ integration, process history, translation history, sensitive data masking, and several important usability improvements.
But this is not just a list of new features. Every capability in InstantQA 1.1.0 is attached to a clear benefit: less manual effort, better enterprise control, faster adoption, stronger security, and more reliable automation at scale.
Scheduled Scenario Execution Means Testing Runs Even When Your Team Is Not Watching
InstantQA now supports scheduled automated scenario runs on a recurring basis.
The benefit is simple: QA no longer has to remember to start the next regression run. Teams can schedule scenarios to run every night, every weekend, before a release review, or on any recurring cadence that fits the delivery cycle.
This turns InstantQA from a script generation platform into a more continuous quality engine. Bugs can surface earlier. Releases can move faster. QA teams can spend less time managing execution and more time reviewing outcomes.
TestRail Integration Means Existing Test Cases Become Automation Fuel
InstantQA 1.1.0 introduces TestRail integration, allowing teams to import test cases from an external Test Management System.
The benefit is enormous for enterprise QA teams. Most large organizations already have thousands of manual test cases stored in systems like TestRail. Until now, those test cases were often trapped as documentation or manual work instructions.
With InstantQA, those existing assets can become the starting point for executable automation. That means less rework, faster onboarding, and a much cleaner path from manual test management to automated validation.
SSO Authentication Means Enterprise Teams Can Adopt InstantQA Securely
InstantQA now supports external Single Sign On through a credentials token exchange flow.
The benefit is enterprise readiness. Larger organizations do not want another standalone login system, another password process, or another user access island. SSO allows InstantQA to fit into existing identity and access management policies.
For IT and security teams, that means better governance. For users, it means easier access. For QA leadership, it removes one more barrier to enterprise rollout.
White Label Branding Means InstantQA Can Match the Customer Experience
InstantQA 1.1.0 adds support for white label branding for enterprise customers.
The benefit is brand continuity and enterprise flexibility. Large customers, partners, and service providers can deliver a fully branded experience to their internal users or external clients.
That matters because adoption improves when tools feel native to the organization. White label branding makes InstantQA easier to embed into enterprise programs, QA centers of excellence, managed testing services, and customer facing quality initiatives.
AIQ Integration Means InstantQA Can Connect to the Larger Appvance Quality Ecosystem
InstantQA 1.1.0 adds AIQ integration.
The benefit is a broader path from instant script generation to enterprise scale AI led testing. InstantQA gives teams a fast way to convert test cases into executable automation. AIQ extends that value into the larger Appvance platform, including deeper automation management, advanced execution, AI driven coverage expansion, and enterprise quality workflows.
This connection is important because many teams start with a focused need: convert test cases into scripts quickly. As they mature, they need broader orchestration, deeper analytics, and more advanced AI testing capabilities. InstantQA now creates a smoother bridge into that future.
Process History Means Teams Can See Everything That Has Been Generated
In InstantQA 1.0.0, the generation section focused on a single active process. In 1.1.0, users now get a full process history experience. They can browse, search, and navigate past and present generation processes by project.
The benefit is visibility. QA teams need to know what was generated, when it was generated, which project it belonged to, and how to get back to it. Process history makes InstantQA easier to manage across larger teams and larger test portfolios.
This is especially useful when teams are processing hundreds or thousands of test cases. Instead of losing context after each run, teams now have a searchable operational history.
Translation History Means Every Test Case Has Better Traceability
Within each generation process, the test case view now displays translation level history per test case.
The benefit is traceability. When a natural language test case becomes an executable automation script, teams need confidence in how that translation occurred. They may want to review changes, compare outcomes, or understand what happened across retries or restarts.
Translation history gives QA teams a clearer audit trail. That makes automation more transparent, easier to govern, and easier to trust.
Sensitive Data Masking Means Test Data Is Safer on Screen
InstantQA now includes sensitive data masking in test case input columns. Password like values are automatically masked. For example, a value such as password equals secret becomes password equals hidden characters. Users can toggle visibility per cell when needed.
The benefit is safer collaboration. Test cases often include credentials, tokens, personal data, or sensitive values. Masking reduces the chance that private data is exposed during demos, screenshots, reviews, support calls, or shared team sessions.
This is a small feature with a large enterprise security benefit.
Real Time Translation Status Means Users Know What Is Happening Now
InstantQA 1.1.0 improves translation process status updates, including status visibility after restarts.
The benefit is confidence. Users do not want to wonder whether a process is running, stalled, restarted, completed, or failed. Real time status reduces confusion and improves operational flow.
For high volume generation, this matters. Teams need clear signals so they know when to wait, when to review, and when to take action.
Duration Sorting Means Slow Scenarios Are Easier to Find
Scenario execution lists can now be sorted by duration.
The benefit is faster performance insight. QA teams can immediately identify the scenarios that take the longest to execute. Long running tests can then be optimized, separated, prioritized, or reviewed for efficiency.
In automated regression, speed matters. Duration sorting gives teams a practical way to reduce bottlenecks and improve execution planning.
Updated Timestamp Logic Means Scenario Lists Reflect Real Test Activity
The Updated column on scenario lists now reflects the latest run date rather than only the entity update date.
The benefit is better operational accuracy. QA teams care about when a scenario was actually executed. By showing the latest run date, InstantQA gives users a more useful view of test freshness and recent activity.
This helps teams understand which tests have been recently validated and which may need attention.
Case Insensitive Search Means Users Find Scenarios Faster
Scenario search by name is now case insensitive.
The benefit is simple but meaningful usability. Users should not have to remember exact capitalization to find a scenario. Search should work the way people expect.
This improvement reduces small moments of friction that add up across busy QA teams.
Project Owner Schedule Isolation Means Better Governance
Schedule visibility is now scoped to project ownership.
The benefit is cleaner access control. In enterprise environments, not every user should see every schedule across every project. Project owner isolation helps keep schedules aligned to the right teams, owners, and responsibilities.
This improves governance and reduces clutter.
Cascade Delete Means Project Cleanup Is Cleaner
Deleting a project now also deletes its associated schedules.
The benefit is cleaner administration. When a project is removed, its leftover schedules should not remain behind as orphaned automation jobs. Cascade delete keeps the environment cleaner and reduces accidental future execution.
For admins, this means less manual cleanup and fewer surprises.
Move Generated Scripts Means Teams Can Organize Automation More Easily
InstantQA 1.1.0 adds a new API endpoint that allows generated scripts to be moved between projects.
The benefit is flexibility. Teams often reorganize projects, split workstreams, consolidate automation, or move scripts from evaluation environments into production projects. This new API makes that easier.
As InstantQA adoption grows, script organization becomes more important. Moving generated scripts helps teams manage automation as a real enterprise asset.
InstantQA 1.1.0 Is About More Than Features
The real story of InstantQA 1.1.0 is not that the product added more buttons, screens, and integrations. The real story is that InstantQA is becoming more operational, more secure, more enterprise ready, and more connected to how QA teams actually work.
Scheduled execution means testing can happen automatically.
TestRail integration means existing test cases can become automated scripts.
SSO means security teams can say yes faster.
White label branding means enterprise programs can make the experience their own.
AIQ integration means InstantQA can grow into the larger Appvance quality ecosystem.
Process history and translation history mean teams gain visibility and trust.
Sensitive data masking means safer collaboration.
Scenario and project improvements mean the platform is easier to manage every day.
InstantQA began with a simple but powerful idea: turn English test cases into executable automation without recorders, coding, or manual scripting. Version 1.1.0 builds on that promise by making InstantQA more usable, more scalable, and more ready for serious enterprise adoption.
This is what modern QA needs. Not more manual effort. Not more fragile scripts. Not more AI theater.
Real automation. Real execution. Real productivity.
That is InstantQA 1.1.0.
