test management

Articles

Power button Simplify Continuous Operation Tests with a Periodic Reboot

Continuous operation tests find important bugs, partly as a result of their long operation and partly by increasing the probability of finding statistical bugs. However, CO tests have their own downsides. Mandating a periodic reset or reboot can work around these issues, as well as save time and cost for testing, reproduction, debugging, and fix verification.

Michael Stahl's picture Michael Stahl
Test documentation Tests as Documentation

It’s important that test authors keep in mind the inherent authority their tests possess. After all, an application’s tests are sometimes the first lines of code a new developer will read when acclimating to a new codebase. Tests aren't the only kind of documentation you need, but automated tests in a CI environment can provide a lot of useful information.

Nelson Nogales's picture Nelson Nogales
Gearbox for a car with a manual transmission Shifting Your Testing: When to Switch Gears

Shifting your testing either left or right can meet different needs and improve different aspects. How do you know whether to make a change? Let your test cycles be your guide. Just like when driving a car with a manual transmission, if the engine starts to whine or you’re afraid you’re about to stall out, switching gears may be just what you need.

Maximilian Bauer's picture Maximilian Bauer
Collection of random numbers When a Number Is Not a Number: Benefits of Random Test Generators

We like to hope that we will consider all possible situations when devising our tests, but it’s all too easy to overlook the unusual cases. That’s the benefit of random test generators. We might feel comfortable after testing a few dozen test cases; these tools generate hundreds. With more stuff getting tossed at the wall, there is a greater likelihood that something interesting sticks.

Steve Poling's picture Steve Poling
Brain made out of a circuit board Leveraging Machine Learning to Predict Test Coverage

Test coverage is an important metric within test management, and as technology evolves, we‘re able to leverage new trends to predict coverage. Weka, an open source suite of machine learning software, can take your test management beyond spreadsheets to the latest AI technologies, letting you predict your test coverage earlier with greater accuracy.

Bhavani Ramasubbu's picture Bhavani Ramasubbu
Group of people holding trophy that says "2018" Top 10 StickyMinds Articles of 2018

With the rise of technology like AI and practices like DevOps, teams everywhere are looking for ways to speed up testing without sacrificing quality. The articles in 2018 reflect that, with the most popular topics being shifting testing left, optimizing tests for continuous integration, and the future of software testing. If you're looking for cutting-edge testing techniques, check out this roundup.

Beth Romanik's picture Beth Romanik
Testers looking at graphs of performance test results Responsibly Reporting Performance Test Results: Trends, Noise, and Uncertainty

In order for performance test results to have value, you should report them in context. There are two main considerations: How do these compare to previous results? And how can we provide early reports on performance while emphasizing that these are preliminary results that may change significantly as we progress? Here are some ideas for responsible reporting.

Michael Stahl's picture Michael Stahl
Gauge with a needle in the green zone, showing good performance 7 Simple Tips for Better Performance Engineering

Rigorous practices to reinforce performance and resilience, and testing continuously for these aspects, are great ways to catch a problem before it starts. And as with many aspects of testing, the quality of the performance practice is much more important than the quantity of tests being executed. Here are seven simple tips to drive an efficient performance and resilience engineering practice.

Franck Jabbari's picture Franck Jabbari
Graph showing how testing earlier costs less and means fewer overall defects The Shift-Left Approach to Software Testing

The earlier you find out about problems in your code, the less impact they have and the less it costs to remediate them. Therefore, it's helpful to move testing activities earlier in the software development lifecycle—shifting it left in the process timeline. This article explores the shift-left methodology and how you can approach shifting left in your organization.

Arthur Hicken's picture Arthur Hicken
Racecar on a track Test Faster: How We Cut Our Test Cycle Time in Half

In just a year, one test team reduced its test cycle by more than 50 percent. It took analysis, planning, and effort—first they looked into how they spent their time, and then they questioned whether they could reduce time in any of those areas. Once they knew where they could be more efficient, they could start tackling their blockers. Here's how you can, too.

John Ruberto's picture John Ruberto

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.