Functional testing is an important checkpoint before releasing a mobile application. In this article, Dmitriy Radchenko shares a checklist of some of the basic points that will be common among mobile applications when you need to perform functional testing.
Unit testing and Test-Driven-Development (TDD) are an important part of every Agile software testing strategy. One of the issue associated to these techniques is the coupling between the source code and its tests. In his blog post, Tingan Ho presents a testing strategy, called Baseline Testing, that should solve the coupling issues with TDD.
Today’s continuous delivery (CD) pipeline is a collection of many technologies that ensure the highest quality product reaches production. As a new feature moves from concept to production it goes through several phases of testing. However, for the CD pipeline to remain efficient, the bulk of this testing must be automated. Unit tests, load tests, integration tests, and user interface tests all require automation infrastructure.
Equivalence partitioning is a software testing technique that can be used during test design to divide the test data into sets of equivalent data called partitions from which you can build your test cases. In this extract from her book “Guide to Advanced Software Testing”, Anne Mette Hass provides an introduction to the concept of equivalence partitioning.
Even if they are at the basis of the software testing pyramid and they are at the heart of the Test-Driven Development (TDD) approach, unit tests are still a controversial topic in software development and some people event consider that most unit testing is waste. In his blog post, Bas Dijkstra explains why he thinks that unit testing should be the basis of any solid automation strategy.
There are often two approaches to improve software testing and software quality: you can get better at finding defects or you can get better at reducing the number of escaped defects. This presentation focuses firmly on the second option, how to set up teams and organisations that produce high quality products at source.
With the multiplication of versions, platforms (desktop, mobile, tablets) and operating systems, testing an application that is supposed to run in a browser is not easy. In this article, Alexander Rayskiy proposes an approach to select the set of browsers that will be used during the software testing activities.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates