Here comes a testing focused article after a series of technical blogs! It is based on experience with projects managed through waterfall processes and it continues the series about tackling test complexity.
It is about a luxury that we so often ask for and we often don’t have in testing: to be involved early in the product development process. What does it mean actually to be involved early in the process? Why is it so important? And how does it help tackling test complexity anyway?
We argued in a previous article that independent testing is about the way testers act and the quality of information that they provide, rather than about the way they are organized or governed. Organization and governence still tend to have a crucial impact on independence. That’s perhaps the reason, why some of defined standards approach testing independence from the point of view of the organization (, ). I prefer to talk about organizationally or governence-wise separate testing rather than independent testing in this context. Here is why.
Testing independence is being referred to in various ways: organizational independence of a test team on other teams within a company, independence of a testing service vendor on other vendors, or testing as an independent engineering or scientific discipline. This blog site intends to refer to software testing as a business function and its in/dependence on other business functions (e.g. software development or other, even non-technical functions). Let me hence, share my perspective on independent testing from this angle and contrast it with outsourcing testing services, given that I see their usage often confused.