Blog

Award-winning strategies for improving testing efficiency and collaboration

  • 3 August 2023
  • 0 replies
  • 30 views
Award-winning strategies for improving testing efficiency and collaboration
Userlevel 4
Badge +2

In response to an unprecedented year, we’ve seen companies place greater importance on optimization – within the functionality of their toolsets, testing automation frameworks, and process improvement across the enterprise.

So, when Tricentis sat down with Nordea, Dell, and Moët Hennessy Louis Vuitton (LVMH) late last year, it was no surprise to hear words like ‘collaboration,’ ‘efficiency,’ and ‘standardization’ being used repeatedly throughout our conversations.

If you’re also facing pressure to meet increased demand while maintaining exceptional quality, consider some of the following software testing approaches taken by three of our 2020 Customer Innovation Award Winners.

Luxury powerhouse LVMH seamlessly onboards new brands by testing less, but better

Home to the world’s most exclusive luxury brands, LVMH’s guiding principle is quality. With the rate of online purchasing at an all-time high, managing an increasing number of e-commerce rollouts at a faster pace, all the while continuing to deliver an exceptional customer experience, is no small task.

When we sat down with Johann Gaggero, Head of Omnichannel QA, one of the topics we were eager to discuss was how his team manages to drive go-to-market speed while keeping quality as a top priority.

In Gaggero’s words, “We test less, but we test better.” He went on to explain that in order to ensure the level of quality that LVMH customers expect and deserve, they had to optimize their rollout routine. With the help of Tricentis qTest, Gaggero’s team has done just that. “We have to ensure quality but optimize our rollout routine. That’s exactly what we did. If I want to launch a new project, 70% of my assets are already ready to go.” When it comes time to add a new e-commerce website, instead of starting from scratch each time, Gaggero’s team simply references existing test cases within their standard library and builds on top of them.

“One year ago, I needed two to three people for a single rollout. Now I need only one.”

Dell ISG streamlines testing across 50 different product groups with extreme reuse

Managing a wide range of products, services, methodologies, and tools is a complex challenge. For a large, multi-national company such as Dell, collaboration becomes critical for success. Tasked with creating one centralized source of truth across many product groups all using their testing tools of choice, the Dell ISG team faced a challenge that is not unique to the technology space.

During our interview with Adam Arakelian, Director of Software Engineering at Dell ISG, we learned how he and his team were able to achieve this.

“I’m focusing on things like collaboration and mobility, as well as standardization of how we drive our software development processes to help really drive a ‘build once, reuse many’ culture… Our focus wasn’t on software development processes and methodologies as much as it was on terminology, alignment on philosophy, and understanding that software development is continuous—really adopting the notion of continuity through a process from a software development perspective.”

In order to apply the same “build once, reuse many” approach to testing, Adam knew that he needed a robust test case management tool. With Tricentis qTest, he continues, they “can focus on creating automation once, building test cases once, and reusing them across our Dell ISG organization.”

“We knew we had to transform and really focused in on some of our DevOps strategies.”

Nordea avoids reinventing the wheel with their test automation “toolbox”

With more than 30K employees and customers in over 20 countries, Nordea Bank is one of Europe’s top financial service providers. At this size, one of their main business drivers is to implement a standardized process across the enterprise. We had the opportunity to speak with Bernes Maksumic, Head of QA Engineering, to better understand why harmonization, specifically with a focus on toolset, was necessary to achieve this goal.

Maksumic indicates “…it’s quite important that we have a standardized process across the bank on how to test the software. Then our release trains and agile release trains can focus on providing the business value, and not focus on “what does the CI/CD and the testing process look like.”

When it came time to select a test case management tool, his philosophy was to “use few and reuse”—similar to the approaches of Dell ISG and LVMH. He adds, “We have a quite large landscape. What we are trying to do is have a predefined set of tools (and also processes), so we can give a toolbox to our projects and programs. When they get onboarded to our engineering system platform, they do not need to set up CI/CD on each and every initiative. It’s the same thing for our test automation framework.”

Maksumic’s decision to go with Tricentis qTest was not solely based on the testing tool’s capabilities compared to others on the market. He makes it clear that they were more focused on their desired outcome.

“Instead of rediscovering everything, we take the best practices that are already working and scale that up to many initiatives.”


0 replies

Be the first to reply!

Reply