Informatika, Quality Assurance, Software testing, Teknologi

Tips on writing bug report

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.

Continue reading

Advertisements
Standard
Quality Assurance, Software testing

Quality metrics

Overview

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.

Continue reading

Standard
Informatika, Quality Assurance, Software testing, Teknologi

Approaches of Software testing

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:

Continue reading

Standard
Quality Assurance

5 principles of quality assurance team member

During my time as QA Analyst, I found these 5 principles helped me a lot to succeed as QA team member:

1. Be a team player

Focus on team’s goals

We can see it in most sports. There are no team sports in which one player does it all.

You may have done a stellar job on the part of a job you were responsible for, but that matters very little if the overall project fails to achieve the target.

Instead, think about it this way. The team is your boat. If your boat is sinking and you can do something, just do it. Hence, you need to put in what’s needed to keep the boat together.

Help others to succeed

Continue reading

Standard
Informatika, Quality Assurance, Software testing, Teknologi

Types of software testing

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.

Overview

There are several well-known types of Software testing. Here are 4 types of testing I use frequently:

1. Regression Testing

Regression testing is a type of software testing that seeks to uncover new software bugs, or regressions, in existing functional and non-functional areas of a system after changes such as enhancements, patches or configuration changes, have been made to them.

Who performs it: Developer, Tester
When: Testing per build (Staging)

Continue reading

Standard
Informatika, Quality Assurance, Software testing, Teknologi

Methods of Software Testing

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.

Overview

These methods are used to describe the point of view that a test engineer takes when designing test cases.

White-box

White-box testing technique is used to examine the program structure and business logic, it validates the code or program of an application. It is also called as Clear-Box Testing, Glass-Box Testing or Open-Box Testing.

Continue reading

Standard