HP ALM Synchronizer Defect Management Tool Hands-On Tutorial

HP ALM Synchronizer

Overview of HP ALM Synchronizer:

HP ALM Synchronizer seems to be a very new term for most of us and several questions surround us when we first see or hear to this term.

Usually, when we come across a new term, we will start doing a Google search to find out the details about what it is.When we do a search for this term, unfortunately not many results can be found except some installation guides, images, few descriptive details etc.


Read moreHP ALM Synchronizer Defect Management Tool Hands-On Tutorial

Backlog Bug Tracking Tool Hands-on Review Tutorial

Backlog Bug Tracking Tool

Discovering, recording, and tracking bugs are important parts of the software development process. Luckily, bug and issue tracking tools can streamline the process, make it easy for teams to prioritize, assign, and fix bugs efficiently.

Many free online tools can capture and track bugs, but working with a single-purpose tool always has its drawbacks. One of the most obvious is the fact that bug tracking becomes siloed from the rest of a team’s work. For this reason, many teams have turned to more comprehensive solutions that help them manage the end-to-end development of projects.


Read moreBacklog Bug Tracking Tool Hands-on Review Tutorial

Defect Prevention Methods and Techniques

Defect Prevention methods

Effective Defect Prevention Approach and the Critical Views:

Quality Assurance is the term that is commonly used to address the testing teams in IT projects.

Technicalities aside, Quality assurance activities are not just targeted at defect identification (which is finding defects after they have happened. This simply is testing or Quality control) but also include defect prevention (making sure the defects do not happen in the first place or the defects are removed/reduced before making their way into the software product).

Read moreDefect Prevention Methods and Techniques

Mantis Bug Tracker Tutorial: MantisBT Issue Tracker Complete Guide

Mantis

MantisBT open source free popular bug tracking system tutorial:

Testing is an integral part of any software development life cycle. The software bug is an error in a software application which causes software to produce incorrect results. Therefore, causing deviation in the expected, and actual outcome.

A bug tracking software is a software application used to maintain records of software bugs reported during the software development life cycle.

Read moreMantis Bug Tracker Tutorial: MantisBT Issue Tracker Complete Guide

JIRA Bug Tracking Tool Tutorial: How to Use JIRA as a Ticketing Tool

JIRA Bug Tracking Tool

The test teams are always apprehensive about picking up JIRA for defect Management.

The doubt is warranted. It stems from the fact that, though JIRA bug tracking tool is applicable to IT businesses it is a generic ticketing system.

Even for IT projects, JIRA’s popularity with the Development teams makes testers and QA teams uncomfortable. Despite the comfort or discomfort, the test teams have no choice but to use JIRA bug tracking tool in most companies. 

Read moreJIRA Bug Tracking Tool Tutorial: How to Use JIRA as a Ticketing Tool

3 Worst Defect Reporting Habits and How to Break Them

worst-defect-reporting-habits

Defects are serious business and small mistakes can be expensive.

You know what to do when you find a defect. You report it; either in a Defect Tracker/Defect Management tool or in an Excel sheet. The underlying principles are the same for both methods.

Defect Management tools don’t guarantee better reporting. It is good practices that save the day.

Read more3 Worst Defect Reporting Habits and How to Break Them

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

software-go-live-criteria

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. 

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

A Step by Step Guide to IBM Rational ClearQuest Tool

IBM Rational ClearQuest Software Guide

For each and every project, as per the Client’s requirement and ease, various tools are recommended and used.

For example, few projects prefer ‘Quality Center’ for managing the project’s data whereas few others prefer Rational ClearQuest tool.

Rational ClearQuest is a defect management and workflow automation software from IBM Rational software division. 

Read moreA Step by Step Guide to IBM Rational ClearQuest Tool

7 Types of Software Errors That Every Tester Should Know

categories of software errors

It’s time again for a post on software testing basics. This post is on types of software errors that every testers should know.

Software bugs are of many types. A bug is a bug no matter what. But sometimes, it is important to understand the nature, its implications and the cause to process it better.

This helps for faster reaction and most importantly, appropriate reaction.

In this article, we will be discussing common kinds of software errors and how to identify them during testing with some examples and simple exercises.

Let us start by defining software error and bugs.

Read more7 Types of Software Errors That Every Tester Should Know

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

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

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