1 of 13

Welcome to Spiral Solutions

2 of 13

Our journey towards

Shift-left Development

Olga Cohen

Spiral Solutions

Noy Zikvashvili

Spiral Solutions

3 of 13

​

    • 99% of automated tests are E2E tests

​

    • Only QAs are responsible to create, execute and maintain test automation

​

    • Automated tests run manually by QA

​

    • Test automation starts after deployment

How we worked before

4 of 13

    • QA became a bottleneck

​

    • E2E tests became hard to maintain

​

    • Lots of flaky tests

​

    • No confidence in automation

​

    • Longer time to market

The Problem

5 of 13

Time for change

6 of 13

The Goal

Significantly reduce time to market without compromising on quality

7 of 13

​

The Solution

​

​

Shift-Left in Test Automation

​

Entire team is responsible for Test Automation

​

Integration of

Automated Tests in CI/CD pipelines

​

    • Shift Left Testing literally pushes testing to the “left,” i.e., to earlier stages in the pipeline
    • The Shift Left approach intends to identify and resolve bugs as early as possible in the development process

​

8 of 13

Shift-Left in

Test Automation

    • The Testing Pyramid is a framework that can help both developers and QAs create high-quality software.
    • It reduces developers’ time to identify if a change they introduced breaks the code.
    • It can also help build a more reliable test suite.

9 of 13

Entire team is responsible for Test Automation

With more and more companies making the shift left in their development process, testing and automation are no longer just QA activities—which means that the roles of developers and testers are beginning to blur.

10 of 13

​

Integration of

Automated Tests in CI/CD pipelines

​

    • Continuous testing means regularly testing software as it's being developed
    • Instead of waiting until the end to test everything at once, continuous testing involves testing small parts of the software frequently

11 of 13

We are in the middle of a transition

​

Our successes: 

    • Dev and QA are more independent
    • We think about how to test before a single line of code is written
    • Code is more testable and maintainable
    • Borders blurred between QA and Developers

​

Our difficulties: 

    • Change of mindset
    • Not enough expertise
    • Transition from existing E2E tests
    • Legacy systems are hard to test in lower levels (Unit/Component tests)

Where are we now?

12 of 13

13 of 13

Thank you!