Introduction to Software Quality Assurance
What do you do?
If you work in
Software industry then you might have faced this question at least once
in your life What do you do? Since Software Industry is now on the edge
that it is most news making industry and over the period of time
software have touched everyone's life, answering this question to layman
became easier than it was in the past few decades. Having said that
Developers might just say i create software. Using create word without
any doubt in mind. When the same question is asked to QA who in popular
term known as Tester he might need to explain a bit more on where he
relates to this 'create' word.
Gone are the days when software used to be totally made first and tested later (or was that the case anytime). In the new edge of software development companies or vendors are keener on providing building software by preventing flaw (which in terms of the software industry is called a bug) rather than fixing a flaw. And There is reasonable philosophy for doing that. Let's understand this with the example of making pizza.
Suppose you own a restaurant and the customer ordered a pizza with his own choices of toppings (maybe Pepperoni, Mushrooms, and Bacon) that he like with this pizza. You passed this order to the chef and he is preparing it while passing order you forgot to mention Bacon so Chef just knows that he needs to add Pepperoni and Mushrooms. He placed the base on pan added some base cheese added Pepperoni forgot Mushrooms and added cheese on top of it. Yeah!! The pizza is ready!! Your Stuart takes the pizza and notices that it is missing Mushrooms and Bacon. Since it is already cooked now is there a room to correct it? Ok let's make it fresh again ... Is it worth the cost? Is it worth the time? What if there was someone who was constantly checking and validating makings of pizza with customers order while entire pasta was being made.
This early entry of QA in Software Making process marked the beginning of a new era where QA's responsibility is not to find bugs but to prevent it. Since finding bugs and fixing it is costly and time-consuming process teams are now focused more on preventing bugs at all. So if someone asks me what do you do I answer I am QA and my first responsibility is to prevent bugs.
Those ways QA is not just tasting pizza but actually contributing to the process of creating pasta that will be appropriate for its customers.
How do I do that?
Am I an astrologer for codes who knows this particular part of code likely have bugs?
We will answer these questions in upcoming post.
Gone are the days when software used to be totally made first and tested later (or was that the case anytime). In the new edge of software development companies or vendors are keener on providing building software by preventing flaw (which in terms of the software industry is called a bug) rather than fixing a flaw. And There is reasonable philosophy for doing that. Let's understand this with the example of making pizza.
Suppose you own a restaurant and the customer ordered a pizza with his own choices of toppings (maybe Pepperoni, Mushrooms, and Bacon) that he like with this pizza. You passed this order to the chef and he is preparing it while passing order you forgot to mention Bacon so Chef just knows that he needs to add Pepperoni and Mushrooms. He placed the base on pan added some base cheese added Pepperoni forgot Mushrooms and added cheese on top of it. Yeah!! The pizza is ready!! Your Stuart takes the pizza and notices that it is missing Mushrooms and Bacon. Since it is already cooked now is there a room to correct it? Ok let's make it fresh again ... Is it worth the cost? Is it worth the time? What if there was someone who was constantly checking and validating makings of pizza with customers order while entire pasta was being made.
This early entry of QA in Software Making process marked the beginning of a new era where QA's responsibility is not to find bugs but to prevent it. Since finding bugs and fixing it is costly and time-consuming process teams are now focused more on preventing bugs at all. So if someone asks me what do you do I answer I am QA and my first responsibility is to prevent bugs.
Those ways QA is not just tasting pizza but actually contributing to the process of creating pasta that will be appropriate for its customers.
How do I do that?
Am I an astrologer for codes who knows this particular part of code likely have bugs?
We will answer these questions in upcoming post.
No comments:
Post a Comment