Tuesday, February 4, 2014
Troubleshooting skills for a software tester?
Its been a lot of time that I've added a post. Apparently, its more than 3 years since I've written anything here. Recently I had been writing some things at my work, which has also inspired me in writing this blog.
Read more »
Any time someone discusses what are the qualities which a good software tester should posses, this note certainly comes up that he needs to know coding. That's when he can identify and dig deep into code and do more deeper levels of testing. But there is one quality which is more important Troubleshooting skills. I feel good troubleshooting skills are going to take a good software tester into better levels. Skills to troubleshoot an issue would be important, as this would get to be a direct pointer into root cause analysis at times. More than anything, this would help the tester get more idea regarding the environment details (thereby environmental dependencies as well) and also expose some more scenarios which would probably be candidates to find interesting bugs.
Labels: MSDTC issues, testing skills, Troubleshooting skills
Saturday, December 11, 2010
Mixing multi-dimensional thoughts into Testing
I was thinking for a solution to the question what should be the team composition to cover the maximum possible test scenarios that can be thought of, while testing an application/product. It was then that the idea of different people testing the same application in different perspectives came into my mind.
Read more »
Read more »
Labels: Mixing multi-dimensional thoughts into Testing
Tuesday, March 30, 2010
Software Testing Demystified part 5
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.
Read more »Labels: Black-Box Testing, Software Testing Demystified, White-Box Testing
Thursday, March 18, 2010
Software Testing Demystified part 4
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
Read more »Labels: Software Testing Demystified, System Testing
Tuesday, March 16, 2010
Software Testing Demystified Part 3
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.
Read more »Labels: Integration Testing, Software Testing Demystified
Thursday, March 11, 2010
Software Testing Demystified part 2
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.
Read more »Labels: Software Testing Demystified, Unit Testing
Monday, March 8, 2010
Software Testing Demystified Part 1
Many of times, I have felt that majority of the testing community are aware of different terminologies used in software testing, but do not really understand what the significance of these are! This is not a real good sign for us testers. That is the motive that I came up with this topic of demystifying the types of testing.
To start with, let us talk of Software Testing as such. Software testing could be defined as the process of verifying and validating the software against the requirements, as well as the industrial needs, respectively. Many of the proclaimed testing universities have got their own definitions for testing. But to put it down in simple words, for a Test Engineer, Software Testing should be the process of finding out bugs.
Read more »Labels: Software Testing Demystified
Subscribe to Posts [Atom]
