Entries Tagged 'Testing Concepts' ↓
September 9th, 2015 — Basics of Software testing, Testing Concepts, Testing Interview questions
It’s back to the basics folks! A classic at that – Verification Vs. Validation.
The following are some of the reasons why it is very important to understand the difference between Verification and Validation:
- It is a fundamental QA concept, therefore is almost the building block to being QA-cognizant
- It is a commonly asked interview question
- Certification syllabi (or is it syllabuses?) have a good amount of chapters revolving around this
- Finally and practically – since we testers do both – we might as well be experts at this.
Continue reading →
September 3rd, 2015 — Basics of Software testing, Testing best practices, Testing Concepts
Scene 8 years ago: when I was having 2 years of experience in software testing industry I was thinking that it was alright if I don’t know some fundamentals about software testing as something one can learn with experience and me too will do.
I was right – and wrong as well.
Right because with experience, you learn to see bigger picture, you understand real meaning of “Critical Situation” and you understand the end user more. Wrong because none of the mentioned things require experience, but early learning, which I understood very late. That is the encouraging factor to write this post. Continue reading →
February 2nd, 2015 — Testing Concepts, Testing Methodologies, Types of testing
Understanding White Box Testing with a Simple Example
In my career so far, I have seen the testers to be the most enthusiastic community in the software industry.
The reason being, that testers always have something in their scope to learn. Be it domain, process or technology, a tester can have a holistic development if they wish to.
Continue reading →
January 7th, 2015 — Testing Concepts, Testing Methodologies
I am not a big fan of labels. Here is what I mean by that.
If I have to check few aspects before I determine whether or not QA can be started, I will simple make a list and perform the action. In my opinion, it does not matter if I officially call it a “Test readiness review” operation or not – as long as I am doing what I am supposed to do, I think there is no need to call it a specific name or label.
But I stand corrected. Recently, in my class I was teaching Agile-scrum model for software development. There was a Continue reading →
September 29th, 2014 — Testing Concepts, Types of testing
The very term ad-hoc implies the lack of structure or something that is not methodical. When you talk about ad-hoc testing, it means that it is a form of black box or behavioral testing performed without any formal process in place.
The formal process here means having the documentation like requirement documents, test plan, test cases and proper test planning in terms of its schedule and order of performed tests. Also any actions performed during the testing are not typically documented. Continue reading →
September 11th, 2014 — Bug Defect tracking, Testing Concepts
In software projects, it is most important to measure the quality, cost and effectiveness of the project and the processes. Without measuring these, project can’t be completed successfully.
In today’s article we will learn with examples and graphs – Software test metrics and measurements and how to use these in software testing process.
There is a famous statement: “We can’t control things which we can’t measure”.
Here controlling the projects means, how a project manager/lead can identify the deviations from the test plan ASAP in order to react in the Continue reading →