Software Testing, QA

Archive for October, 2011

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 »

Usability Testing

Introduction

Concept of usability testing
First of all, I would like to say that I don’t consider myself to be an expert in usability testing and user interface design. But I want to share my knowledge and quite unpretending experience in these areas with others. That is why I’ve decided to write a series of articles about usability and usability testing. Maybe, somebody (or many) of you already know this information.

At the beginning I’ll tell you about history of usability, guidelines and standards of usability, definition and components of the concept of usability.So, let’s start.

What is usability?

Nowadays the software market is sated enough. A certain task can be solved by means of tens competing programs with almost identical functionality. Finally, the choice of this or that application more and more depends on nonfunctional characteristics. The user interface which provides simplicity and overall performance with a software product, can be of primary importance for making such a decision.

Read the rest of this entry »

 

Selenium: An Introduction

What is Selenium?

Selenium is a suite of tools for browser automation.

There are four Selenium tools:

  • Selenium IDE
  • Selenium RC
  • Selenium WebDriver
  • Selenium Grid

Each tool has a specific role.Let’s look at them…
Read the rest of this entry »

Peculiarities of mobile applications testing

Mobile applications are appreciably different from PC applications. There are constructive features of mobile devices and diversity of mobile platforms. Everything listed above is important for testing. In this article I’ll tell you about a few points you should pay attention to. Some of them I found in UTC for Android application and you can also discover many useful things there.

Firstly, we usually test installation of an application. The application can be installed on phone memory and on memory card if the device supports such cards. The application should be installed correctly on all appropriate devices and we have to check that the application should not be installed on unsuitable devices (unsuitable OS). If you have tested the installation, check surely the uninstall, too. The application should be removed completely from phone memory and memory cards.

Read the rest of this entry »

Follow

Get every new post delivered to your Inbox.

Join 60 other followers