A Better Way of Reporting Performance Test Results
Powerful reporting of test results is one of the holy grails of our profession. If done correctly, it improves the project's quality and helps us focus on the actual issues. But if done badly, it adds confusion and reduces the value that testers bring.
Reporting the results of functional tests is relatively simple because these tests have a clear pass or fail result. Reporting the results of performance testing is much more nuanced.
Let's start with a definition: For the purpose of this guide, I use the term performance test to imply any evaluation that performs a measurement, with a range of numerical values all, considered an acceptable result. It may be the measurement of energy intake, the number of users a website serves in parallel, the rate that information can be read from a disk, etc.--any measurement of a nonfunctional requirement.
The first challenge in performance testing is deciding what's considered a"pass" Often this is neglected in the requirements definition stage. I've seen many requirements that read something like, "Data extraction time from the database shall be under 10 mSec," or"The rate of processing a movie file will likely be at least 100 frames per seconds (fps)." Such requirements are incomplete since they do not include the actual target we want to hit. We just know the worst result we agree to tolerate and approve the product. There are two issues here.
First, let's assume I conducted a test and found that video file processing is done at a rate of 101 fps (recall that the requirement was"at least 100 fps"). Sounds great, right? But does this mean we are close to the edge (that is, the product hardly meets the requirement) or everything is fine? If the requirement was well defined, it would have contained both the goal and the minimal --for instance, goal: 120 fps; minimal: 100 fps. With such a requirement, a result of 101 fps clearly indicates the product hardly meets the requirements.
Second, when a test fails slightly (e.g., 99 fps), the product manager is under pressure to be"flexible" and accept the product as is. How often have we heard, "Really, we are below the minimum, but we are nearly passing, so we can determine it's fine"? If the full requirement were available (goal: 120 fps), it would be clear how far the results are out of the target and the product has a real problem.
For the sake of completeness, I will mention that a nonfunctional requirement should not just specify target and minimum, but also the test method because the test method influences the results. By way of example, when measuring CPU utilization, the results could vary significantly depending on how we perform the measurement. Can we measure the maximum value listed? Over how long a time? Do we average dimensions? How many dimensions a second? What's running on the CPU in parallel to our test?
In theory, reporting performance test results should not be an issue in any way. Just present the results and indicate a pass or fail. But again, we do not just wish to know the result; we would like to get an idea of how the result is related to the target. Crafting a report that is not overly complex but still delivers a comprehensive picture of the status is a balancing act.
We can use a table:
But because most products have many performance requirements, we will end up with a huge table filled with numbers. It'll be hard to quickly see where there's a problem. We could use color to improve readability:
But this brings up more questions. Does it make sense that frame processing rate and CPU utilization get the same color code? One is practically failing, while another is well within the acceptable variety. So perhaps color frame processing in red? But then what color would we use for a collapse? And how long would we believe a result green before it should become yellow? Not to mention the problems that could happen because of some people having color-blindness.
I was thinking about this issue when my doctor sent me for my yearly blood check, which I really do meticulously--about every 3 years. Anyhow, the results from the laboratory included a list of dozens of numbers displayed in this format:
Despite the fact that I'm not a physician, I could tell immediately which results were fine, which were marginal, and which were something I should discuss with my physician.
A light bulb went on in my head: Why not use this method for reporting performance tests? I took a few data points and experimented with PowerPoint:
Notice that I still use colours, but the axis explains the selection of color and explains where higher is better and where lower is better in a color-independent way. The reader can clearly understand the position of each measurement inside the allowed range; the colours serve mainly to focus attention where there is trouble. Creating such a report takes some time, but it could be automatic.
I haven't yet seen this idea implemented in a real project--I am still working on that--but if you do use this idea, I'd be delighted to learn about your experience and the response from your organization.
Issue tracking is one of the most important parts of a software development lifecycle that cannot be skipped or omitted. While organizations emphasize on increasing their software testing efforts to improve quality and ensure faster releases, their dependency on tools increases too.
As the importance of software continues to grow, there are several factors whose influence have grown right along with it. And out of all of them, test automation frameworks have garnered their fair share of attention from the market. Why is that?
Electronic Health Records system offers benefits that have enabled an industry as tricky as healthcare. The software allows for medical professionals and other professionals across the ecosystem to quickly input as well as access information about a patient.
Development, while eventually rewarding, can be a very tedious process. But that’s the thing about technology; it always manages to find a solution, no matter the problem. So, in the context of development, experts came up with frameworks that would help programmers do away with tedious and arduous coding practices.
DevOps and Agile approach in an organization is not merely an implementation of certain tools and techniques, instead, it is cultural change. Many organizations in the software industry have either adopted these methodologies or are making accommodations to incorporate them in their system.
Running a company, no matter how big or small is no easy task. It has so many different parts and components that all need to be managed correctly to ensure seamless operations for the company. Now, different people may have different opinions about how to ensure the smooth functioning of a business.
These days, collaboration has become a business need to support innovative ways of working. Companies are well beyond a realm where employees are destined to their counters. The staff is hardly in the same place at the same time
Almost every single person in the software industry must have heard about code reviews and may be familiar with it. Even then the concept of reviewing codes is misinterpreted. People in this industry generally assume that performing tests must be sufficient to meet the requirements of the verification process, yet it is mostly ignored in the software development life cycle.