Zappos Case Study: Agile Test Automation for Increased Revenue

Introducing Tricentis Copilot: AI assistants for test automation at scale. Join us for a first look at Testim Copilot, the first of three Copilot solutions designed to boost your testing productivity and speed.

Learn more

Solutions

Featured webinar

How Wolters Kluwer built a foundation for standardized quality on a global scale

Hear how VP of QE at Wolters Kluwer created a Quality Engineering Center of Excellence, resulting in significant quality improvements, as well as time and cost savings.

Learn more

Services & Support

Resources

Contact

Company

Management team Careers News Locations Partners

Blog

Customer Portal

Trials & demos

Zappos

Company overview

Zappos.com’s purpose is simple: to live and deliver WOW.

Twenty years ago, they began as a small online retailer that only sold shoes. Today, they still sell shoes — as well as clothing, handbags, accessories, and more. That “more” is providing the very best customer service, customer experience, and company culture. They aim to inspire the world by showing it’s possible to simultaneously deliver happiness to customers, employees, vendors, shareholders, and the community in a long-term, sustainable way.

Zppos.com hopes that in the future people won’t even realize they started selling shoes online. Instead, they’ll know Zappos as a service company that just happens to sell ________.

Industry: Retail
Organization size: 1,001-5,000 employees
Location: United States
Products:
- Tricentis qTest

A better way

Since they practice agile development, there’s extra pressure on the QA team to effectively test crucial parts of the application. The Zappos testing team manually tracked QA for years. “It was a real challenge trying to manage so many test cases using a spreadsheet,” said Jesse Reynosa, Senior Quality Engineer. “It just wasn’t working.”

“I evaluated every test case management software available on the market,” says Reynosa. “I needed a tool that was easy to use because I didn’t want the team wasting time reading extensive user guides. If it was too complicated, I knew they wouldn’t use it.”

Easy implementation & integration

After an extensive evaluation, Jesse showed his team all the tools and qTest, which runs on AWS, was the clear winner. “A lot of the other tools were either too simple or too clunky,” said Reynosa. “qTest gave us all the key features we wanted and was easy to use.” Plus, we just imported our spreadsheets into qTest and we were good to go.

“We evaluated a lot of other testing platforms out there and found qTest to be the best and by far the most intuitive… we’ve improved efficiency by at least 50% since implementing qTest.”

Jesse Reynosa, Senior Quality Enginer

Test case quality boost

Reynosa likes the workflow in qTest: “It’s not complicated to go from point A to point B. You write your test cases and go right to execution.” He also relies heavily on qTest reporting. “Once a week we run integration tests,” he notes. “The reports help us understand if the health of the website is getting better or worse over time.”

Since implementing qTest, Reynosa has seen significant improvement in collaboration and test case quality. “We can look at each other’s test cases and see what makes sense and what doesn’t,” he said. “Plus, test runs are much easier than before. We’ve improved efficiency by at least 50% since implementing qTest.”

Why They Love It

Reporting capabilities
Easy workflow
Test case quality improvement
Increased automation
Easy team collaboration

How They Use It

To work more quickly and collaboratively
To maintain high quality in an agile environment
To use test cases more effectively
To continuously deploy