Entries Tagged 'Basics of Software testing' ↓

7-Step Practical Implementation of Manual Testing Before Production Release

In the previous post of this series around Manual Testing, I tried to throw as much light as possible on the basics of Manual Testing.

If you missed it, you can read it here.

I hope it was successful in taking you as close as possible to the answers you were looking for.

In that case, wouldn’t you love to know more about the practical implementation of Manual Testing, how to get more familiar with it and how to actually start a career in it?  Continue reading →

Manual Testing Tutorials for ALL the Testers: Getting the Basics Right

We will be covering different aspects of manual testing through this series of manual testing tutorials for beginners as well as experienced professionals.

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

Well, what does the word ‘Manual Testing’ tell you? Any testing which you do manually right? Though it be manual functional testing or measuring the response time of a web page manually or a security test which you perform manually. Same is not the case with our Testing industry. :)  Continue reading →

Component Testing (or Module Testing) Explained with a Simple Example

A component is the lowest unit of any application. So Component testing; as the name suggest, is a technique of testing the lowest or the smallest unit of any application.

Component testing sometimes is also referred as Program or Module Testing.

An application can be thought of a combination and integration of many small individual modules. Before we test the entire system as a whole, it is imperial that each and every component OR the smallest unit of the application is tested thoroughly.

Continue reading →

How Do You Decide Which Defects are Acceptable for the Software to Go-live?

Software Go-Live is always a big event for any software product. It is important to absolutely make sure that everything works and that we are releasing quality software to the users.

A bad or premature or unstable or difficult to use product can cause a lot of losses financially and could also make the user lose trust in the brand itself.

Often times, we hear that testing should be done until we meet the exit criteria. We also hear that defects have to be fixed to an acceptable level.  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 →