Software Tester's Desk

There are quite a number of ways in which we can categorize Software Testing other than the types which are already discussed. Let me try to throw some light into the software testing classification based on the exposure of the application. The major classification of software testing are (this should have been covered earlier though) Black-Box Testing and White-Box Testing. This categorization, as I mentioned, is typically based on the exposure that a tester has to the application. All of the previously discussed categories of Software Testing come under these two basic and broad categories of testing.

Let me come to the most interesting and the most widely followed type of testing process in the whole world. Perhaps, many of us start within this phase and continue to do the same for much longer periods of time. Hey, don’t get confused! I am talking about the System Testing. Most of the product companies keep the name of their testing team as System Integration Test team or the SIT, but they majorly follow and perform system testing, and little integration testing

In the last post, I talked about the Unit Testing phase. Let me take up the topic of Integration Testing this time. Practically, Unit and Integration testing phases go together. Although we find many teams named as System Integration Testing teams, they typically are involved in System Testing and little integration.

In my previous post, I discussed about the classification of Software Testing on the basis of the Software requirements. In this post, I will try to cover how these are being accomplished in different phases across the development cycle in different Institutions. Since we have been talking about software testing alone, I will be following a bottom-up approach in describing about the various testing methodologies that are followed. Please note that this does not mean that the processes are always adopted in similar fashion and order always. There can be deviations at any phase.