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.
You see, if you are even vaguely familiar with the concept of web app development, you'd know that it's a process that is mired in questions and decisions before you can also get started. Also, though there's a good deal of choices involved, perhaps the most consequential is choosing the framework that will be used to deliver the web app for your business.
This blog post showcases the difference between PHP and Java and explains which would be a better option for what type of enterprise application development.
According to a recent study, the world is well on its way to having more than six billion smartphone users across the globe by next year. Researchers are also of the opinion that by 2022, the number of total app downloads is likely to be as much as 258.2 billion.
Every small and large enterprise require some actionable insights to grow their business. Moreover, to get such ideas, it is necessary to gather the data from various sources that stored in different technology platforms.
Telemedicine is the remote diagnosis and treatment made by health professionals to the patients through web and mobile platforms. Telemedicine or say telehealth applications allow people to connect with the practitioners from anywhere without physical presence.
Round Robin is a strategy for scheduling territorial sales, which sounds not only as to music to most ears, but it is also a very interesting topic for understanding for users of easy to use CRM software.
Whether you are planning to arrange a seminar or conference, university alumni meeting, or recruitment for the company, you will need to cope with many things to keep everything streamlined. Moreover, you may have to deal with some last minute glitches which need teamwork and much workforce for making the event engaging and memorable
Many times, people are having queries related to secured PDF files having the owner password. Basically, these files are restricting them to edit and print PDF documents. Therefore, in such cases, it becomes necessary for the user to remove permission password from PDF documents.
When an injury or fatality happens at a workplace, it causes immeasurable suffering and problems to the employees & their families. Moreover, it costs the organizations large & inexorable expenses every year. To minimize these unwanted pains, companies are switching to the OHS (Organizational Health and Safety) management systems