Software Testing, QA

Posts tagged ‘qa’

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 »

Selenium WebDriver: Page Object Pattern and PageFactory

How does it work?

Page Object Pattern is a pattern that displays user interface as a class. In addition to user interface, functionality of the page is also described in this class. This provides a bridge between page and test.

Read the rest of this entry »

Decision tables

Decision tables are used:
– when the output data or program behavior depends on the combinations of input data values;
– by checking the “business rules”.

Decision tables are usually divided into four parts.

Read the rest of this entry »

Robolectric: An Introduction

Robolectric
Robolectric is a unit test framework that de-fangs the Android SDK jar so you can test-drive the development of your Android app. Tests run inside the JVM on your workstation in seconds.

Read the rest of this entry »

Pairwise testing


Let our program take a dozen parameters. To test all combinations is very difficult, so you should choose the most common and potentially affecting each other. Bugs that arise by a particular combination of all ten parameters are rare.
The most common are bugs that arise by a particular combination of two parameters. The more information about the mutual influence of the parameters (more precisely – of the mutual non-influence), the more combinations we can not test. In the absence of such information, as well as by complex algorithms of program behavior, you should apply the method of pairwise testing.
Thus, we can simplify our task and test all the possible values ​​for each pair of parameters.

Read the rest of this entry »

Boundary Value Testing

Boundary Value Testing is the most well-known and simple technique of test design, which helps the tester choose the most effective values ​​from the ranges of values. This technique is applicable at all levels of testing – unit, integration, system, and system-integration test levels.

We consider the steps of using of the equivalence classes technique:
1.Determining the range of values ​​(usually, the equivalence class).
2.Determination of the boundary range.
3.Creating three test cases for each boundary – one that checks the border value; second that checks the value below boundary; and the third that checks the value above boundary.

Read the rest of this entry »

Automated Testing: To Be Or Not To Be

Automated Testing

To be or not to be the automated testing? This is a question that can be answered in most cases very difficultly. It requires an individual approach.

So, in this article, I will try to uncover all the problems of this issue.

Read the rest of this entry »

Follow

Get every new post delivered to your Inbox.

Join 60 other followers