Marvell Technology Group Ltd. provides data infrastructure technology that keeps the world running. They move, store, process, and secure the world’s data with semiconductor solutions designed for their customers’ current needs and future ambitions. Everything they do revolves around 4 key principles: reliable results, superior performance, nimble dexterity, and rigorous execution.
Releasing exceptional-quality software faster is a key part of advancing these goals. That’s why Marvell made testing transformation a key element of their recently-launched DevOps initiative. Specifically, they recognized that maximizing the benefits of DevOps would require an enterprise-grade test management solution with asset sharing, approval processes, integration into the DevOps pipeline, and real-time reporting on test results and quality trends. Their existing process of using Excel files to plan tests and track test results, manually coordinating test execution, then manually compiling reports upon stakeholder request was not fast, efficient, or scalable enough for their new DevOps process.
After exploring several solutions, Marvell’s SSD Firmware team selected Tricentis qTest. Instead of adding tests to individual Excel files on individual testers’ systems, all tests are created and visible within a central repository and correlated to requirements in Jira, their requirements management system. This enables team members to see if any reusable assets already exist before creating new assets from scratch. Approvals can be tracked and reviewed at a glance. qTest-Jenkins integration enables automated test execution within the DevOps pipeline, with results reported back to qTest and Jira. Test results and Marvell’s key quality metrics (e.g., failure rate from version to version) are visualized in custom dashboards, giving stakeholders instant insight into test status and release readiness.
Marvell’s qTest adoption rapidly expanded across additional business units after seeing how the solution increased the efficiency of test planning and sharing, standardized test execution in the DevOps pipeline, and simplified reporting.