Successful implementation of reusability in software QA testing throws up many challenges. They might be difficult to answer; but they are certainly not impossible. Here we have a look at the most difficult challenges that lie in the effective implementation of reusability.
Reusability in Software / QA Testing - Conceptual Understanding
The Software QA / testing domain is a very rich field that could be mined for the benefits of reusability. Most of all QA actions such as clicking an object, opening a page, executing a command, verifying the output, generating different kinds of test data etc., are very generic in nature and wide in scope, they are just molded a bit as per the specifics of any project.
Before we discuss about how reusability can be implemented, let’s first have a look at the benefits that reusability brings; and the challenges which confront its implementation. Having a look at the both of these will help us appreciate reusability to a higher degree.
Before we discuss about how reusability can be implemented, let’s first have a look at the benefits that reusability brings; and the challenges which confront its implementation. Having a look at the both of these will help us appreciate reusability to a higher degree.
Doing Out of the box Software / QA Testing.
"You need to think out of the box." or "Develop your out of the box testing skills" is one common KRA (Key Result Area) that is commonly set in our appraisals :) So what exactly is out of the box thinking ability which a software tester needs to inculcate?
Well for starters, when managers complain about you not having "out of the box" thinking abilities, what they mean to say is that most of your testing is simple, and the defects that you are reporting are again simple. Think, if you have really caught some complex defects recently? How about the defects that were leaked in the latest release? Why were they missed? Did the existing test cases not cover them? If yes, then what testing should have been done to catch them earlier? Are you getting the picture?
Well for starters, when managers complain about you not having "out of the box" thinking abilities, what they mean to say is that most of your testing is simple, and the defects that you are reporting are again simple. Think, if you have really caught some complex defects recently? How about the defects that were leaked in the latest release? Why were they missed? Did the existing test cases not cover them? If yes, then what testing should have been done to catch them earlier? Are you getting the picture?
How to be a Better Test / QA Manager?
Congratulations, now that you have become a Test / QA Manager in your company. So how do you aim to turn from a novice QA Manager to the Best QA Manager? Well, help is at hand. :) Read on for simple but effective advice to make this transformation.
How to do a Test Bug Bash for your Software Project?
Bug Bash is a unique exercise that is seldom used by projects. Not many people are aware as to what is a bug bash, and why it is used. Lets start our learning process about software bug bash activity.
What is a Bug Bash?
Bug Bash is a test activity that is carried out by a number of people of simultaneously. It may comprise of people of the same team, or it could have people from different teams participating in it. It is not uncommon to involve people in a bug bash who are not exposed to the product at all. It places no constraints of the type of people that may participate in it. It is common to see developers, analysts, managers as well as testers take part in project bug bashes.
What is a Bug Bash?
Bug Bash is a test activity that is carried out by a number of people of simultaneously. It may comprise of people of the same team, or it could have people from different teams participating in it. It is not uncommon to involve people in a bug bash who are not exposed to the product at all. It places no constraints of the type of people that may participate in it. It is common to see developers, analysts, managers as well as testers take part in project bug bashes.
Test Case Prioritization
Different organizations use different scales for prioritization of test cases. One of the most commonly used scale prioritizes the Test Scenarios into the following 4 levels of Priorities.
- BVT
- P1
- P2
- P3
Principles of Test Automation Designing
Test Automation is not an easy process. While designing it various factors need to be considered. The essential guiding principles we should follow when developing our overall test strategy (or evaluating the test strategy of a tool we wish to consider) are mentioned below. Read on...
Traits / Habits of a Good Software / QA Test Engineer.
Working in the software industry for more than a decade, I find that sometimes I enjoy working with some software / QA testers more than with others. Digging a bit deeper into what makes me enjoy working with these people, I came to form a list of certain traits and habits which are common across these high performers. I strongly encourage you all to adapt these habits and distinguish yourselfves in your teams.
Posts
