How do QA write test cases in IT companies?
As a test person or QA you may encounter this job task sooner or later in your glittering test career :)
All glitter is not always gold ;) But do QA cares about the gold? Naaa.....
What he/she got in return is a heavy push to do QA fast in less time rather than gain some thing for the whole QA process. This is irony of QA field :(
Anyway, it look I am deviating from my blog title.....may be this was long weekend movie side effects ;)
So, how do we create test cases in general in any IT company, do we generally follow or allow to follow a proper test plans or any use case documents.
In general this is not a hard core QA practice. I am confirm that after this comment I am going to get a hard commenting for those who actually follow the all QA driven processes. I wish all QA have the same fate like them, to make QA life more interesting and thrilling.
So, here is how a TC creation process, I am trying to show in most general, don't take my view as all IT QA view, its just an simple individual opinion. Open mind view point required to go through this theory :P
In real a QA get some technical documents, which are most of time way ahead to his/her understanding and also his so called T.L or T.M grey matter range ;P, and these QA souls need to build a secure and bug free, gaussian test castle around the product, so that every stakeholders feel good a bout the product :D
A simple .xls sheet a word document and few more technical code snippets and more tech. jargons........
And now the TC writing process started, there is one thing is fixed and very clear and each team member know about it, its named as 'dead-line' to finished the TC............
disclaimer notice: Open to re-use and plagiarism :)
As a test person or QA you may encounter this job task sooner or later in your glittering test career :)
All glitter is not always gold ;) But do QA cares about the gold? Naaa.....
What he/she got in return is a heavy push to do QA fast in less time rather than gain some thing for the whole QA process. This is irony of QA field :(
Anyway, it look I am deviating from my blog title.....may be this was long weekend movie side effects ;)
So, how do we create test cases in general in any IT company, do we generally follow or allow to follow a proper test plans or any use case documents.
In general this is not a hard core QA practice. I am confirm that after this comment I am going to get a hard commenting for those who actually follow the all QA driven processes. I wish all QA have the same fate like them, to make QA life more interesting and thrilling.
So, here is how a TC creation process, I am trying to show in most general, don't take my view as all IT QA view, its just an simple individual opinion. Open mind view point required to go through this theory :P
In real a QA get some technical documents, which are most of time way ahead to his/her understanding and also his so called T.L or T.M grey matter range ;P, and these QA souls need to build a secure and bug free, gaussian test castle around the product, so that every stakeholders feel good a bout the product :D
A simple .xls sheet a word document and few more technical code snippets and more tech. jargons........
And now the TC writing process started, there is one thing is fixed and very clear and each team member know about it, its named as 'dead-line' to finished the TC............
disclaimer notice: Open to re-use and plagiarism :)
