Tips on writing bug report

Manual Test, Quality Assurance, Software testing, Technology

Why writing an effective bug report is a good skill for QA team?

In my earlier days as QA analyst, Development team often complained me about how confusing bug report I wrote.

The general complaints I received are about ambiguous description, confusing steps to reproduce, and missing visual evidence.

I felt annoyed with these complaints at the time. So I complained back to them that they should already understand the bug because they were the one who created it in the first place.

Quality metrics

Quality Assurance, Software testing, Technology


The aim of collecting quality metrics is to use the data for:

  • improving the test process,
  • learning how our team improved its efficiency and productivity, rather than to just show fancy reports.

This includes finding tangible answers to the questions:

  • How bad are the bugs?
  • How many bugs found were fixed? reopened? closed? deferred?
  • How many bugs did the test team did not find?
  • How good were the tests?
  • Was the test effort adequate? Could we have fit more testing in this release?

Good answers to these questions need measurement. This post includes metrics to answer above question.

Approaches of Software testing

Quality Assurance, Software testing, Technology

This page is a curated information from blogs, articles, tutorials about software testing that relevant to QA team.

If you are new to software testing, you can use information on this page as starting point to grow your skills on software testing.

Scripted Testing

In this approach, test engineers perform testing on the system under test with a set of prepared instructions to ensure that the system functions as expected.

A test script specifies:

  • the test operations,
  • the expected results,
  • the comparisons the human or machine should make.

The scripting process provides opportunities to achieve several key benefits: