Shift-left testing emphasizes the “ Testing Early”
the principle of testing.
Early testing
“To find defects early, testing activities shall be
started as early as possible in the software or
system development life cycle and shall be
focused on defined objectives.”
2. Shift-Left Testing and Continuous Testing
• Implementing agile practices without the shift-left
approach may result in your software to lack
quality or have a delay in its delivery.
• Shift-left testing emphasizes the “ Testing Early”
principle of testing.
Early testing
“To find defects early, testing activities shall be
started as early as possible in the software or
system development life cycle and shall be
focused on defined objectives.”
3.
4. Benefits of Shift-Left Testing
As you can see from the previous graph, the testing process should start in the requirements phase.
There are two reasons why the testing team should shift left from the requirements phase.
Providing fast feedback
The fast feedback is crucial for the development team. Therefore, if you can send feedback in
advance to your team that the requirement will cause an error, it will be the most precious feedback to
your team.
Reducing costs of a bug/risk
The early you reveal and fix the bug, the more you can solve and get rid of it cheaper. The issue is,
you may never have a chance to get the time to fix the bug or return what the bug causes. Shift Left
can enable teams to reveal bugs early and get cheaper solutions.
5. What is Continuous Testing?
Continuous Testing is the process of
executing tests as part of the delivery
(DevOps) pipeline to get faster feedback
on the potential software bugs related to
a release as soon as possible.
Continuous testing supports the teams
that are working on release,
deployment, and operation. In other
words, continuous testing is the
approach which enables continuous
deployment for development teams.
6. Continuous Testing
Old-fashioned manual testing methodologies are inadequate to support the DevOps pipeline in terms of
coverage, speed and risk elimination. Therefore, to be able to apply continuous testing, using test automation
in different levels of testing is a basic requirement.
• Continuous testing is substantial to be able to provide fast delivery of a high-quality product.
• Continuous testing process provides testing to take care of your risks at several stages including an early
stage, delivery, and even the production stage.
• The only thing you should do is pairing your testing suites to the correct stage of your pipeline.
7. Continuous Testing Benefits
Prevents
bottlenecks
Optimizes test
execution in
terms of time
Supports Shift
Left in terms of
test execution
optimization and
test coverage
Embraces Shift
Right in terms of
monitoring,
APM, Testing in
Production
8. The Testinium Effect
• Testinium is a cloud-based test automation tool that executes test scripts.
• Testinium provides time-saving by preventing you to set up test environments
such as Selenium Grid or executors.
• In addition to that, Testinium offers real mobile devices and web configurations.
You can see below:
• Ubuntu with Chrome Browser.
• Windows 7 with Firefox Browser.
• Chrome Browser in iOS 11 and derivations.
• Google Pixel 2 with Firefox Browser.
9. Testinium Support
• The first thing that Testinium supports you in terms of agile practices is the speed of the delivery.
• It offers you help with the testing infrastructure, handles it for you and saves a lot of time. The only thing
left for you to do is scripting your tests.
• Agile teams must develop quality assurance and quality control processes to avoid time pressure and
achieve fast delivery. To help out the agile teams in terms of quality and test, Testinium can support and
help out with the time pressure in terms of test coverage and fast feedback.
10. Conclusion
• Teams that are following agile practices should keep in mind that being agile in the development phase is
not enough to satisfy business line of the product. To be able to deliver a high-quality product fastly, all
these approaches should be considered and implemented by teams within their own Software
Development Life Cycle (SDLC) culture.
• In total, these approaches or methodologies will never help you out as individuals. Therefore, you should
build your SDLC considering your resources and needs.
• Continuous testing and shift-left can be used separately or independently. The main issue is that they are
not enough by themselves without the support of test automation, a strong test design, and a deep agile
practices understanding.
• In the testing part, implementing test automation in different kinds of testing levels is crucial to support
the quality of the product
• Click here to check out Testinium to experience the Testinium effect yourself!