MORE SPEED & EFFICIENCY IN YOUR TEST AUTOMATION

3 HACKS TO GET YOUR SOFTWARE TEST

AUTOMATION UP AND RUNNING FAST
STARTING WAS NEVER SO EASY
HOW TO APPROACH SOFTWARE TEST
AUTOMATION FOR ANY PROJECT
Efficiency and speed in testing are the keys to success in the DevOps age. High software quality and fast results despite
increased release frequency. But how do you address the initial automation effort when automating testing for your software or
switching to a new test automation tool?

Where should you start? What is the best strategy? What is the best way to select and prioritize the test cases to automate? How to have
everything automated and running as quickly as possible?

With our 3 hacks and the roadmap checklist you have a simple and clear guideline for the success of your test automation.

Have fun reading and implementing!

Tobias Müller
Managing Director
HACK #1: VIDEO AS A BASIS FOR TESTING
MORE SPEED IN YOUR TEST
AUTOMATION
In order to automate test cases, a test case script is needed. What are the steps,
what is expected. These scripts can be very time consuming. And for automation
you need to know the software well to understand the script.

If you make a video of your test case instead of written scripts, anyone with no prior
knowledge of your application can automate the test cases and confusion is avoided.

YOUR BENEFITS:
• It’s much easier to find people to automate the test cases without training on
your software
• Test cases are created faster than if you have to write detailed scripts
• Error rate and effort for queries are reduced to a minimum
Video as test case HACK #1: VIDEO AS A BASIS FOR TESTING
description & design
 How does the test case run?
 Which test data and dependencies must
MORE SPEED IN YOUR TEST
be given?
 What must be verified during the AUTOMATION
process? (Verification points)
 Which value is expected in which field?
 Or are the values dependent and can be What do you need to keep in mind to ensure that your video test cases produce
calculated? If so, how? meaningful results with minimal effort?

Basis for test case

Use your video to answer the questions listed on the left. Either on the audio track,
automation
as a text insert or in a separate file. And remember to include any test data and
 Video
 Test data configurations with the video.
 Configuration
 CUSTOMER EXAMPLE
997
Total test cases
748
Test cases that can be automated
102
Test cases with the greatest impact
~10%
of the test cases cover
>60%
the functionality from
HACK #2: SELECTION OF THE TEST CASES
TEST COVERAGE AS A
STRATEGIC IMPLEMENTATION
You have several hundred test cases and don't know where to start with
automation? According to which criteria should the test cases be prioritized?
To quickly achieve good test coverage, only a fraction of the test cases need to be
automated. With 10% of the test cases you can already achieve a 60% coverage of
the functionalities. See the customer example on the left.
YOUR BENEFITS:
• High coverage of functionalities in the shortest time possible
• After the majority of the application is covered by the test cases, the other test
cases are automated much faster
• Quickly a good control over the software quality
Your Application
BEFORE: How test cases usually get
prioritised for test automation
… whithout coverage of the application in
mind.
HACK: Start with the test cases that give
you a decent coverage of the application
HACK #2: SELECTION OF THE TEST CASES
TEST COVERAGE AS A
STRATEGIC IMPLEMENTATION
Prioritize your test cases strategically so that you achieve the greatest possible
coverage with the smallest possible number of test cases.
In the model-based approach, you achieve a good base model, which allows you to
automate the other test cases much faster.
Priorisiere die Testfälle nach den folgenden 3 Kriterien:
• High traffic: Which features does the end customer/user use most often?
• Past defect severity: In which areas have the most serious problems occurred
in the past?
• Functional coverage: Which test cases contribute most to my model?
HACK #3: DON’T RELY SOLEY ON UNIT TESTS
COMBINE TEST STACK TO ENSURE
YOUR SOFTWARE QUALITY
Unit tests are great, but they are not enough and not the most efficient way to
test all your software. And they are not traceable, a must if you are in a
regulated environment.

With the main focus on unit tests, in the long term the quality of the software is no
longer fully guaranteed. The combination of unit tests, integration tests and end-to-
end tests will give you back control over the bugs.

YOUR BENEFITS:
• All levels of the test pyramid are covered in the long term
• High software quality throughout the entire lifecycle - even with agile teams
• Higher customer satisfaction and fewer support tickets
Unit Tests Over Time in
Agile Teams HACK #3: DON’T RELY SOLEY ON UNIT TESTS
COMBINE TEST STACK TO ENSURE
YOUR SOFTWARE QUALITY
Unit-Tests are a must-have in today’s development teams. The challenge of
unit-tests is maintenance and documentation and level of testing.

Integration and end-to-end testing is a long term, fully traceable approach to ensure
quality in terms of regression testing, i.e., does the existing functionality still work as
expected in the new software version. The magic formula:

Unit Testing + Integration Testing + End-to-End Testing

Unit-tests as only testing effort will lead over time to a broken testing pyramid
forcing even more end-to-end tests.
TEST AUTOMATION
ROADMAP CHECKLISTE
01. PLANNING  Implementation of the Test Automation Framework
 Is the vision for automation named?  Model for Subject Under Test completed
 What will be automated? (Which modules/processes)  Test data generation/source defined
 How much is automated? (Which test cases)  Additional logging for debugging built in
 Has the budget been released?  Specific support interfaces implemented
 Is the Test Automation Plan defined  Reporting
 Is the high-level test automation design defined?  Result reports defined
 Is the schedule defined?  Integrated with Bug Tracker
 Integrated with Testcase Management Tool

02. IMPLEMENTATION
03. EXECUTION
 Is tool know-how available?
 Error handling options available
 Is configuration management defined?
 Test case logs
 Version control of the Subject Under Test (SUT)
 Subject Under Test Log Files
 Control of the test environments
 Error analysis
 Is the deployment defined?
 Optional: Verification/validation of the test platform
 Synchronized with Software Development Lifecylce (SDLC)?
 Deploying and resetting the test environments  Metrics defined for test automation progress

 Is Continuous Integration defined? 04. MAINTENANCE

 When are tests started/triggered?  Preventive
 Parallel execution of test sets?
 Corrective
 Is the management of the automation project source code defined?  Improvements/optimizations
TESTRESULTS.IO
THE FUNDAMENTALLY NEW APPROACH TO NEXT
GENERATION SOFTWARE TESTING
WHY TESTRESULTS.IO?
Get the power and freedom of the #1 IDE and the no-code/low-code
automated testing – easy to maintain – all in one powerful solution. Minimal Testing Like a Human.
maintenance effort and the warm feeling of being in control over the bugs in Everything a person can use, you can
your software. automate with TestResults.io end-to-
end.

You shouldn't waste your time and nerves on maintaining your test automation. Full-Stack Testing. One and the
Gain back your time and the good feeling of being in control over the bugs in same test case can be used to check
your software with TestResults.io: the entire application, from the UI to
business logic and generated reports.
🚀 super-low-maintenance
🚀 no flaky test cases Dynamic & Visually Complex
Scenarios. Easy automation of
🚀 easy to use, low entry level, intuitive dynamic elements and visually
complex test cases like tables
🚀 super stable or even 3D modeling and
rendering software.
🚀 detailed bug insights in 3 clicks

Book your FREE demo now!