# Logic verification, test suite maps, and GitLab code access > 6 updates: Logic verification for rule-heavy code (beta), Repository mapping imports recent PRs and maps your test suite, Clearer PR review comments and… Source: https://qa.tech/changelog/2026-10-24 --- 6 updates shipped on October 24, 2026. In this release 1. 01[Logic verification for rule-heavy code (beta)](#2026-10-24-logic-verification-beta)Highlight 2. 02[Repository mapping imports recent PRs and maps your test suite](#2026-10-24-repository-mapping-imports-prs-and-maps-tests)Highlight 3. 03[Clearer PR review comments and a retrospectives tab](#2026-10-24-clearer-pr-review-comments-and-retro-tab) 4. 04[GitLab code access and the post-merge agent on Azure DevOps](#2026-10-24-gitlab-code-access-and-azure-devops-post-merge) 5. 05[Cancel the Start-up plan and edit billing details in-app](#2026-10-24-manage-billing-in-app) 6. 06[Set up your project knowledge from chat with /knowledge](#2026-10-24-set-up-project-knowledge-with-knowledge) 1. Highlight Featured this release ## Logic verification for rule-heavy code (beta) QA.tech can find concrete inputs that break your business rules, such as dates, money, permissions, limits and status transitions. In chat, ask it to verify logic in any project with code access. For PR reviews, enable Logic Verification (beta) under Code Access in the GitHub or Azure DevOps repository settings. Findings with a reachable screen become targeted tests; backend-only findings appear in the review as issues found in code, not confirmed in the app. More on this: [PR testing](https://qa.tech/product/pr-testing), [roles and permissions testing](https://qa.tech/use-cases/roles-permissions-testing) and [testing AI-generated code](https://qa.tech/use-cases/ai-generated-code-testing). [\# Direct link](#2026-10-24-logic-verification-beta) 2. Highlight Featured this release ## Repository mapping imports recent PRs and maps your test suite Connecting a repository pulls in its 30 most recent pull requests and builds a map of your existing tests. Mapping a GitHub, GitLab or Azure DevOps repository imports its 30 most recent pull requests, so a fresh project starts with history. With code access on, QA.tech also reads your unit, integration and e2e tests and saves a Test suite map to your project library: which layers exist, reusable test data, flows already covered, gaps ranked by risk and specs worth porting. The scan is read-only and never runs your tests. More on this: [integrations](https://qa.tech/product/integrations) and [end-to-end testing](https://qa.tech/use-cases/end-to-end-testing). [\# Direct link](#2026-10-24-repository-mapping-imports-prs-and-maps-tests) 3. Update 03 of 06 ## Clearer PR review comments and a retrospectives tab Review comments open with a Verified, Bugs found or Couldn't verify pill, and retrospectives get their own chat tab. The progress checklist shows a check, spinner or grey circle per step. Recorded PR retrospectives open in a canvas tab with the verdict, what went well and wrong, and follow-up todos. Review tabs show which commit was reviewed and link to newer reviews. More on this: [PR testing](https://qa.tech/product/pr-testing) and [shift-left testing](https://qa.tech/use-cases/shift-left-testing). [\# Direct link](#2026-10-24-clearer-pr-review-comments-and-retro-tab) 4. Update 04 of 06 ## GitLab code access and the post-merge agent on Azure DevOps GitLab projects can give QA.tech read access to code, and Azure DevOps gets the post-merge agent. GitLab repository mappings support Code Access, and each repository has its own settings with applications, a review trigger, environment mapping and review instructions, plus a ready-made `.gitlab-ci.yml` snippet. On Azure DevOps, turn on the Post-Merge Agent in the repository settings, review screenshots show inline, and a follow-up `@qa.tech` mention continues the existing review thread. More on this: [integrations](https://qa.tech/product/integrations), [PR and CI/CD testing](https://qa.tech/use-cases/pr-cicd-testing) and [GitLab CI/CD guide](https://qa.tech/blog/automating-qa-with-ai-in-gitlab-ci-cd-a-step-by-step-guide). [\# Direct link](#2026-10-24-gitlab-code-access-and-azure-devops-post-merge) 5. Update 05 of 06 ## Cancel the Start-up plan and edit billing details in-app Billing admins can cancel the Start-up plan and manage invoicing details without leaving QA.tech. Click Cancel Plan on the Start-up card, pick a reason, and the plan stays active until the end of the paid period with a Cancels on note. The new Billing Details tab covers company name, billing email, up to 5 CC recipients, address, tax IDs, PO number and invoice memo. Members without billing permission see it read-only. ![A cancelled Start-up plan showing the date access ends](https://qa.tech/changelog-assets/2026-10-24-cancel-start-up-plan.webp) More on this: [pricing](https://qa.tech/pricing) and [account settings testing](https://qa.tech/use-cases/account-settings-testing). [\# Direct link](#2026-10-24-manage-billing-in-app) 6. Update 06 of 06 ## Set up your project knowledge from chat with /knowledge A guided skill walks you through your knowledge library, memories and agent rules without leaving the chat. Type `/knowledge` in the chat input, or pick the new card on the empty chat screen, and the assistant helps you set up and clean up library items, memories, agent rules and custom skills. It is listed with the other built-in skills under Settings → Knowledge → Assistant. More on this: [product](https://qa.tech/product) and [AI test generation](https://qa.tech/use-cases/ai-test-generation). [\# Direct link](#2026-10-24-set-up-project-knowledge-with-knowledge) ## 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. [Book 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) - [Partner Program](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