Category - Testing

The Best Practices in Organization of QA Process for a Software Development Project (Part II)

Our previous article described how to build a template for a testing round and what and why we need for that. But such template is just a tool and it is useless when not used correctly. So let’s drill down into QA process and its procedures we are using to let the testing be flowing fast and easily. Below, we are going to share the detailed instructions as well as some QA process improvement ideas.
Read More

The Best Practices in Organization of QA Process for a Software Development Project

This article describes our best practices in building the QA process for a software development project. What are our main goals in it?

Fast and featureful

First, the delivery of new software versions to end users as fast as possible is vital for software development nowadays. Fierce competition in the software market compels software companies to release new features sooner than their rivals to attract users. As a result, the Agile techniques have spread widely as they combine flexibility and short delivery cycles.
Read More

Benchmarking: Best Practice For Code Optimization

For most developers performance testing sounds like something really difficult to get started on. It might come to mind that some special and usually expensive environment and tools to test the performance.

Well, sometimes you do indeed need them to test the network communications impact, or if you have a cluster and want to measure its capacity, for example. But if you have some small system or you don’t have a lot of money, you may still face performance problems. Sometimes you can’t scale the environment, because it is expensive or your code has bugs preventing it from scaling.
Read More

How to Make Performance Testing More Efficient

Performance testing is a type of testing proceess to determine the responsiveness, throughput, reliability and scalability of a system, it has under a certain load. The goal of the performance testing is one of the listed below:

  1. To assess readiness of the system for the production release,
  2. To evaluate performance of the system against some baselines,
  3. To find the best configuration settings of the system,
  4. To find the source of performance,
  5. To determine throughput levels.

Read More

Automated Tests: Why and How

If you aren’t implementing a prototype for some quick demo in some 8 hours, 3 days, etc. to archive it in a folder like the “trash” right after that, then you will have to think about the quality assurance, finding bugs, etc. Somebody will have to do this job after all. Whether you include the automated tests in the code development process or you totally rely on the testers, the automated tests will appear in your system sooner or later (or the project will die aborning).

The worst thing is that auto tests are also the code, i.e. all problems relating to the code development (the design, bugs, usability, performance, etc.) exist in tests. When you automate the testing, you actually implement the new functionality in your system. Thus, you should develop tests as any other features.

Read More

A way to speed up your Selenium tests

Selenium is an awesome and one of the most popular tools for automation of
Web Front End testing. The idea is that you write an application which opens your browser and simulates user actions.
After each action you check if application reacts as you expect it to. Selenium provides all the neccessary API to
make the process easier for you. Read More