To be a Bug or not to be a Bug. What’s, How’s and Why’s of Bug Report

Being in a Software Testing field, process engineering, and now Application Security, I have been reading and documenting about Bug Reports but I have never came across such good, concise and precise definition of Bug Reporting.
What is Observation, Expectation, Reproducibility, and ultimately, what is Bug.

Have a look.

http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/

http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/observation.html

http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/expectation.html

http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/reproducibility.html

http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/responsibility.html

You’re using your computer and all of a sudden you notice something wrong. Something doesn’t seem to work correctly… it doesn’t do what you expect it to.

Is there something wrong with the hardware or with the software? Is there something wrong in your configuration or the way you’re using the computer? Are you expecting the wrong thing to happen?

You don’t know yet, but one thing is sure: What you saw didn’t match what you expected.

At this stage, this is an observation. Something looks wrong, so you start to troubleshoot.

Here’s an example of an observation:“While walking, I felt a pain in my right foot”.

Here’s an example of a valid expectation:“My shoe should not hurt my foot”.

Here’s an example of a reproducible issue:“Every time I walk, I feel a pain in my right foot”.

Here’s an example of an issue where the responsible component was identified:

“My Nike shoes hurt my right foot every time I walk. I feel no pain with other pairs of shoes, the same socks, the same places, the same amount of time.”

HPC (High Performance Computing) and Coffee

Today while reading an e-paper on HPC, I came across this humor. Loved it and sharing it.

Creating a good tasting coffee may be art, but keeping it fresh is a science. A leading food packager has found that instead of metal cans, plastic containers maintain coffee freshness longer after they’re opened. The simple solution was to switch to plastic coffee containers right? Well not so fast. Plastic created

another problem. Coffee continues to release gasses after packaging. A metal container can easily sustain the pressure, but a metal container doesn’t keep the coffee as fresh. The solution was to design a check valve that releases the pressure that builds up in the plastic coffee container. This solution, while fixing the first problem, created a second issue. When the coffee is shipped to the stores, the truck can take mountainous routes where the outside pressure becomes quite low. Gases exit the container via the check valve, but when the pressure increases the container implodes. To avoid "crushed coffee" the company

applied HPC technologies to engineer a container that would, for lack of better words, "implode gracefully." Using some clever design and HPC, they were able to create canisters that can travel far and wide yet still maintain their shape and keep the coffee fresh after it is open. This may be a good time to mention that

there is often lots of coffee-drinking involved in the world of HPC too — good to the last FLOP.