Articles

Please enter an article title, author, or keyword
Magnifying glass Exposing False Confidence in Your Tests

Testing can't tell you what's wrong with your code. It can only show what is not wrong with it. And though we cannot possibly conceive everything that might be wrong, it's important to stray from the "happy path." We need test cases that present bogus inputs and assert that they raise exceptions. That's how we can replace our false confidence with true assurance.

Steve Poling
Weak link in a chain The Problem with How We Do Regression Testing

Current approaches to automated UI testing are broken because regression testing is not testing; regression testing is version control of the behavior of the system. The goal is functional consistency. The regression test ensures that, after a change to the software, the unchanged parts still work the same as before. This realization makes creating and maintaining tests much more efficient.

Jeremias Rößler
Jack-o'-lantern 3 Scarily Easy Testing Tips

In the “spirit” of Halloween, here are three scarily easy testing tips that will help you find defects in your software under test. These tips will help you easily test an app's power usage, search for a particular term in a dynamically generated URL, and verify a form's checkbox has a checkmark. After all, it’s our job as testers to make sure using our software is a treat, not a trick.

Michael Mak
4 steps in a QA process 4 Strategies for a Structured QA Process

Being a software tester is no longer just about finding bugs. It is about continuous improvement, defining a clear test strategy, and going that extra mile to improve quality. Following a consistent, structured approach to QA will help you acquire more knowledge about the product you are testing, ask questions you otherwise may not have thought of, and become a true owner of quality.

Praveena Ramakrishnan
Bug taxonomy Using Bug Taxonomy to Design Better Software Tests

In software testing, bug taxonomy involves defining feature categories and collecting lists of possible bugs in each category. These lists can be used to give inexperienced testers some starting points, to help experienced testers brainstorm new ideas, and to evaluate the completeness of a test case. Using an existing bug taxonomy can be useful, but creating your own is even better.

Michael Stahl
Metrics dashboard on a tablet For Great Performance, Rethink Your Load Testing

The word concurrency is often used to define workload for load testing, as in concurrent users. Too often, it's the only input defined. In reality, there are a number of factors that contribute to workload and affect concurrency, and they all contribute to your load testing abilities—and, ultimately, the performance of your product.

Tim Koopmans
Person looking at an app on multiple devices 3 Strategies for an Efficient Mobile App Testing Project

Developing a testing strategy for a mobile app means facing multiple challenges that are part of the field. But by employing these three strategies, you can get valuable feedback about your mobile app’s functionalities before it is published—while still keeping time and budget in mind.

Thomas Raynott
Tweezers plucking a password out of code Conducting Security Testing for Web Applications

As cyber attacks continue to create panic, the threat to our applications and data in the digital sphere grows stronger. Enterprises in the connected world need to realize that security testing is essential for their web applications. They need modern, all-inclusive security testing plans from the inception of their projects to ensure a secure user experience. Here's how to get started.

Ketan Sirigiri
Icon showing one end to another Endgame Testing: Exploring Your Agile Product End to End

The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product.

Doron Bar
A pile of documents Slim Down Your Test Plan Documentation

Test plans are essential for communicating intent and requirements for testing efforts, but excessive documentation creates confusion—or just goes unread. Try the 5W2H method. The name comes from the seven questions you ask: why, what, where, when, who, how, and how much. That's all you need to provide valuable feedback and develop a sufficient plan of action.

László Szegedi

Pages

Upcoming Events

Apr 28
Jun 02
Nov 03