Get a demo or trial

Company

Services & Support

Resources

Events

Contact us

NeoLoad introduces RTE support for simplified mainframe testing

How data integrity can help enterprise SAP teams be AI-ready

4 key quality metrics for executives – and how to track them in Tricentis SeaLights

The business value of SAP testing: Insights from IDC research

Quality is AI-driven

Accenture

Amazon Web Services (AWS)

Capgemini

Cognizant

DXC Technology

How a global leader in athletic apparel accelerates SAP S/4HANA migration with Tricentis Tosca’s end-to-end test automation

How North Carolina Department of Health &#038; Human Services transformed their test automation strategy with Tricentis Tosca

reduction in test duration for recent large release

custom Oracle extensions under test within end-to-end test suite

Almac automates end-to-end testing for critical Oracle business processes

DocMorris’ Quality Assurance contributes to the ‘health-in-one-click’ mission with ‘testing-in-one-click’

hours of data validation saved per release

total team adoption of Tricentis automation tooling

How Tricentis and Capgemini ensured a health insurance company’s data integrity with automated testing

Tricentis Unveils Enhanced Tosca for New Era in Cloud-Based Test Automation

Tricentis Launches qTest Copilot to Empower QA Organizations to Ship Quality Software Faster

Tricentis’ David Colwell talks new hurdles in AI development

Lessons from the CrowdStrike outage: A wake-up call for software testing

Maximizing AI investments: transforming DevOps teams in APAC

Senior Director Analyst

Unternehmen können es sich nicht mehr leisten, sagen wir mal die zehn wichtigsten Mobilgeräte zu kaufen. Wenn eine Mitarbeiterin oder ein Mitarbeiter früher um ein Gerät angefragt hat, konnte man sagen: Nun ja, in unserer Organisation sind nur zwei oder drei mobile Geräte zugelassen, bitte wähle. Bei einer Anwendung kannst man das jedoch vergessen – noch dazu, wenn es um eine geht, die der Öffentlichkeit zugänglich gemacht wird. Du weißt einfach nicht, was die Nutzer wirklich verwenden.

Gartner – Improve mobile engagement through testing – Resource (German)

Test Manager

“Having the ability to run our entire automated regression suite each time we introduce changes gives us assurance that we have maintained the integrity of our production systems.”

Stockland &#8211; Regression suite, integrity of production systems

Product Owner SDLC and ERP Toolchain

&#8220;We use a lot less time in both building and maintaining our test cases thanks to Tosca. People still have the choice to use an older automation solution that is still available, but a large majority of our stakeholders consistently ask for Tosca.”

Heineken &#8211; Tosca &#8211; ask for Tosca, test cases

Chapter Lead Technology Specialist QA

“Ease of use and the fact that Tosca is codeless are key aspects when offering a testing platform to product teams.”

Heineken quote &#8211; Tosca &#8211; Ease, codeless

保険会社

コンサルティングチームから1日にも満たないサポートを受けただけで、進行中のプロジェクトの重点分野に適合するロードマップを策定することができました。Tricentisの支援により、Toscaで自動化を行う前から、具体的な結成果を得ることができました。

Consulting EMEA &#8211; Roadmap Insurance JA

Testim Mobile: Faster and higher quality for all mobile apps

Simplify and scale test automation in the cloud with Tosca cloud deployment

Tricentis NeoLoad 2024.3: Elevating legacy performance testing with remote terminal emulation (RTE)

Introducing qTest Copilot: Your AI-powered test generation assistant

Unlocking RISE with SAP and Tricentis: Quality assurance in your cloud journey

An introduction to agile test management

Jira test case management: How and why?

React Native side menu step by step guide with examples

What is test case management: What it is and why it’s important

Cloud testing: A complete introduction

<h3>Follow the clues to reveal the path to maturity</h3>
It was Professor Plum in the Ballroom with the Candlestick!
Or was it the Tester in the Study with the Spreadsheet?
Sometimes the world of DevOps testing can resemble the mystery board game Clue – and there’s no scarier weapon against killing testing practices than the dreaded spreadsheet.
But when it comes to figuring out the mystery of modernizing testing for DevOps, many organizations don’t have, well, a clue about where to start. Wherever you are on your path to DevOps testing maturity, we’ll help you sleuth out where to start and how to follow the clues to the next steps.

The test management tool has gone missing from XYZ Corporation, and if the company doesn’t find it soon, it might have to delay the release of its new software.

Join us as we crack “The case of the missing DevOps testing strategy.”

default

<ul>
<li>You need a better way to manage and share test assets</li>
<li>It&#8217;s difficult to trace test coverage to requirements</li>
<li>Your team is doing some automated testing, and you need better visibility</li>
</ul>

Start with Clue #1 if:

<ul>
<li>You&#8217;re moving towards more frequent releases, adding more features, and anticipate more regular regression testing</li>
<li>You&#8217;re already releasing frequently and manual regression testing causes delays</li>
<li>Your regression test suite has grown too large and it&#8217;s challenging to achieve adequate risk coverage</li>
</ul>

Take the secret passage to Clue #2 if:

<ul>
<li>You need to get started with load and performance testing</li>
<li>You&#8217;re doing functional test automation but can&#8217;t reuse those assets for load testing</li>
<li>You need to scale performance testing but have scarce resources</li>
</ul>

Follow the footprints to Clue #3 if:

<a id="clues">Let’s get sleuthing for the secret to DevOps success</a>

Continue

Back to clues

Start with test management to build a foundation for success. 
The evidence:
<ul>
<li>The XYZ QA team’s fingerprints were found all over multiple spreadsheets.</li>
<li>An email from a company executive read:  “We really need to start managing our test cases in a central area. Why don’t we use Excel? After all, everyone has spreadsheets on their workstations, so we don’t have to buy and install the software.”</li>
</ul>
There has been some suspicious activity happening at XYZ Corporation and it appears they have been relying on spreadsheets for testing for far too long. Excel as a test case management tool seemed like such a good idea at first –but cut to six months and 60 spreadsheets later, and the testers at XYZ need to reuse something from that first spreadsheet. They don’t know where it is, and even if they can locate the spreadsheet, they can’t be sure the information is still up to date.

<a id="clue-1">Clue #1: If you’re trying to find where the test cases should dwell, here’s a hint – it’s not in Excel.</a>

Companies can lay the foundation for their success by starting with dedicated test management that doesn’t include spreadsheets. By establishing testing best practices that each testing team can adhere to, companies can create a scalable method that ensures they can:
&nbsp;
<ul>
<li>Centralize and organize testing</li>
<li>Share test assets and minimize rework</li>
<li>Integrate testing tools for a single-pane-of-glass view</li>
<li>Analyze the test case library and get rid of redundancy</li>
<li>Understand how much is automated today and where to go next</li>
</ul>

Laying the foundation for success

Excel may be great for the accounting team but it’s not so great for test management. For example, Excel won’t integrate with your issue tracker, which makes traceability and bug reporting unnecessarily tricky. Reporting becomes more and more challenging, leading to a breakdown in visibility and trust between QA and development.
&nbsp;
By making the switch from spreadsheets to a dedicated test management solution built for Agile and DevOps teams, you’ll be able to build a foundation for a more efficient, sustainable, and scalable testing practice. Begin by gathering internal support for your business case and examining your requirements by following these steps:
&nbsp;
<ol>
<li>Create a mission statement: The mission statement will underscore the purpose of moving away from spreadsheets and include the benefits and measurable outcomes. Use it to make a business case to gain internal approvals and funding for test management. In addition to leadership, get other stakeholders from development and product management on board by highlighting how improved visibility and collaboration will benefit everyone.</li>
<li>Build out technical requirements: Analyze what you need in a test management solution. Consider that the solution should have:
<ul>
<li>A seamless integration with your Agile planning tool (Jira, Rally, etc.)</li>
<li>A test case library that makes it easy to organize, share, and reuse test assets</li>
<li>CI/CD integration to help orchestrate test automation as part of the CI/CD process</li>
<li>Reporting and visibility across QA efforts, teams, and testing tools</li>
</ul>
</li>
<li>Build out business requirements: Once you have narrowed down potential test management solutions, it’s time to examine how they could help you with your success criteria. Ideally, you want a well-established provider who can give you implementation guidance and ongoing support.</li>
</ol>

Centralize and organize testing with streamlined test management

Tricentis <a href="https://be.tricentis.com/products/unified-test-management-qtest/">qTest</a> helps organizations standardize and scale testing best practices across projects, tools, and teams. The centralized test management solution offers a straightforward spreadsheet migration path and test automation management that sets teams up for scale.
&nbsp;
The testing team at online retailer <a href="/case-studies/zappos">Zappos</a> had been manually tracking QA for years. “It was a real challenge trying to manage so many test cases using a spreadsheet,” said Jesse Reynosa, Senior Quality Engineer. After extensively evaluating the test case management software available on the market, Zappos selected Tricentis qTest because it’s easy to use and the testing team could import its existing test case library, which was housed in spreadsheets, into qTest. Zappos has increased efficiency by at least 50% since implementing qTest.

Tricentis qTest for unified test management

Watch webinar

From spreadsheets to scalable, streamlined test management

Watch the webinar to learn more

It’s time to build a scalable test automation practice.  

The evidence:
<ul>
<li>An XYZ tester’s alibi was that he was home eating dinner, but his laptop login showed he was at work rushing to finish up testing to meet that two-week Agile sprint deadline.</li>
<li>Holding a magnifying glass to the testing team’s timesheets reveals that regression testing takes days to complete, and the testing timeline is way behind schedule.</li>
</ul>
XYZ Corporation had planned a two-week Agile sprint. Testing usually takes four days, but now XYZ’s iterations are being extended to three weeks or even longer. The likely culprit for the significant delay is&#8230;regression testing. Allocating adequate time for regression testing before a new release is critical for ensuring that changes won’t impact existing functionality. As applications mature, there’s more existing functionality to test. For many testing teams like XYZ, frequent releases and rapidly expanding feature-sets can exponentially increase regression suites. Before long, they reach a tipping point, at which it’s impossible to achieve adequate risk coverage and still complete testing on time (or get home in time for dinner!)

<a id="clue-2">Clue #2: If you’re wondering where to search next in your testing transformation quest, scaling regression testing might be best. </a>

Regression testing is essential to ensuring ongoing software quality, reducing the risk of defects, and providing meaningful feedback to developers when there’s still time to address issues. But many teams struggle to scale due to limited test engineering resources who can create the scripts. By adopting a codeless automated regression testing solution, teams can:
<ul>
<li>Have a scalable approach regardless of skillset</li>
<li>Build an effective regression test suite to scale with the organization – both vertically and horizontally</li>
<li>Automate end-to-end workflows without introducing risks</li>
</ul>

Building a scalable automation practice

To enable faster testing and attack the bottleneck from all angles – while still mitigating risk –you need to start by simplifying your regression testing. Here are five strategies to consider:
<ol>
<li>Increase execution speed with automation: Ensure your automation framework can handle different technology types such as mobile, web, thick-client, and legacy apps so that you can scale your test automation efforts across various applications and projects over time. Otherwise, you may encounter a case of tool fragmentation.</li>
<li>Reduce test scope by shifting to risk-based testing: Optimize your test strategy to mitigate business risk and make it easier for go/no-go decisions. Focusing test automation on the highest-risk areas will help to lower the test burden and increase release velocity.</li>
<li>Adopt model-based automation to drive overall coverage: Script-based solutions are hard to maintain, but model-based test automation frameworks enable you to update test cases in bulk, since many test cases can be built using various combinations of models. This means you can continue to drive more coverage over time instead of spending time maintaining what you’ve built.</li>
<li>Simplify test data and environment provisioning: These steps are sometimes overlooked because testers often wait for environments to be provisioned and to receive stateful test data. But by prioritizing test data management and environment provisioning up front (or, better yet, selecting a solution that includes these features), you’ll streamline the process and win back valuable cycle time.</li>
<li>Up-skill your current team members: Script-based solutions have their time and place, but they require automation engineers. With a codeless solution that’s business-user friendly, more of your current staff can meaningfully contribute to automation – and you can scale faster.</li>
</ol>

Cut regression testing timelines from days to hours

If you are conducting regression testing on a regular basis, then you need a product like <a href="https://be.tricentis.com/products/automate-continuous-testing-tosca/">Tricentis Tosca</a> to automate at scale, simplify maintenance, and accelerate end-to-end testing across your entire digital landscape. Tosca’s codeless, AI-powered approach takes the bottlenecks out of testing and the risks out of software releases so you can execute resilient, automated regression tests.
&nbsp;
Tricentis customer <a href="/case-studies/agl-energy">AGL</a> is a leading provider of gas, electricity, and solar photovoltaic solutions in Australia. To support its Customer Experience Transformation (CXT) program, AGL’s management launched an Idea to Production in five days initiative for AGL’s SAP delivery units. One key hurdle to this acceleration was AGL’s lengthy regression test cycles. By implementing Tricentis Tosca, AGL can now complete the regression testing around its SAP initiatives — which previously took more than a week — in only a single day.

Tricentis Tosca for intelligent test automation

How to cut regression testing timelines from days to hours

It’s time to verify application performance under load. 
The evidence:
<ul>
<li>Under intense interrogation, an XYZ customer showed signs of impatience and admitted to abandoning the application because it was slow to load.</li>
<li>A DevOps team member picks an XYZ manager out of a line-up as the one attempting to impersonate a testing expert and trying to learn to code complex performance tests.</li>
</ul>
XYZ Corporation’s user base has scaled exponentially, but during peak times, there’s evidence of the application slowing down. It doesn&#8217;t take a detective to know that slow-performing applications are the number one reason for site and application abandonment. If a page doesn&#8217;t load within 4 seconds, XYZ will most likely lose customers and compromise brand value. XYZ executives have tried to speed up testing by bridging the gap between experts and non-experts. But scaling testing across teams brings a long learning curve, especially for team members who don&#8217;t possess deep coding knowledge.

<a id="clue-3">Clue #3: You're getting close to cracking the case, but first you must ponder this. If your application doesn’t perform at scale...you may fail. </a>

According to the <a href="https://www.capgemini.com/insights/research-library/world-quality-report-wqr-2021-22/" target="_blank" rel="noopener">2021 World Quality Report</a>, 42% of organizations have little to no adoption of automated functional or load testing solutions. But as your application matures and adoption increases, you need to verify that your application can perform under load to prevent downstream performance issues. Creating a load and performance testing strategy will help you:
<ul>
<li>Achieve quality at scale across releases and apps</li>
<li>Provide meaningful feedback on performance quickly, while developers can still do something about it</li>
<li>Simplify load and performance testing to empower every team to incorporate performance data into their go/no-go decisions</li>
</ul>

Ensuring your application performs as your user base grows

But when do you know you’re ready for load and performance testing? Typically, it is when you start to experience degradations in responsiveness, load times, and stability. For most organizations, degradation happens when the application surpasses around 100 to 200 users. This range tends to apply to custom built applications, like a web portal, site, or SaaS tool. Load and performance testing is generally not doable for a packaged application since you don&#8217;t own the infrastructure that an application sits on, such as the database.
&nbsp;
Here are <a href="https://www.tricentis.com/learn/load-testing">five ways </a>to optimize your load and performance testing: 
<ul>
<li>Generate virtual users: A realistic load test includes virtual users, each running a predefined scenario. Apps can&#8217;t differentiate between virtual and real users, making this an effective way to identify where problems may arise.</li>
<li>Set up unit performance tests: Before creating load tests, you should set up unit performance tests, which can be done when that section of code is ready. If you’re following a test-driven development (TDD) approach, you&#8217;ll need to set performance expectations and create executable tests for each code module.</li>
<li>Adopt a modular approach: Automating unit performance testing allows you to create a unit test library quickly. You then have many different modules which can be assembled into several test scenarios.</li>
<li>Do exploratory tests: Exploratory testing is an approach that prescribes testing sections of your app before it&#8217;s complete. This helps you explore the app/website without setting up specific scenarios.</li>
<li>Involve the whole team: To maximize the testing effort, follow an approach that builds performance testing into your development structure early and often, incorporating all team members on board. The Agile methodology is an excellent example of this – encouraging teams to communicate and collaborate to gain flexibility and responsiveness.</li>
</ul>

Introduce load and performance testing to ensure uptime and application stability

Tricentis <a href="https://be.tricentis.com/products/performance-testing-neoload/">NeoLoad</a> is a performance and load-testing solution that helps deliver responsive, scalable, and reliable applications in production to mitigate the damage to your reputation and revenue, while helping you deliver on customer expectations. Whether your software is cloud-based or on-premises behind a firewall, Tricentis NeoLoad has the flexibility to configure all use cases to generate load tests from both the server and client sides.
&nbsp;
<a href="/resources/neoload-webinar-telia">Telia</a> is a leading telecommunications operator in the Nordics. The company has massive quarterly synchronized releases, but its performance testing was scattered or relied on homegrown and open-source tools. LoadRunner Enterprise was available, but utilization was low, and the substantial license cost yielded poor ROI. Telia replaced LoadRunner with NeoLoad because it is a single program that addresses all its needs, including being more accessible, platform independent, and enabling parallel executions. The Telia webstore experiences high loads when new iPhones are released. Using NeoLoad, Telia was able to identify and fix errors before release days for a smooth launch. Telia was the only major telecom operator with a site that stayed up on release day.

Tricentis NeoLoad for performance testing

A new approach for browser-based performance testing

Congratulations! You have solved “The Case of the Missing DevOps Testing Strategy” and helped XYZ Corporation avoid delaying the release of its new software. By following the evidence, you sleuthed out the best next steps for maturing your testing practice.
&nbsp;
Clue #1 led you to<a href="https://www.tricentis.com/products/unified-test-management-qtest"> Tricentis qTest</a> to centralize and organize testing by sending Excel charts to the testing jail. That success set you up for a strong foundation for Clue #2 as you built scalable automation practices with <a href="https://www.tricentis.com/products/automate-continuous-testing-tosca">Tricentis Tosca</a>. Clue #3 cracked the case as you discovered that load and performance testing is needed to ensure stability as your user base grows. And you probably already had a hunch of the outcome since <a href="https://www.tricentis.com/products/performance-testing-neoload">Tricentis NeoLoad</a> integrates with both Tosca and qTest to power the ultimate DevOps testing strategy.
&nbsp;
Now on to your next assignment … we still haven’t found that Tester in the Study with the Spreadsheet.

Closing the case on DevOps testing strategy 

In this demo, we’ll provide an overview of qTest Manager, Launch, and Pulse applications for test case management, centralized test automation, and DevOps orchestration, including:
<ul>
<li>An example of how to manage automated testing using Tricentis qTest, Tosca, and NeoLoad</li>
<li>How to orchestrate automated testing within a DevOps delivery pipeline with open source test tools, Jenkins, and chat ops notifications using Slack</li>
<li>How to orchestrate automated testing for an SAP Fiori application using Tosca and Azure DevOps pipelines</li>
</ul>

Automate, orchestrate, and accelerate testing within DevOps workflows using Tricentis qTest

Today, the new challenge organizations face is not just dealing with application changes, but also with environment, data, and business process changes in parallel. This heightened complexity makes the need for complete, end-to-end testing greater than ever before.
Read this buyers’ guide to learn about the must-have capabilities when choosing the best test automation tool, including:
<ul>
<li>End-to-end coverage across complex application landscapes</li>
<li>AI-powered test automation and self-healing AI</li>
<li>No-code, low-code approach</li>
<li>Risk-based prioritization and test case design</li>
</ul>
Download the buyers’ guide and learn what’s needed to help ensure your applications and end-to-end business process work flawlessly – no matter where changes occur in your complex, entangled IT and application ecosystems.

10 must-have capabilities for complete, end-to-end test automation coverage

Maybe you’ve thought about changing your performance testing platform, but have a lot of fears: Will you waste money? Lose valuable time? Open your company up to risk?
Change doesn’t have to be scary.
Read this eBook to learn five reasons why changing performance testing platforms shouldn’t be frightening, and a few strategies to ensuring your migration is a success, like:
<ul>
<li>How to pinpoint the best approach to performance testing</li>
<li>Why you need to consider the breadth and complexity of your systems landscape</li>
<li>A checklist for finding the right partner</li>
</ul>

Guides & Insights

The case of the missing DevOps testing strategy

Follow the clues to reveal the path to maturity