Classic Testing Mistakes
It’s easy to make mistakes when testing software or planning a testing effort. Some mistakes are made so often, so repeatedly, by so many different people, that they deserve the label Classic Mistake.
source
Weekly newsletter about leadership, technology, books and anything else we felt compelled to share with others
Year 4 - Edition 31
A Fistful of Links is a weekly newsletter about leadership, technology, books, and anything else we felt compelled to share with others, brought to you by Og Maciel and Mirek Długosz.
It’s easy to make mistakes when testing software or planning a testing effort. Some mistakes are made so often, so repeatedly, by so many different people, that they deserve the label Classic Mistake.
source
The starting requirements is that instead of trusting secondary agreed sources for the information about what you have at hand for testing, using code as a source of information is essential. Mostly things don’t change without the code changing somewhere in the ecosystem, and seeing the change helps you target testing.
source
With an increasing number of breaches, intrusions, and data thefts, securing a web application is extremely important. On the other hand, programmers often do not have a strong grasp of how attacks work and how to mitigate them. This post attempts to close that gap a little.
source
Conceived in 2019, the Ten Years Reproducibility Challenge dares scientists to find and re-execute old code, to reproduce computationally driven papers they had published ten or more years earlier.
source
Asking questions like “Do we need testing?” are important. But there are other questions we should probably ask first.
source
Happy reading!
The Editors at A Fistful of Links