Dentsu Creative cuts defect escape rate by 90% with BrowserStack Test Management

Dentsu Creative is a global integrated creative and digital agency. Its Experience practice in Australia designs, develops and optimises customer experiences through website development, apps, and other digital products. With a fast-moving project environment, multiple client accounts running simultaneously, and quality assurance sitting at the centre of every delivery, the need for a scalable, centralised, and transparent test management platform became impossible to ignore.

Nandini Savithri, Principal Quality Engineer, and Makarand Khamkar, Senior QA Professional, have been BrowserStack customers for six years, expanding from cross-browser testing into App Automate, Live, and most recently Test Management. By adopting BrowserStack Test Management and its AI-powered agents, Dentsu Creative cut defect escape rates by 90%, reduced test case creation time by 80%, achieved 4x more test cases, and delivered a seamless production deployment with zero critical defects on their most recent project.

Before adopting BrowserStack Test Management, Dentsu Creative’s QA process relied on a fragmented mix of tools including Spreadsheets, JIRA, Zephyr, and XRay, depending on the project. None of these gave the team a single, unified view of test activities, and the gaps in coverage and visibility had a direct impact on release quality and delivery timelines.

1. Test cases scattered across disconnected tools: With different projects using different tools, there was no single place to manage test planning, creation, execution, and defect management together. The lack of centralisation meant effort was duplicated, consistency was hard to maintain, and nothing gave a true picture of where quality stood at any given moment.

2. No transparency for non-technical stakeholders: Dashboards and progress summaries required manual effort to produce. Clients and project managers had no real-time visibility into test progress, execution status, or overall coverage, meaning every update required someone from the QA team to stop and report it.

3. Poor test coverage leaving gaps across the product: Because test case creation was slow and the tooling was fragmented, coverage was limited. Medium-priority scenarios and edge cases were not being tested, leaving meaningful quality gaps that increased the risk of defects going undetected.

4. Defects slipping quietly into production: The combination of low coverage and slow processes meant defects were making it through to production. Fixing and retesting production defects added significant unplanned effort to every cycle, and two-week sprints frequently stretched to three weeks as a result.

5. Editing test cases was tedious and time-consuming: In fast-moving digital projects, requirements change constantly. Updating test cases to reflect requirement changes in spreadsheets or Jira was a manual, time-consuming process that slowed the team’s ability to keep pace with development.

After evaluating alternatives including Zephyr and Xray, Nandini selected BrowserStack Test Management as the platform that ticked every requirement: AI capability, end-to-end test activity management, transparent reporting, and seamless integration with Jira. The team started a new project from scratch on the platform and saw the impact from day one.

1. Test Case Generator Agent for faster, broader coverage: Rather than writing test cases manually from scratch, the team used the Test Case Generator Agent to generate structured test cases quickly and at scale. The agent surfaced edge case scenarios that even experienced QA professionals had not identified, ensuring coverage went further than it ever had with manual authoring alone. The result was 4x more test cases created and an 80% reduction in the time spent on test case creation.

2. Test Deduplication Agent for a clean, efficient suite: As coverage grew, the Deduplication Agent automatically identified and flagged duplicate test cases, keeping the test suite clean and preventing redundant execution effort from accumulating over time.

3. Low Code Authoring Agent for automated test execution: The Low Code Authoring Agent allowed the team to automate test scripts directly within the platform without building a complex automation framework from scratch. Automated tests could then be run on a daily basis, increasing both the frequency and reliability of test execution.

4. Jira integration for full traceability: BrowserStack Test Management integrated seamlessly with Jira, which Dentsu Creative uses across the majority of its projects. Once set up, all test cases and defects raised were visible directly under the relevant user story in Jira, giving clients and project managers a real-time view of exactly what was being tested, what had been raised, and where things stood, without needing to ask the QA team for an update.

5. A unified platform replacing fragmented tooling: For the first time, the entire test lifecycle, including test planning, test case creation, execution, defect management, and reporting, lived in one place. The platform’s modern, user-friendly interface meant non-technical stakeholders could navigate it without support, and the centralised dashboard gave everyone visibility into test progress and coverage at any time.

6. BrowserStack was chosen over its competitors for its AI depth and end-to-end capability: During evaluation, BrowserStack Test Management consistently ticked more boxes than competing tools, particularly on AI capability, reporting, and the ability to handle all test activities within a single platform. The existing BrowserStack relationship of six years also meant there was no new vendor to onboard.

The impact of BrowserStack Test Management was felt across every stage of the testing lifecycle, from how quickly test cases could be created to how confidently the team could sign off on a production release.

1. 4x more test cases created: The combination of AI-assisted generation and a faster, more intuitive platform meant the team could create significantly more test cases than before, broadening coverage across both high-priority and edge case scenarios that were previously untested.

2. 80% reduction in test case creation time: What previously required significant manual effort across disconnected tools was dramatically compressed, freeing QA engineers to focus on execution, exploration, and defect resolution rather than authoring.

3. 90% reduction in Defect Escape rate: With broader test coverage, AI-surfaced edge cases, and automated daily execution, the rate at which defects reached production fell by 90%. Developers received more defects earlier in the cycle, driving the team toward a test-driven development approach where issues were fixed before they could escape.

4. 100% traceability of test cases to requirements and defects to test cases: For the first time, Dentsu Creative had complete, auditable linkage across the entire test chain. Every test case was linked to its requirement, and every defect was linked to its test case, giving clients and project managers a clear line of sight from requirement to release quality.

5. Seamless production deployment with zero critical defects: On the first major project using BrowserStack Test Management, the team achieved a seamless production deployment with no critical defects, a result that was cited as a significant win and a direct outcome of the improvement in coverage and traceability.

6. Full visibility for clients and non-technical stakeholders: Clients and project managers could track test progress, view execution status, and review coverage at any time through the dashboard, without requesting a manual update from the QA team. This transparency was specifically highlighted as a standout outcome by both technical and non-technical team members.

7. 500 plus test cases managed seamlessly on an ongoing basis: The team created more than 500 test cases on their most recent project and continues to run them on an everyday basis with minimal defects, demonstrating the platform’s ability to scale with the team’s needs.

8. Easier test case editing as requirements change: With requirements changing constantly in digital project environments, the ability to edit and update test cases quickly within a single platform removed one of the most persistent frustrations of the previous approach, keeping the test suite current without significant manual overhead.