Software Testing, QA

Posts tagged ‘tips’

Testing of the installation

1. We get a list of files from the installation package builder. We need to get a list of files before, and the file list checking is performed after the installation. We can also hear the phrase: “Make a list after the installation, everything is true there” – this is a provocation! Do not give in!

Another point: the same installation package can install different file sets under different operating systems, i.e., we perform testing for each operating system separately.

Read the rest of this entry »


Test Summary Report + Template

In this article I’ll discuss the first step for ensuring of transparency between testing department and customer.
It is best to build the relationship in such a way that the customer sees what is happening and what he pays money for. Over time, if our relationship is transparent and we continue working with this person, this relationship is improving. This person begins trusting more and more.

Rule: Quality work + Full transparency of what is happening in the sum gives us confidence of the customer.

Read the rest of this entry »

How to create a good bug report

example of bug report

The template of the bug report depends on the bug tracking system you use. Usually the bug report should contain the following fields:

  • unique identifier
  • build version
  • summary
  • description
  • step to reproduction
  • reproduction (always, sometimes)
  • severity
  • priority
  • symptom

As soon as a bug has been found, it must be reported because you can forget about the bug. Do not prepare the report on a paper (you can lose it) and log the report to the bug tracking system. These are simple rules but many testers neglect them and many bugs have been left unfixed.

Read the rest of this entry »

8 Tips For Effective Testing

1. Tests should always have a priority. The priority of test is defined by importance of the feature and probability of error emergence (which is determined empirically, on the basis of communication with developers, functional changes etc.)
2. You should always document the priority of functionalities, coordinate it with PMs and analysts. You don’t need to spend much time on features that nobody uses.
3. If there are tasks with different priority levels, you should always check the task with a higher priority (if it is possible, and if tasks are independent).

Read the rest of this entry »