Software testing should start early in the Software Development Life Cycle. This helps to capture and eliminate defects in the early stages of SDLC i.e requirement gathering and design phases. An early start to testing helps to reduce the number of defects and ultimately the rework cost in the end.

The various aspects of Early Testing which would help the QA Managers and Leads while developing or devising the Testing Strategy document in SDLC are explained here.

Adoption of Early Test will immensely result in the successful delivery of a Quality Product.

Load Testing is a very popular type of testing which all of us as testers must have come across.

So, while thinking of load testing, maybe, you are frustrated with the current solutions you are using and find it to be too difficult to write and maintain your tests. Or maybe, you are even thinking about doing load testing for the first time.

Either way, it’s a great first step to be thinking about load testing at all – which many companies don’t and suffer the consequences.

The testing world is moving at a very quicker pace with technological advancements in order to ensure “quality at the speed of light”.

“Continuous Integration, Digital transformation, life-cycle automation, shifting quality to the left to minimize costs” etc are some of the magical words that are swinging around. While we speak about these, the underlying question –“Why and how the defect was missed” still continues to be heard and remains unanswered as well.

This is the guide for software developers and testers to understand and start working on the very famous Agile SCRUM methodology for software development and testing. Learn the basic but important terminologies used in the Agile Scrum process along with a real example of the complete process.

We have listed all the Agile Tutorials in this series for your convenience. Hope they will be of immense help to you.

An overview of ‘shift-left in Quality’ and the differences between the concept of shift-left in testing and quality is explained in detail in this tutorial.

We have heard a lot of people talking about the concept of ‘Shift-left in Testing’. Well, we all understand what it is, but for the benefit of those who are new to this term or concept, let me explain in simple terms.

The term ‘Refactoring’ is mainly used to indicate required code cleanup/redesign.

In this tutorial, we will understand the definition of refactoring, discuss the need for code refactoring, and review the impact of refactoring code on various project team members. We will also discuss the answer for the most important question – As a tester, why do you need to know about refactoring?

A testing professional is required to thoroughly test the software developed to ensure if the software meets the end requirements of the customer.

A Business Analyst is also responsible to verify whether the software built and delivered meets the end customer requirements. This aspect of both the roles make it easier for a tester to switch to a business analyst role.

In this digital world, automation has become the core for businesses to grow and expand. Automation has revolutionized the way organizations operate their businesses.

The pace of advancement in technology has been on a continual increase for the last decade and lead us to a new automation age. The impact of automation is quite evident on distinct industries, including Software industry itself.

With the need for implementing API automation test for my projects, I have reviewed and developed proofs of concept (POC) using various tools and testing frameworks.

Honestly, it is a very challenging task to decide on the most suitable tool for my team of one senior QA and four junior QAs. There are several tools that can help with creating robust, light and maintainable scripts. However, they require technical skills. The other alternatives are easier to use but create brittle and temperamental tests.

This tutorial will give you a brief introduction of one of the most prominent testing types ‘Positive testing’.

Software Testing is the process of verifying and validating a software and confirming that it is working as expected. A software tester should have the intent to find defects and make sure that the application is working as expected. In order to achieve this different testing types and test techniques are used.