Entries Tagged 'Testing best practices' ↓

How to Maximize Test Coverage in Less Time and Achieve Better Testing Results

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.

Simply put, coverage is “What are we testing and How much are we testing?”  Continue reading →

4 Mistakes of My Life as a Software Tester (and You’re Probably Making These)

We all heard the story of the little frogs in the well who thought the world is the well until they came out and realized how big, beautiful and different it is!

Do you think you have lived this story at some point in your professional life? Well, everyone has. Welcome to the world of reality – beautiful testing :).

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

Today, I want to share 4 mistakes I made when I started my software testing career. You’re Probably Making These. Check out.  Continue reading →

Top 10 Challenges Testers Face at Workplace and How to Overcome Them

Challenges are normal. It is when you look at them as opportunities, a gold mine and as obstacles, a land mine. I have had my share of ‘opportunities’ over the years in the IT industry.

Some came with the role I was playing, some general. This is my attempt to record them and to reach out to the community to see if any of those resonate with you and maybe, in a small capacity help you and let you know that you are not alone.

Here’s my top 10 list:

Continue reading →




What is Technical Debt and Why QA Testers Should be Concerned About It?

Technical debt is a metaphorical idea which argues that just as one may run into debt problems in finance, software organizations encounter something similar in the buildup of unfinished work during past projects and version releases/sprints.

What is Technical debt?

It represents the effort needed to fix the issues/defects that remain in the code when an application is released. In simple words – it’s the difference (in terms of bugs) between what is expected and what is delivered.

When a development team is busy working on a project and fixing bugs unfortunately, many new bugs appear. Out of Continue reading →

This Scenario Explains How Important It is to Document the Frequently Encountered Errors

Do you believe that software errors occur only once and that on being fixed they never resurface? I feel that about 30% of the errors reoccur.

In this article, I want to cover how important it is to document some of the frequently encountered errors.

Below, you will find some common areas where issues are seen and a template to document them.  Continue reading →

How to Improve Software Quality Using Continuous Integration Process

In the first part of the article series, we understood the nuances of Continuous Delivery (CD) where we have production ready software at any point via continuous feedback loops. Continuous integration (CI) is the real meat behind the CD process and is the reason that makes Continuous Delivery possible.

To understand CI, let’s take the terms at face value and deduce a basic definition. The first word means “ongoing” or “frequent” and the second “merged” or “made part of”. So CI is a process where something is being “merged”-“frequently”.

Logically the next question is: What is the something being merged and where is it merged?

Continue reading →