# Self-improving PR reviews, GitLab CI attribution, and plan defaults in chat > 4 updates: GitLab CI run attribution, PR reviews learn from your feedback, Full run results on the PR review page, Pin test plan defaults from chat Source: https://qa.tech/changelog/2026-09-01 --- 4 updates shipped on September 1, 2026. In this release 1. 01[GitLab CI run attribution](#2026-09-01-gitlab-ci-run-attribution)Highlight 2. 02[PR reviews learn from your feedback](#2026-09-01-pr-reviews-learn-from-your-feedback)Highlight 3. 03[Full run results on the PR review page](#2026-09-01-full-run-results-on-the-pr-review-page) 4. 04[Pin test plan defaults from chat](#2026-09-01-pin-test-plan-defaults-from-chat) 1. Highlight Featured this release ## GitLab CI run attribution Runs triggered from GitLab CI show GitLab icon with linked branch and commit, self-hosted included. Runs triggered through the public [API](https://docs.qa.tech/api-reference/introduction) from GitLab CI are now recognised as first-class GitLab runs, with branch and commit links back to GitLab, support for self-hosted GitLab instances, and GitLab as a filter option alongside your other trigger sources. More on this: the [GitLab integration](https://qa.tech/product/integrations/gitlab) and [PR and CI/CD testing](https://qa.tech/use-cases/pr-cicd-testing). [\# Direct link](#2026-09-01-gitlab-ci-run-attribution) 2. Highlight Featured this release ## PR reviews learn from your feedback A thumbs-down with a written reason now shapes the next review on that project. When you rate a [PR review](https://qa.tech/product/pr-testing) down and explain why, QA.tech turns that into a lasting improvement for future reviews on the same project – either a standing rule the next review is briefed on, or a memory it recalls when relevant. Outdated rules get narrowed or retired as your app changes, so the reviewer stops flagging things that no longer apply. More on this: [pull request testing](https://qa.tech/product/pr-testing) and [why developers should not test their own code](https://qa.tech/blog/why-developers-shouldnt-test-their-own-code). [\# Direct link](#2026-09-01-pr-reviews-learn-from-your-feedback) 3. Update 03 of 04 ## Full run results on the PR review page PR reviews now show the same List and Dependencies views as the results page. Each PR review card renders the full run results view for that round – switch between List and Dependencies to see how the tests relate, then follow "View Full Run" to open the complete run on the results page. More on this: [pull request testing](https://qa.tech/product/pr-testing) and [PR and CI/CD testing](https://qa.tech/use-cases/pr-cicd-testing). [\# Direct link](#2026-09-01-full-run-results-on-the-pr-review-page) 4. Update 04 of 04 ## Pin test plan defaults from chat Set a test plan environment, device and agent in chat and it sticks for every future run. Chat could already create and edit [test plans](https://docs.qa.tech/core-concepts/test-plans); the default environment, device preset and agent lived only in plan Settings. Now you can pin all three directly in chat when creating or editing a plan, and ask for a plan's current defaults without leaving the conversation. Scheduled and manual runs use whatever you set. More on this: [multi-environment testing](https://qa.tech/use-cases/multi-environment-testing) and [smoke testing](https://qa.tech/use-cases/smoke-testing). [\# Direct link](#2026-09-01-pin-test-plan-defaults-from-chat) ## 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) ### 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) - [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