One hundred cards. One hundred Test-related concepts.
Here on the club, we’ll feature a card from the TestSphere deck for people to write their stories about every month.
I challenge you:
Take a few minutes to think about your experiences with the featured card.
What bugs have you found that are related? Which ones have you missed?
How have you tackled testing for this concept?
What made it difficult or more easy?
What have you learned? What can others learn from your experience?
Take one of those experiences and put it to prose.
Telling your stories is as valuable to yourself as it is to others.
Two projects ago, I was tinkering with a performance testing tool to upload multiple different files at the same time.
At one point, I ran the scenarios for a couple of hours, uploading many files over the course of time.
This was on a Friday afternoon.
Monday, I returned to find the whole team severely pissed at me. Apparently, a number of servers and systems were completely messed up, down and blocked because of my test. This caused issues for multiple teams.
During my scenario’s, some of them looped and uploaded the same file multiple times and overlapped, creating all sorts of bad stuff.
I felt really bad, incapable even, while the whole team agreed I must be an idiot to be doing these kinds of tests.
It’s only months later that one developer told me that because of that scenario, the team was able to lay bare and fix a number of important issues with our architecture and setup.
Testing can cause a number of issues for multiple people. Especially when the results are unexpected. However, it can bring about many opportunities for success.
What’s your story?