Quality MattersBlog - The art of Software QA and Testing |
|||||||||||||||||||||||||||||||||||||||||||
Sympathetic TestingRecently, I came across this interesting term in James Bach and Ajay Balamurugadas' blog. Instead of testing for bugs, Sympathetic Testing's goal is to focus on "learning" the product and its features. In fact, I'm sure that all of us already apply sympathetic testing to some degree without knowing it. Differences between Quality Assurance and Quality Control This is one of the most frequently asked question by students and professionals around the software QA industry as well as during the interview. You can find many version of the definition between these two on the internet. Similar to my very first post, I'll give you the definition that I found the most appropriate: Software Quality Control is the set of procedures used by organizations to ensure that a software product will meet its quality goals at the best value to the customer, and to continually improve the organization’s ability to produce software products in the future. [Source: Wikipedia: http://en.wikipedia.org/wiki/Software_quality_control] Software quality assurance (SQA) consists of a means of monitoring the software engineering processes and methods used to ensure quality. The methods by which this is accomplished are many and varied, and may include ensuring conformance to one or more standards, such as ISO 9000 or a model such as CMMI. [Source; Wikipedia: http://en.wikipedia.org/wiki/Software_quality_assurance] "Product" and "Process" are the keywords that distinguish the differences between QA and QC. Quality Control is "Product-oriented", it focus on the "product" itself, whether it meet its quality goals and user requirements. E.g: Testing, Review and Inspection fall into this category. On the other hand, Quality Assurance is "Process-oriented"; focus on whether the process element of a project is conforming to standards and methodologies. Since QA focus more on the whole project, hence it can have a supervision on quality control. Tips for passing the ISTQB Foundation Level exam - Do's and Don't's![]() Last week, I passed my ISTQB-Foundation level exam with an excellent grade. I would like to share the methods I used and some helpful self studying tips. Keep in mind that the more you know the Syllabus the better you do on the exam. Rule #1: DO NOT take the words of those who claimed anyone can pass by cramming for two days right before the exam. Even an experience tester may be caught off guard by this exam because they may have different opinions or views on some materials. You are strongly encouraged to study the Syllabus thoroughly before even attempting the exam. Rule #2: DO NOT practice sample exam papers from online sources! There are many sample exam questions online and I suggest NOT to do any of them as there are many INCORRECT solutions. Moreover, some questions are misleading since they do not even follow the ISTQB Syllabus. Rule #3: DO buy a textbook. I recommend Foundations Software Testing by Graham, Veenendaal, Evans, Black Not only it covers all the materials from the foundation level syllabus but also includes sample exam questions at the end of each chapter. In addition, it also includes a mock exam at the end of the book. The latest version of this textbook is 2007, but it still covers the 2011 syllabus very well. Rule #4: I would suggest this textbook if you need additional sample exam questions,: Sample Exam Questions: ISTQB Certified Tester Foundation Level by Estrella, Estrella. They are more difficult than the actual exam but it further enhances your overall knowledge on the subject. Rule #5. DO REMEMBER, you WILL NOT be able to find the actual exam questions online or even from the sample exam questions above. Actual exam questions are highly confidential and ISTQB does not disclose to the public. Therefore, you need to STUDY THOROUGHLY the materials by going through the syllabus, textbooks and online tutorials . The sample questions are used to measure your level of understanding and your progress. DO NOT Blindly memorize multiple choices questions and answers. What is Quality?![]() What is Quality? (Software Quality) Different people have different opinions about this term. Let's explore the definition that I found the most appropriate: From ISTQB (IEEE 610 standard): Quality: The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations. The term "requirement" should include both explicit and implicit requirements. Explicit requirements are those that are clearly documented. Implicit requirements are those that customers assume or expect to be fulfilled but not explicitly specified on any document. However, do not underestimate the importance of the "implicit" part of the requirements. Failure to meet implicit requirement may lead to unsatisfied customers which means deteriorating software quality. The definition of "good quality" is simply satisfying users or customers' explicit and implicit requirements. |
About MeMy Profile Archives Friends My Photo Album
LinksASTWeekend Testing Software Testing Club SQAForums James Bach's Blog CategoriesSoftware TestingAutomation Recent EntriesMoved...Installing Maven + Selenium WebDriver Sympathetic Testing Differences between Quality Assurance and Quality Control Tips for passing the ISTQB Foundation Level exam - Do's and Don't's Friends |
||||||||||||||||||||||||||||||||||||||||||