Part 2 – INDEPENDENCE OF TESTER

This video discusses the concept of independence in software testing, specifically in the context of the ISTQB FL and SAP testing.

ISTQB 4.0 highlights that independence in testing is important because it helps testers identify defects that may be overlooked by the developers due to cognitive biases. However, independence should not replace familiarity, as developers can effectively find defects in their own code. There are different levels of independence: low level (author testing their own work), medium level (peers from the same team testing), high level (testers from outside the author’s team but within the organization testing), and the highest level (test activities given to people outside the organization). In most projects, it is recommended to have multiple levels of independence. Developers should perform component and component integration testing, the test team should focus on system integration testing, and business representatives should perform acceptance testing. This follows the “4 eye principle” where dedicated testers with different backgrounds and perspectives can identify various types of failures and defects.

While independence in testing has benefits, there are also drawbacks. Independent testers may become isolated from the development team, leading to collaboration and communication issues. They may also be seen as a bottleneck or blamed for release delays. Developers may lose their sense of responsibility for quality if testing is entirely independent.

In the case of SAP testing, the concept of independence may not be as applicable or beneficial. SAP systems are complex and require specialized knowledge, making it challenging for independent testers without deep understanding of industry-specific requirements and business processes to identify potential defects. Instead, involving testers with specific SAP expertise relevant to the project may be more efficient.

SAP testing often involves close collaboration between developers, testers, and business representatives due to the need for a deep understanding of the system’s business processes and workflows. Independent testers disconnected from the team may lack the necessary context and face difficulties in collaborating effectively. Therefore, a collaborative environment where testers can work closely with developers and business stakeholders is crucial for comprehensive testing.

While the principle of independence in testing holds value in many software development projects, SAP testing presents unique challenges that may limit its applicability.