In the last issue, I introduced this series of articles on critical software testing processes. For our first article, let’s look at the processes associated with an essential precondition for any test activities: creation, delivery, and installation of a software release into the test environment. Without software to test, there can be no software testing, but, as obvious as this is, many software development organizations do a poor job of managing test release processes. Often, the role of building a test release devolves into the test organization, which is generally ill-prepared to handle the tasks, and the processes are defined reactively— to put out fires—not proactively—to handle key roles optimally.
Read this article → (PDF 236 kB)
Category: Best Practices