Get a demo or trial

Company

Services & Support

Resources

Events

Contact us

Introducing Tricentis qTest Copilot

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

Accenture

Amazon Web Services (AWS)

Capgemini

Cognizant

DXC Technology

qTest users following standard testing methodology

ContiTech streamlines global SAP testing with Tricentis qTest in major business transformation program

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’

GTCR Makes $1.33 Billion Investment in Tricentis

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

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

Jake Paul vs. Mike Tyson: A match for the ring — and Netflix&#8217;s servers?

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

An introduction to cucumber test automation

Jira testing workflow: how to use jira for testing

UI performance testing: A comprehensive guide

How to manage test cases in Jira

Recovery testing: what, why, and how

<h3>How a Tricentis Testim customer transitioned from manual testing to 40,000 automated UI tests in five months</h3>
Do you want to make the jump from manual UI testing to automated testing for your AI-driven application, but don’t know where to start? In this guide, you’ll learn the four steps to kickstart your UI test automation strategy to save time, improve test coverage, and reduce production errors. You’ll also learn how Tricentis customer Globality successfully put these steps into practice using <a href="/products/test-automation-web-apps-testim/">Tricentis Testim</a>.

Globality is the number one B2B services marketplace and matches leading companies with small and midsize service firms worldwide for specialized high-value projects. Globality has revolutionized the RFP process with AI technology, and millions of people use its platform and transact billions of dollars every year. Here are the steps they took to modernize the QA process to deliver a high-quality experience.

default

It’s important to set clear and achievable goals when identifying a business objective–the same is true for test automation. Some goals organizations like yours might have in mind include:
<ul>
<li>Improving quality to enhance user experience and employee satisfaction</li>
<li>Implementing quality checks earlier in the lifecycle and detecting defects sooner</li>
<li>Reducing resource waste (time, money, or the dreaded ‘brain drain’ of your most technical experts) and shortening delivery time</li>
</ul>
&nbsp;
Setting the right goals means establishing specific outcomes in certain time frames. Be sure to analyze every step against that goal. Instead of boiling the ocean, think about making incremental improvements, one cup at a time.
<h3 style="color: #ffffff;">Globality’s software quality goals</h3>
&nbsp;
Given Globality’s high-end enterprise clientele, quality is a core value and an exceptional user experience – every time – is a must.
With these things in mind, Globality set out to accomplish the following software quality goals in six months:
<ul>
<li>Improve product quality by increasing test coverage by 50%</li>
<li>Implement quality checks early by adding automation into its sprints</li>
<li>Free up manual testers for more exploratory and usability testing</li>
<li>Keep the number of bugs that slip to production at 0 to 1</li>
<li>Set up cross-browser testing</li>
</ul>

Step 1: Set the right goals for test automation

The next course of action for companies looking to move to automated testing is to find a suitable time to introduce automation into your journey, identify the right quality level, and then prioritize your testing around it. Incorporating 100% test automation is unrealistic – you’ll always need to augment automation with manual testing. Consider the things you do most frequently and allocate sufficient resources to automate those tasks. Look at what’s driving revenues, user flows, or bottlenecks. Here are two ways of thinking to consider:
<ul>
<li>Risk-based approach: Identify user flows that are critical to your business or areas of the application that are more stable. For example, if 90% of your users use the same set of features, you might want to automate testing for that feature set because any issues would affect 90% of your user base. Another example is the checkout process, which is a revenue-generating flow.</li>
<li>Conversation-led approach: Most context-driven software quality professionals are subject matter experts who know the systems they test inside and out. Having these team members consult with developers or testers to identify repetitive areas for automated testing can go a long way toward understanding where automation can add value and where it can’t.</li>
</ul>
&nbsp;
With the right automation approach, manual testing can be limited to a few critical areas. While automation might be able to test those areas of the application, you may find that the effort of authoring and maintaining those tests as code is too high.
One approach that can help you extend automation coverage is to think of your tests in building blocks. If certain steps are repeated across a number of tests, you can break these down into reusable components and share steps and groups of steps across tests. This can reduce duplication, improve visual understanding of the test flow, and simplify maintenance. If you do it right, then a big portion of your test will involve plugging the right building blocks together and making it easier to maintain, use, and extend coverage.

Step 2: Prioritize your automation efforts

Exploratory testing
&nbsp;
This type of testing primarily relies on a human’s skills–knowledge, experience, and creativity. Typically, it has limited execution time and no comprehensive documentation, making manual execution the best fit for this kind of testing.
&nbsp;
Usability testing
&nbsp;
This testing type aims to validate a product’s efficiency, usability, and ease of use. Manual testing lets your team assess and observe software quality first-hand.
&nbsp;
Ad-hoc testing
&nbsp;
This kind of testing, random and spontaneous, is nearly impossible to automate.

Manual testing

Regression testing
&nbsp;
Automated testing is advantageous here, as it can vet frequent code changes in a timely manner. Automating your regression suites allows for repeatability and saves time and effort through multiple test scenario reruns.
&nbsp;
Load testing
&nbsp;
Automated testing allows just one developer to easily simulate thousands of concurrent users, database queries, and server requests.
&nbsp;
Performance testing
&nbsp;
Automation is ideal for performance testing, as it allows teams to simulate simultaneous users while being able to track various metrics.

Automated testing

Here are our recommendations for what to automate and what’s better suited for human testers:

After determining what needs to be automated, through conversations amongst team members or according to the highest business risk, companies should start to streamline their QA and development work. Here’s how Globality did it.
Globality takes a unique approach to R&amp;D, assembling groups of engineers based on the project at hand. For example, when Globality needed to develop a payment system, they created a group that worked together for a few weeks until the project was complete.
Similarly, QA groups are assembled based on specialized tasks and the skill sets required for each project. Globality’s Head of QA is looped in at the design phase to determine the best strategy and team for testing a new component or set of features.
Once a week, Globality’s developers push the changes to testing, and QA begins. Some of the testing challenges the team have encountered include:
<ul>
<li>Constant change across the product and its users required a high volume of testing</li>
<li>Difficulty striking the right balance between progression and regression testing</li>
<li>Content changes to the interactive dialogue made it difficult to create fixed tests</li>
</ul>
&nbsp;
<h3>Tricentis Testim’s impact on Globality’s software quality initiatives</h3>
&nbsp;
Globality tried to automate its functional and end-to-end testing for two years using Selenium. According to Zeevik Neuman, Head of QA for Globality, “The number of features we had plus the amount of maintenance made it too time-consuming to continue with Selenium.”
Globality’s first objective was to automate the product’s entire happy path. The team was able to complete this task using Tricentis Testim in under a month. In just thirty days, test coverage increased by 30%.
According to Ran Harpaz, Globality’s Chief Technology Officer, &#8220;The wow moment was when Tricentis Testim took our most complex flow, the project brief, and automated that in a few days. We plugged that into our pipeline and quickly saw that maintenance was much more manageable.&#8221;
Globality then began testing different browsers and quickly started detecting bugs. As teams continued assembling and disassembling, Testim made it easy for developers and QA to work together ensure quality.
“Now, I can say with confidence that I am testing every aspect of the system, and we’re releasing with confidence. Decisions are made on facts, not feelings,” Harpaz said.
There used to be a misconception that automated testing was not as easy as “set it and forget it,” where you can author a test once and let it run on its own moving forward. Before AI, this was true. Developers and testers used to spend up to 50% of their time regularly maintaining the automated testing scripts alongside the application source code. Failing to do this led to false test results.
Now, with AI, testing is easier than ever before. Tricentis Testim uses AI to speed up the authoring, execution, and maintenance of automated tests.

Step 3: Streamline QA and dev work when change is constant 

Testing AI systems is not easy. The challenge is managing constant change, as a learning system will change its behavior over time, meaning what’s correct today will be different tomorrow. A software quality professional requires the skills to interpret a system’s boundaries, as there are always certain boundaries within which the output must fail. To ensure the system stays within these boundaries, developers and testers must not only look at output but also at input.
When developing an AI solution, the testing task is a vital activity. Whoever performs this task must ensure that the functional and nonfunctional requirements are fulfilled. How is this different from testing traditional software? Because of the complexity of managing change, the software’s behavior is much harder to predict. The complex functioning of an AI system has many more input values that must be tested to verify the outcomes.
These are some commonly asked questions when it comes to testing AI:
<ul>
<li>What are the acceptance criteria?</li>
<li>How can we design test cases that test those criteria?</li>
<li>Are there different data sets for training data and test data?</li>
<li>Does the test data adequately represent the expected outcomes?</li>
<li>Is the training data biased?</li>
<li>What is the expected outcome of the model?</li>
</ul>
&nbsp;
<h3 style="color: #ffffff;">Four simple steps to fuel testing transformation</h3>
&nbsp;
With the right goals, strategies, and tools in place, Globality modernized their testing strategy from manual testing to automating 40,000 UI tests in just five months. Your organization can do the same by following the recommendations outlined above.

Step 4: Use AI to test an AI-based system

Given the rapid changes in the application development world, how should teams adapt their QA practices to deliver high-quality releases faster in 2022 and beyond? To answer this question, our test automation design team will share some of their learnings to inject into your practices moving forward.
Watch this webinar to learn: 
<ul>
<li>Tips and tricks to address typical testing issues such as building trust with test status and improving test stability with clean tests</li>
<li>How to manage growing tests and teams with Tricentis Testim, a low-code AI-based solution</li>
<li>Answers to a selection of your most pressing, head-scratching questions</li>
</ul>

Best practices for UI test automation in 2022 and beyond

Whether you are building test automation for your custom web app for the first time, or you’re a seasoned Selenium veteran, you’ve undoubtedly encountered some hard-to-test challenges. Perhaps it’s a stability issue caused by a dynamic UI, or your application uses multiple tabs, embeds iFrames, or has various, nearly- identical elements.
Watch this webinar to learn: 
<ul>
<li>Some of the tricks to address typical testing issues such as picking a test coverage strategy</li>
<li>How to manage growing tests and teams with Tricentis Testim, a low-code AI-based solution</li>
<li>Answers to a selection of your most pressing, head-scratching questions</li>
</ul>

How to scale UI test automation with Tricentis Testim

In this 5-minute product tour video, you will learn how Tricentis Testim accelerates UI testing for customer-facing web and mobile applications with highly resilient automated tests. See how the SaaS-based, AI-powered platform scales to help your Agile teams release faster and boost innovation.
See Testim features in action, including:
<ul>
<li>Fast codeless authoring with the recorder, test configurations, component reuse, auto grouping , and test scheduling</li>
<li>AI-driven and self-healing smart locators that build resiliency against false positives and improve test stability</li>
<li>TestOps mechanisms to manage your tests at scale, including the dashboard with key insights</li>
</ul>
The product profiled in this video is <a href="/products/test-automation-web-apps-testim">Tricentis Testim</a>. <a href="/software-testing-tool-trial-demo/testim-trial">Try it for free</a> or <a href="/software-testing-tool-trial-demo/testim-demo">request a personalized 1:1 demo</a>.

Guide

How to automate testing for AI systems

How a Tricentis Testim customer transitioned from manual testing to 40,000 automated UI tests in five months