Articles

Please enter an article title, author, or keyword
Stopwatch timeout Using Test Automation Timeouts as Performance Alarms

In automated testing, one of the challenges to developing consistent and stable tests is loading and rendering time and latencies. This plays a larger role for web applications or other network dependent applications, especially with user interface automation. But you can design tests so that timeouts can be used to measure the performance of the application and service while testing the functionality.

Faisal Qureshi's picture Faisal Qureshi
Testing code Hybrid Verification: Mixing Formal Methods and Testing

The ability to verify contracts either statically or dynamically, coupled with recent advances in proof technology, has opened up a new and promising approach to verification. Critical code can be proved with formal methods, and less critical code can be verified using traditional testing, with a clear separation at the interfaces between the two.

Ben Brosgol's picture Ben Brosgol
Data servers 7 Steps to Improving Your Data Testing

When you have tens of thousands of rows of data, how do you know what to test or how much to test? A set percentage? Random test cases? When do you stop testing? It can be overwhelming. Here are seven steps to help your team streamline their data testing efforts and know what to test, how much to test, and when to stop testing.

Karis Van Valin's picture Karis Van Valin
Pencil to paper Document Why as Well as What: Finding the Purpose of Your Software

Code can express what we want to accomplish, but it’s a little more difficult to express why we’re doing something in the first place. The people who maintain code are often not those who originally wrote it, so documenting why helps set a context and gives clues as to what the author was thinking when they came up with a particular design, making developers' jobs easier.

David Bernstein's picture David Bernstein
"Hello" in different languages Linguistic Testing: Setting Up Your Software for Global Quality

Globalization is an important step in ensuring your product is ready for worldwide markets, and linguistic testing is a crucial piece of the puzzle. This article looks at what linguistic testing is, product examples, and how locale-specific cultures play an important part in enabling linguistic support. Here’s how to design the best strategy for implementing a linguistic test effort.

Mukesh Sharma's picture Mukesh Sharma
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's picture 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's picture 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's picture 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's picture 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's picture Michael Stahl

Pages

Upcoming Events

Jan 30
Apr 29
Jun 03
Jun 25