Entries Tagged 'Testing Concepts' ↓

How to Perform Software Product Testing – Detailed Process and Methods with Examples

Software Products need their own unique approach to test adequately and correctly. Often times, teams treat them as any other software (i.e. internal applications built for a specific client or team; not accessible by the general public; non-revenue generating) and that is the starting point of trouble.

------------

Software Product Testing needs a custom test style and strategy to add value. Software Product development and sustenance is in itself a complex ecosystem and to thrive testers need to adapt. Continue reading →

Understanding The Difference Between Unit, Integration and Functional Testing

For any software application, both Unit testing and Integration testing are very important as they each employ unique processes to test the software application. But one or both of them cannot replace Functional testing.

In this article, we will understand Unit, Integration, and Functional testing and clarify the differences between these forms/levels of testing.

Continue reading →

Mutation Testing: Testing Technique with a Simple Example

Sci-Fi fans: Don’t get your hopes up. This isn’t that kind of mutation we are talking about :)

What is Mutation Testing?

Mutation testing is a fault-based testing technique where variations of a software program are subjected to the test dataset. This is done to determine the effectiveness of the test set in isolating the deviations.

It sounds a little complicated, isn’t it?  Continue reading →

Retest Vs Regression Testing – How Much Regression Testers Should Be Doing?

Don’t you all love the compare and contrast themed articles? I know I do. It is such a great way to invite thoughts, comments and maybe even, strong disagreement.

Today’s topic is the difference between Retesting and Regression Test.

Let’s begin with Retesting:

------------

Retest means to test again. The reason does not matter. When you repeat a test, you retest. You could retest current version functionality. Or a bug fix, previous version functionality, a test case you just ran, etc.

Continue reading →

When to Stop Testing (Exit Criteria in Software Testing)

Exit criteria in Testing:

“Well begun is half done” – Applies everywhere, even software testing.

Often we see software testers very enthusiastic at the beginning of the project. We create testing documents such as Test Strategy, Test Plan or Test Cases eagerly and enthusiastically.

Then we get to testing software with a BANG! This is only amplified by the interesting defects we find at the beginning of the project. Getting them resolved will only add to our accomplishment.  Continue reading →