# Environments for API-created tests, tested nodes on the coverage map, and contract-aware billing > 4 updates: Set the environment when creating test cases through the API, Billing page follows your contract, Coverage map shows what's tested, Jump to… Source: https://qa.tech/changelog/2026-10-07 --- 4 updates shipped on October 7, 2026. In this release 1. 01[Set the environment when creating test cases through the API](#2026-10-07-set-environment-when-creating-tests-via-api)Highlight 2. 02[Billing page follows your contract](#2026-10-07-billing-page-follows-your-contract) 3. 03[Coverage map shows what's tested](#2026-10-07-coverage-map-shows-whats-tested) 4. 04[Jump to the latest run from Automations](#2026-10-07-jump-to-the-latest-run-from-automations) 1. Highlight Featured this release ## Set the environment when creating test cases through the API POST /v1/test-cases and the MCP create\_test\_case tool take an optional environment for the first run. Pass `environment` – for example `{ "url": "https://my-preview.example.com" }` – and the first run of a new test targets that preview or tunnel URL instead of the default environment. It applies to the first run only and isn't stored on the test case. URLs must be http(s). Useful for coding agents that write a test and want it checked against their own branch – see [agentic testing](https://qa.tech/). More on this: [MCP and coding agents](https://qa.tech/product/mcp), [API testing](https://qa.tech/product/api-testing) and [testing AI-generated code](https://qa.tech/use-cases/ai-generated-code-testing). [\# Direct link](#2026-10-07-set-environment-when-creating-tests-via-api) 2. Update 02 of 04 ## Billing page follows your contract Invoices and Commits & Credits appear for every member of an organization with a contract. Under Settings → Billing, the Invoices and Commits & Credits tabs show whenever your organization has a contract, including ended ones. Budget & Spending Alerts and Spend Limits are editable for owners and admins when they apply, and usage rows use readable labels like "Chromium" and "Mobile Builds". More on this: [pricing](https://qa.tech/pricing) and [CTOs](https://qa.tech/solutions/ctos). [\# Direct link](#2026-10-07-billing-page-follows-your-contract) 3. Update 03 of 04 ## Coverage map shows what's tested Tested actions and pages light up on the Coverage map. Actions touched by a test, and pages with at least half their actions covered, are filled near-white, while untested nodes keep their application color. A "Tested" legend sits bottom-left, the info panel gets a "Tested" row, and side-panel thumbnails center on the action. More on this: [automated regression testing](https://qa.tech/use-cases/automated-regression-testing), [CTOs](https://qa.tech/solutions/ctos) and [why 100% coverage isn't the goal](https://qa.tech/blog/why-100-test-coverage-isnt-the-goal). [\# Direct link](#2026-10-07-coverage-map-shows-whats-tested) 4. Update 04 of 04 ## Jump to the latest run from Automations The Last Run date on the Automations page links straight to the latest run. Chat automations open the conversation and test-plan automations open the run result. The date stays plain text until a run has been recorded. More on this: [smoke testing](https://qa.tech/use-cases/smoke-testing) and [automated regression testing](https://qa.tech/use-cases/automated-regression-testing). [\# Direct link](#2026-10-07-jump-to-the-latest-run-from-automations) ## Your team moves fast. Can your testing keep up? QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo. [Get a demo](https://qa.tech/demo) [QA.tech](https://qa.tech/)[SOC 2 Type 2 compliant![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png)](https://trust.qa.tech/) ### Product - [API Testing](https://qa.tech/product/api-testing) - [MCP](https://qa.tech/product/mcp) - [Mobile Testing](https://qa.tech/product/mobile-testing) - [PR Testing](https://qa.tech/product/pr-testing) - [Voice Testing](https://qa.tech/product/voice-testing) - [Web Testing](https://qa.tech/product/web-testing) - [AI QA testing guide](https://qa.tech/ai-qa-testing) - [Changelog](https://qa.tech/changelog) - [Integrations](https://qa.tech/product/integrations) - [Platform overview](https://qa.tech/product) - [Use cases](https://qa.tech/use-cases) ### Compare - [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress) - [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl) - [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright) - [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf) - [B2B SaaS testing](https://qa.tech/saas) - [Ecommerce testing](https://qa.tech/industries/ecommerce) - [For CTOs](https://qa.tech/solutions/ctos) - [For QA teams](https://qa.tech/solutions/qa-testers) ### Resources - [Docs](https://docs.qa.tech/) - [Blog](https://qa.tech/blog) - [Events](https://qa.tech/events) - [Pricing](https://qa.tech/pricing) - [Case Studies](https://qa.tech/case-studies) ### Company - [About](https://qa.tech/about-us) - [Partnerships](https://qa.tech/partnerships) - [Press](https://qa.tech/press) - [Contact Us](https://qa.tech/contact) - [Privacy Policy](https://qa.tech/privacy-policy) - [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf) - [Trust Center: Security & Compliance](https://trust.qa.tech/) ### Social - [](https://www.linkedin.com/company/qa-tech-ai/) - [](https://x.com/getqatech) - [](https://www.instagram.com/getqatech/) © 2026 QA.tech. All rights reserved