Entries Tagged 'Basics of Software testing' ↓

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 →

6 Most Important Steps to Make Your Test Reports Even Better

Before we go ahead with suggestions about how to create an effective test report, look into below reports and ask yourself, which one would you prefer when you are a decision maker or even a team member (any recipient of the report).

Report #1:

Tested following modules:

  • Module X: Login page.
  • Module Y: Home page and relevant tabs.

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 →

What To Do When There Isn’t Enough Time To Test?

Part way through your test cycle, do you often realize you do not have enough time to test? You had it all under control, to begin with, but soon you are reaching the contingency plan’s “What to do when there isn’t enough time to test?” section.

I have been there too and it is not fun. :)

I thought about this long and hard. How can something that started so well, go down so badly, so quickly. And, here is my analysis.  Continue reading →

6 Basic Skills That Every Tester (Mainly Fresher) Should Have

Software Testing or QA is the best platform for newcomers to enter into IT industry despite the misconceptions that it is a lesser or lower paid job.

The most important skill that a tester needs is the ability to find bugs.  And, if you are the sort of person who loves finding bugs, then you are going to love and grow in this field.

Having said that, there are few more skills that can help you find bugs and work with QA processes better.  Continue reading →