The Feature Shipped. The UI Automation Didn’t.
How I’m using Jira, Figma, GitLab, and Playwright MCPs to make automation part of delivery—not the task that comes after it. “Can we finish testing this before the release?” “Yes.” “And automate it?” “We’ll pick that up next sprint.” If you work in quality engineering, that conversation probably sounds familiar. It’s not that nobody cares about automation. It’s that delivery has a deadline, while…
Many quality engineers face a common dilemma: delivering a feature before the deadline, while automation often lags behind due to the backlog of test cases and defects. The challenge lies in striking a balance between these two aspects of software development. To address this issue, one reporter utilized Jira, Figma, GitLab, and Playwright MCP integrations to streamline the automation process.
These tools enable the reporter to load manual test cases, review designs, reference implementation, and inspect the running application, all within a single workflow. By connecting these sources of context, the AI assistant becomes a valuable helper in assembling tests, allowing the quality engineer to focus on reviewing and executing the generated tests.
This approach minimizes the time spent on mechanical tasks such as finding stable locators and verifying assertions, ultimately enabling the automation of regression coverage more effectively.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
