When a test fails, trace the successful operation before the observed failure
Logs should trace product information
Trace sufficient and helpful failure context
Avoid logging unnecessary information
Each test point should record a result when a result has been verified or validated
Follow team standards on naming
Friday, September 11, 2009
Monday, August 10, 2009
“It’s not a bug, it’s a feature”
At some point in a tester’s life, they have had to come across this statement.
One day, I spent hours arguing with a developer about a “by design” bug. I thought his “resolution” was more a result of laziness and an uncaring attitude. Eventually, I think we both gave up and decided to go home for the night. I was walking through the parking lot trying to remember where I parked ( happens frequently after long days at work) and couldn’t help but laugh when I saw an old Volkswagen Beetle(or “Bug”) parked in one of the stalls. The car was mostly navy blue but had a yellow cover on the engine with a vanity plate centered on it. The vanity plate read “FEATURE”!!! Go figure…
One day, I spent hours arguing with a developer about a “by design” bug. I thought his “resolution” was more a result of laziness and an uncaring attitude. Eventually, I think we both gave up and decided to go home for the night. I was walking through the parking lot trying to remember where I parked ( happens frequently after long days at work) and couldn’t help but laugh when I saw an old Volkswagen Beetle(or “Bug”) parked in one of the stalls. The car was mostly navy blue but had a yellow cover on the engine with a vanity plate centered on it. The vanity plate read “FEATURE”!!! Go figure…
Tuesday, July 21, 2009
A Bug's Life
A Bug’s Life:
A software bug begins its “life” as code or some other artifact of the development process. No one might know the bug really exists until the code or design is excercised by someone, usually a customer, developer or tester
Anatomy of a Bug Report
Ttile
Description
Status
Version Number
Feature Area
Reproduction Steps
Assignment
Severity
Customer Impact
Environment
Resolution
A software bug begins its “life” as code or some other artifact of the development process. No one might know the bug really exists until the code or design is excercised by someone, usually a customer, developer or tester
Anatomy of a Bug Report
Ttile
Description
Status
Version Number
Feature Area
Reproduction Steps
Assignment
Severity
Customer Impact
Environment
Resolution
Thursday, July 9, 2009
How we test Software at Microsoft
I recently picked up this book called "How we test software at Microsoft". I think every qa person should have 1 copy. It has rich resources, tons of information, different methodologies, baseline studies and tests, case studies and much more.
One amusing fact it talks about is being in a situation where the bugs "wont fix" meaning that a fix was not planned for the current or future release. The reason for these resolutions was simple: The code was "too scary to touch" and apparently the original developer had left the company years earlier. The code was so complex and difficult to comprehend that not a single developer was comfortable fixing bugs for fear that he or she would cause a dozen other failures - Now we all know this doesn’t happen to us "regular" people does it ??
Anytime simplicity isn't a part of the initial design and implementation of the software, there is potential for the code to grow into a nonmaintainable mess. I believe, proper QA Analysts should be involved at the start of the SDLC to ensure to keep it simple. A professor once introduced the term "KISS" - Keep It Simple Stupid :)
The book talks about using Metrics for evaluation and testing. One such metric is Halstead Metrics:
Halstead metrics are an entirely different complexity metric based on 4 measurements of syntax elements in a program:
Number of unique operators
Number of unique operands
Total occurrences of operators
Total occurrences of operands
Eg. To measure the code length. Halstead metics has an formula – (n1/n2) * (N1/N2)
Model-Based Testing Tools at Microsoft
Spec explorer – One powerful tool used for model=based testing at Micosoft. This was created in 2002. It can do impressive analysis and transformation of the model program that generates FSMs(Finite State Machines)
Spec explorer for Visual Studio – 3rd generation spec explorer
One amusing fact it talks about is being in a situation where the bugs "wont fix" meaning that a fix was not planned for the current or future release. The reason for these resolutions was simple: The code was "too scary to touch" and apparently the original developer had left the company years earlier. The code was so complex and difficult to comprehend that not a single developer was comfortable fixing bugs for fear that he or she would cause a dozen other failures - Now we all know this doesn’t happen to us "regular" people does it ??
Anytime simplicity isn't a part of the initial design and implementation of the software, there is potential for the code to grow into a nonmaintainable mess. I believe, proper QA Analysts should be involved at the start of the SDLC to ensure to keep it simple. A professor once introduced the term "KISS" - Keep It Simple Stupid :)
The book talks about using Metrics for evaluation and testing. One such metric is Halstead Metrics:
Halstead metrics are an entirely different complexity metric based on 4 measurements of syntax elements in a program:
Number of unique operators
Number of unique operands
Total occurrences of operators
Total occurrences of operands
Eg. To measure the code length. Halstead metics has an formula – (n1/n2) * (N1/N2)
Model-Based Testing Tools at Microsoft
Spec explorer – One powerful tool used for model=based testing at Micosoft. This was created in 2002. It can do impressive analysis and transformation of the model program that generates FSMs(Finite State Machines)
Spec explorer for Visual Studio – 3rd generation spec explorer
Tuesday, May 5, 2009
CSQA Certification Exam
I finally gave my certification exam. I had studied for it for two months. Read it 6 times. Even though I read it so many times, I was still not confident about sitting for the exam. In order to take the CSQA exam, you really do have to know the CBOK thoroughly. A lot of people have asked me what are the major differences in CSQA and CSTE?
Simple answer:
CSTE: Associated to testing, For Testers
CSQA: Associated to processes, improving processes in quality, For Quality Assurance Analysts
There is a difference between QA and QC. These terms are interchangeably used, but shouldn’t. QC has to do with testing. Testers usually use tools, automated scripts to test their data or application. QA is one step above QC, so this is more into a Lead or Management role, but not always though. Most companies can’t afford to have both so they use the same workforce (people) to do both QA and QC. But essentially, QA is a higher level position. In this role, the QA Analyst, thinks of improving the testing process. They do this by using metrics and objective data to reach a consensus. So really, CSTE is for people who want to just stick with testing, and nothing else. It’s a good foundation for the CSQA exam. But CSQA is for people who know testing but want to advance more and take a bigger role in the processes that are involved with testing. Of course, there is more associated to these things but the above explanation is just a simple one. I have taken a look at both the CSTE and the CSQA. I would say that I found it similar but with CSTE testing methodologies are explained more in depth.
SO I decided to go for CSQA as that is where my interest lied. I took the exam two days ago, it consisted of 4 sections: 1st section: 50 multiple choice 2nd section: 10 essay questions 3rd section: 50 multiple choice 4rth section: 10 essay questions Don’t be alarmed at the essay questions. Examiners know that you have only 5-7 mins to write the answers. Write everything in a point format, a systematic approach should be used. You don’t need to really write an "essay". A brief definition,a brief explanation,and an example should be just enough. Always remember to READ the questions as it has two parts to it (most of the time), so be careful of writing the first part and missing the second part out.
Simple answer:
CSTE: Associated to testing, For Testers
CSQA: Associated to processes, improving processes in quality, For Quality Assurance Analysts
There is a difference between QA and QC. These terms are interchangeably used, but shouldn’t. QC has to do with testing. Testers usually use tools, automated scripts to test their data or application. QA is one step above QC, so this is more into a Lead or Management role, but not always though. Most companies can’t afford to have both so they use the same workforce (people) to do both QA and QC. But essentially, QA is a higher level position. In this role, the QA Analyst, thinks of improving the testing process. They do this by using metrics and objective data to reach a consensus. So really, CSTE is for people who want to just stick with testing, and nothing else. It’s a good foundation for the CSQA exam. But CSQA is for people who know testing but want to advance more and take a bigger role in the processes that are involved with testing. Of course, there is more associated to these things but the above explanation is just a simple one. I have taken a look at both the CSTE and the CSQA. I would say that I found it similar but with CSTE testing methodologies are explained more in depth.
SO I decided to go for CSQA as that is where my interest lied. I took the exam two days ago, it consisted of 4 sections: 1st section: 50 multiple choice 2nd section: 10 essay questions 3rd section: 50 multiple choice 4rth section: 10 essay questions Don’t be alarmed at the essay questions. Examiners know that you have only 5-7 mins to write the answers. Write everything in a point format, a systematic approach should be used. You don’t need to really write an "essay". A brief definition,a brief explanation,and an example should be just enough. Always remember to READ the questions as it has two parts to it (most of the time), so be careful of writing the first part and missing the second part out.
Friday, March 6, 2009
Everything QA
So far, in my life, I have dedicated every being of myself to QA. I have decided that someday I will be testing software in Microsoft. Now whether that will happen or not, we will just have to wait and see. But untill then, I want to gain every knowledge, skills imaginable that will help me get my foot in the door. Even if I dont get in the "Worlds best Software Company", I will atleast have formed a deep meaningful relationship with QA. SO I have decided to call this phase in my life "Everything QA". I am currently studying for the CSQA certification. Let me tell you this is no child's play. I dont know if its just me being out of the college mode and having a bit of a difficult time, getting back into this mode, but this exam is quite extensive. You have to buy the BIG FAT book called The common body of knowledge. For those of you who want a copy of it, its attached on this blog. But bear in mind, it is advisable for you to buy this book from QAI. Note: Please buy the book. Please dont ask them for an extra copy.
In June 09, the CBOK is scheduled to change and have a new version with extra information and a few things shaved off from the current version. Its advisable to take the CSQA exam as soon as possible, as it will change. Which results in, you buying the current version of the book and studying it again to take the exam. Note: The CBOK WILL BE CHANGING THIS YEAR. SO its advisable to take the CSQA exam as soon as possible.
I had also taken the ISTQB exam. I would not say its similar to the CSTE, but if you are looking at a faster route, then ISTQB is the way to go. But I feel one of the best certifications to get is that offered by QAI. They are known worldwide and recognized as well. ISTQB is too, but it really is for people who are beginners in testing. Its a good foundation to start and prepare taking other certifications. I had gone to a testing conference once, and the speaker said " It really matters how many "letters" you have after your name" True enough!! Although I am not saying that everyone should and would have a Phd. but it does matter if you have known certifications behind your name. Couple that with a Masters or a Phd. you become "dangerous" you become unique.
QAI has started to offer CSBA, which starts from ground up. You do not need to have previous BA experience to sit for this certification exam. You can find more about this certification on http://www.qaiworldwide.org/qai.html
In June 09, the CBOK is scheduled to change and have a new version with extra information and a few things shaved off from the current version. Its advisable to take the CSQA exam as soon as possible, as it will change. Which results in, you buying the current version of the book and studying it again to take the exam. Note: The CBOK WILL BE CHANGING THIS YEAR. SO its advisable to take the CSQA exam as soon as possible.
I had also taken the ISTQB exam. I would not say its similar to the CSTE, but if you are looking at a faster route, then ISTQB is the way to go. But I feel one of the best certifications to get is that offered by QAI. They are known worldwide and recognized as well. ISTQB is too, but it really is for people who are beginners in testing. Its a good foundation to start and prepare taking other certifications. I had gone to a testing conference once, and the speaker said " It really matters how many "letters" you have after your name" True enough!! Although I am not saying that everyone should and would have a Phd. but it does matter if you have known certifications behind your name. Couple that with a Masters or a Phd. you become "dangerous" you become unique.
QAI has started to offer CSBA, which starts from ground up. You do not need to have previous BA experience to sit for this certification exam. You can find more about this certification on http://www.qaiworldwide.org/qai.html
Tuesday, January 6, 2009
New to QA
I decided to write a blog on QA. I recently just started QA. It kinda fell into my lap. I work as a Technical Coordinator at a Company. The QA department were running short on workforce so they asked the Opertaions Department to help out. And thats when I met my love QA. I thoroughly enjoyed learning and performing it. Being new at the QA game I decided to surround myself with books and people in the industry in order to learn as much as I can about the facinating line. This blog was created to record my learnings and the experiences I have or will have in QA.I have been reading a book called Software Testing Foundations. I am going to take the Software Foundation Certification. I want to be certified in this field. If you are new at QA and are seriously interested in learning about it and pursuing it as a career. I suggest getting certified. You do not have to be completly technical but if you are its a BIG plus. Start joining forums and blogs and sign up with websites on QA like mine. Leave comments and ask lots and lots of questions. I have realized that no question is stupid when you are new to a field. There are people out there just like me who would thrive on getting questions and researching them for answers. There are a couple of QA user groups meetings and you should be on the watch out for one in your location. For starterd the AQAA society is great for QA. Check them out: http://www.aqaa.org/ They have tons of resources and the board members work in the industry as well. They are all certified QA Engineers who offer plenty of Knoweledge. I am a member. The membership fee is 60.00 dollars for the entire year. They also offer classes in order to help you prepare for a certification. I learned that when you start out in QA and are interested in being certified, you can take the Software Foundation Testing Certification. Its a basic certification. Level 1. To start out you can get this and then move up. There are basically three kinds of certification. There are others too but these are the ones that you can start off doing and then move on to other ones. I have not done any extensive research on other certifications but this one is quite interesting. The first level is the software foundation certification and in this you are just tested on the terms and the know hows of testing. Nothing big and i think anyone starting out should get this done. In order to have a firm understanding of all the terms and processes its a good test to give. Books that can help you in this are: Software Testing Foundations 2nd edition by Andreas Spillner, Tilo Linz and hans Schaefer, Software Testing 2nd edition by Ron Patton.They can be found on Amazon or any other book store. I found Amazon cheaper.There are other great books too but these are the ones that helped me. There are also some institutes that offer preparation classes for these certifications and at the end of the class help you to take the test. The fee for taking the test is also covered by them and is included in the course fee. ASPE Technology, http://www.learningtree.com/ are some good institutes. The cost usually is 1995 which includes course material and the cost of taking the certification test.
Subscribe to:
Posts (Atom)