Entries Tagged 'Testing Concepts' ↓

What QA Tester Should Know About Release and Deployment Management Process

In our team meeting today, the manager checked with everyone on their readiness for test execution. He mentioned the “code will be ready for QA by tomorrow morning”. What did he mean when he said “code will be ready”, does it mean the developers are going to write the code in QA environment tonight?

He actually meant that the deployment is planned to be done at night and the new code will be deployed to the QA environment for testing.

Many of you may now ask, what deployment is and what do they really do in it? Continue reading →

Verification vs Validation – What’s the Difference and Why It is Important to Understand It

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:


  1. It is a fundamental QA concept, therefore is almost the building block to being QA-cognizant
  2. It is a commonly asked interview question
  3. Certification syllabi (or is it syllabuses?) have a good amount of chapters revolving around this
  4. Finally and practically – since we testers do both – we might as well be experts at this.

Continue reading →

Test Coverage in Software Testing (Tips to Maximize Testing Coverage)

Software Testing Test Coverage Complete Guide: How to Test More, Save Time, and Achieve Better Testing Results:

Software testing is an essential activity in the software development and maintenance life cycles. It is a practice often used to decide and improve software quality.

Development is more systematic nowadays and organizations seek measures of testing completeness and effectiveness to show test completion criteria. Of them all, coverage is considered especially valuable.  Continue reading →

White Box Testing: A Complete Guide with Techniques, Examples, & Tools

What is White Box Testing?

If we go by the definition, “White box testing” (also known as clear, glass box or structural testing) is a testing technique which evaluates the code and the internal structure of a program.

White box testing involves looking at the structure of the code. When you know the internal structure of a product, tests can be conducted to ensure that the internal operations performed according to the specification. And all internal components have been adequately exercised.  Continue reading →

What is Test Harness and How is it Applicable to us, Testers

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 simply 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.

What is test harness

But I stand corrected. Recently, in my class, I was teaching Agile-scrum model for software development. There was a Continue reading →

Ad-hoc Testing: How to Find Defects Without a Formal Testing Process

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 a black box or behavioural 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 →

Important Software Test Metrics and Measurements – Explained with Examples and Graphs

In software projects, it is most important to measure the quality, cost and effectiveness of the project and the processes. Without measuring these, a project can’t be completed successfully.

In today’s article, we will learn with examples and graphsSoftware 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 →

Static Testing and Dynamic Testing – Difference Between These Two Important Testing Techniques

Testing is verification and validation. We all know that it takes 2 Vs to make testing complete.

In today’s article, we will shed some light on Static testing. It is also called as Verification. We will learn all about it and pay special emphasis on this because dynamic testing often receives maximum attention and has innumerable articles detailing it out.

However, no discussion on static testing would be complete without an explanation of what its counterpart, dynamic testing means. Dynamic testing is validation, the other “V”. Dynamic testing is when you are working with the actual system (not some artifact or model that represents Continue reading →

What is Difference Between Test Plan, Test Strategy, Test Case, Test Script, Test Scenario and Test Condition?

Our popular software testing questions and answers series is back again! Just to remind – in this series we answer questions asked by the readers. You can check some earlier posts in this series here and here. Got a question? Submit it in the comment section below or use the contact form.

In today’s article in this series, we are going to answer (with examples) some most commonly asked (and confusing) questions about the difference between test plan, test strategy, test case, test script, test scenario and test condition.

These questions are asked by “sasi C“.

Continue reading →

State Transition Testing Technique and State Transition Diagram with Examples

What is State Transition Testing and State Transition Diagram? Explained with examples.

In our last article, we saw ‘Cause and effect graph’ test case writing technique. Today let’s move to next dynamic test case writing method – State transition technique.

Note – The test design techniques mentioned here may seem difficult but once you get hold of it, it becomes very easy to implement and re-use, increasing productivity and test coverage.
Continue reading →