Facebook is released twice a day, and keeping up this pace is at the heart of its culture. With this release pace, automated testing with Selenium is crucial to making sure everything works before being released.
Big Data is a big topic in software development today. When it comes to practice, software testers may not yet fully understand what is exactly Big Data. A tester knows that you need a plan for testing it. Since most Big Data lacks a traditional structure, how does Big Data quality look like? And what the are most appropriate software testing tools? This article tries to answer these questions.
If unit testing has not always been adopted by software developers, this practice has become more mainstream with Agile approaches. Test-Driven Development and Continuous Integration are two technical approaches that require good unit testing. In this blog post, Maxime Lemaitre discusses attitudes that might make your unit testing fail.
With a growing number of instrumented tools in the market, Mobile End-to-End Testing (MOET) uses a non-instrumentation approach, and extensive use of design patterns. MOET’s mobile device libraries are pluggable open-sourced components and only one language and test harness is needed for testing on diverse mobile platforms.
In unit testing, you use mocks to simulate the behavior of other code parts in controlled ways. mock is a Python library for testing that allows you to replace parts of the system under test with mock objects and make assertions about how they have been used. mock has been integrated the Python standard library since version 3.3 under the name unittest.mock.
Tom DeMarco wrote “You can’t control what you cannot measure”. If test automation has always been actively discussed, the returns of automated tests were usually described in a very general way. There have been so far very few methodologies that can provide you with unbiased assessment of your software testing automation process. This article proposes some of methods to define test automation key performance indicator (KPI).
In this presentation, Michael Bolton explains how he uses interdisciplinary and exploratory methods to make sense of both the products we test and software testing itself. He explains how anthropology, which describes cultures and artifacts, can guide our testing; how investigative journalism can show us how to build a compelling testing story; and how sociology can help us understand how people interact with their tools.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates