Articles

Please enter an article title, author, or keyword
Toolkit full of tools What Testers Need in Their Accessibility Testing Toolkits

A software tester’s accessibility testing toolkit should contain various tools, both to help testers “walk in the shoes” of their users and to quickly flag obvious problems and expose accessibility features (or a lack of them). High performance is only achievable with human skill, but these tools will help you uncover potential issues and make your product a better user experience for a wider audience.

Albert Gareev's picture Albert Gareev
A line of identical rubber ducks The Unspoken Requirement: Testing for Consistency

It's easy to see that style consistency is important when discussing the user interface. But there are other areas where being consistent is just as important, even though they are not as visible. Consistency is one of the quality attributes of a product—any product—even if it is not stated clearly in the requirements documents, and testers have a responsibility to check for it.

Michael Stahl's picture Michael Stahl
Legos 100 Percent Unit Test Coverage Is Not Enough

Many people equate 100 percent unit test coverage with high code quality, but that is not enough. Code coverage tools only measure whether the tests execute the code; they make no judgment on the effectiveness of the tests. Testers should review unit tests, even if they have high coverage levels, and either help improve the tests or supplement them with extra tests where necessary.

John Ruberto's picture John Ruberto
Smiling robot The Future of Software Testing

Many software testers have opinions about the future of their profession. Here, László Szegedi takes a look at how today's realities could shape tomorrow's possibilities for testers when it comes to new skills and technologies, roles and dynamics, and tools and devices. What could your job look like a decade or more from now?

László Szegedi's picture László Szegedi
Extract, transform, load Testing the Extract, Transform, and Load Process in Data Warehouses

Pulling data from a source system and putting it into a data warehouse is a process commonly known as extract, transform, and load, or ETL. Testing the process can be a chore—you need to be sure all appropriate data is extracted, that it is transformed correctly to match the data warehouse schema, and that it's all imported. Instead of testing the ETL process as a black box, you can pull it apart, testing each piece in isolation.

Matthew Heusser's picture Matthew Heusser
Taking notes next to computer How Testers Can Start Thinking like Users

When it comes to what testers should focus on, people always say you have to think like a user. Aleksis Tulonen used to think he was good at doing that—until he started actually sitting next to his applications' users. Then he thought of all kinds of questions that testers should consider more often. He discusses what you can learn from your users.

Aleksis Tulonen's picture Aleksis Tulonen
Five pillars 5 Pillars of a Successful Test Automation Implementation

Discussions on what constitutes a “proper implementation” of test automation often focus on what tool you should use, but that is only one part of the equation. Bas Djikstra details four other things you should consider, how they contribute to the success of your test automation, and what risks are associated with failing to pay proper attention to each of them.

Bas Dijkstra's picture Bas Dijkstra
Green lightsaber Strategies for Testing a Lightsaber (That Don’t Include the Force)

In the Star Wars saga, those in tune with the Force wield lightsabers. Lightsabers are self-built, so each one is unique and a reflection of the personality of its creator. As a tester, I found it intriguing to think about how we would test lightsabers in our own galaxy. Let’s explore how the techniques we might use for testing lightsabers can inform our real-world testing.

Michael Mak's picture Michael Mak
Passing the baton Testing during Transition: Test Criteria for Outsourced Software

In the world of IT outsourcing, it is not uncommon for a company to have its applications and infrastructure developed or maintained by others. As vendors compete for this business, a common trial is testing the transition activity as a whole. How would you design acceptance criteria of a transition trial so that it is testable and clearly communicated?

Jesper Ottosen's picture Jesper Ottosen
Continuous delivery Test Coverage in the Age of Continuous Delivery

Test coverage is a strategy to help us spend scarce testing time on the right priorities. When things were tested last, how much automation coverage we have, how often the customers use the feature, and how critical the feature is to application are all factors to consider. Here are some ideas for keeping quality high when you're transitioning to continuous delivery.

Matthew Heusser's picture Matthew Heusser

Pages

Upcoming Events

Nov 28
Dec 04
Apr 29
Jun 25