Xento is a product based organisation with more than 800 IT Professionals including 350+ PHP Professionals working with a healthy dose of creativity and innovation. We promote an open atmosphere, where team members freely voice new ideas and are involved in all phases of our growth. At Xento, working is not just work; it's fun. Nurturing individual talent, fostering team work and recognition are the key elements of the Xento Culture.

Shift Left- Testing approach

Category: Software Quality

Shift left a unique testing approach

Shift left  testing is an approach in which software and system testing is performed earlier, in each phase of the project/product life cycle.
As we know, the software development life cycle goes sequentially in the order as:

Requirements => Design => Coding => Testing. So, if you start from the left to right, the testing phase is to the extreme of software development life cycle. “Bugs are cheaper when caught young, says Larry Smith, a well known expert, another reason why we should start testing at an earlier stage. This concept was introduced where testing/tester need to be integrated from inception of the projects / products.

The principle of ‘shift left’ supports the testing team to collaborate with all the stakeholders early in the software development phase to clearly understand the requirement, design, draft testcase and automation scripts  to help know where the software may fail and fix them at the earliest.

Benefit of shift left are as follows:

  • Business requirements are clear to a team members
  • Accountability of a QA personnel is in parity with other stakeholders
  • More individual interactions over the process and tools, working software over detailed documentation.

As a tester we can & need to engage ourselves initially to provide useful valid inputs, interact with management and operation team for a proper planned resources, tools and training interact with end users/clients. Furthermore, to know who is our user base and purpose of the software. our competitors in the market, to analyze this requirement for any ambiguity, completeness, testability, acceptance criteria definition etc. It is vital to provide real life example of current issues, attending design review meeting to understand and identify the design flaws. Nonetheless, suggestions should be made on alternate design options, identify the loopholes, and create test scenarios accordingly. It is important to carry out static testing, provide test case in advance to develop the code, and unit test, to adopt to test automation, and integrate the suite at all stages and to perform formal audit.

So, in a nutshell, it is important to get started with software testing earlier because a stitch on time saves nine. Besides this, shift left is a big leap in software development methodology that contributes towards robustness in market, improved software quality and saves time.

Author: Ratna Ganguly