OuttaBox retweeted
The regular questions that I receive from someone who wants to be a "Security Tester".
1) What certifications do you recommend?
2) What courses do you suggest?
3) What tools should I learn?
No one asked me about, "How can I train myself to practice and build a Hacker Mindset?
OuttaBox retweeted
Here's another blog post that is worth reading, reflecting upon, and signal-boosting. Grab a coffee and 15 minutes to read and reflect.
"Six Things That Go Wrong With Discussions About Testing"
satisfice.com/blog/archives/…
OuttaBox retweeted
OK, Australia: Rapid Software Testing 4.0 is coming to Sydney (Feb 12-14; test-ed.com.au/events/rapid-…) and Brisbane (Feb 19-21; test-ed.com.au/events/rapid-…). New perspectives & exercises for the whole team, Agile or not. Preview at Sydney Testers' Meetup Dec. 13: meetup.com/Sydney-Testers/ev…
OuttaBox retweeted
Inspiring story! @FaizaYousuf: Engineering Momentum in the Pakistani Tech Scene - Dismantling the tech sector patriarchy one “manel” at a time tinyurl.com/wogrammer-faiza @WomenInTechPK #WomenintechPK @OuttaBoxPK @NEDUNIVERSITY
OuttaBox retweeted
Hey all. A request for some help.
@simTesting is a great tester and an active member of the community.
He is looking for a new contract. A RT of his post could help him get his new gig.
Thanks nitter.cf/simTesting/status/1005… nitter.cf/simTesting/status/1005…
Some insight into what a skilled Software Tester can really do, and how I can help your company.
Special thanks goes to Richard Bradshaw for the idea.
Also thank you to the support I have received recently from the community. theinterpretivetester.wordpr…
OuttaBox retweeted
It may be that the value of the opportunity outweighs the cost & the risks. That's a great conversation to have. Help your team understand the business opportunity & the value their work can have. Let them help you understand the technical risks inherent in your request
OuttaBox retweeted
Good software development teams will endeavour to deliver value to you in short, regular cycles. Sometimes what they bring you will be 'we don't think we should build this right now'. That's not them failing. That's them trying to save you considerable time & money
OuttaBox retweeted
A request to those who make requests of software development teams: Please treat the discipline of software development as an act of ongoing exploration and discovery and not as a promise factory.
OuttaBox retweeted
Use Slack? Want a place to get help and support, and share your insights with over 6000 testers, @heather_reiduff suggests you join the testers.chat community Slack. #NTD2018
OuttaBox retweeted
I should add to this. A long time ago now, I stopped and thought about how life’s work, as most games work offline, I knew it had to be local. So time seemed the most logical thing to try. Worked on every game since, that I’ve played!
OuttaBox retweeted
A perk of being a tester, altering the time on my iPad to refill my life’s on games
OuttaBox retweeted
Apparently there is a meetup in Manchester called TestBoss. It feels like something I should attend.
OuttaBox retweeted
Is your organization fixated on procedurally scripted test cases? That’s tantamount to obsessive demonstration—a profoundly weak form of testing. Variation matters. You'll find a lot more bugs if you think of procedurally scripted test cases as *examples* instead of instructions.
OuttaBox retweeted
For all those testers terrified that AI will replace us... Relax. AI is not *intelligent*; it's merely sophisticated software... and the more sophisticated software is intended to be, the more it needs testing by skilled testers, right?
OuttaBox retweeted
If you don't mention risk at least once a day, are you even a tester? #poke
OuttaBox retweeted
Not only a myth, but a myth with damaging public relations problems. "The product was fine... UNTIL THE TESTERS BROKE IT." "We could ship right now... BUT THE TESTERS KEEP BREAKING IT." "There are no systemic problems in our product or process; only that THE TESTERS BREAK IT." nitter.cf/stephenjanaway/status/…
OuttaBox retweeted
Replying to @michaelbolton
We took it a step further and evolved that into a fully chartered Test Strategy. Mindmap+HTSM+FEW HICCUPPS on steroids basically. Many instances now of developers saying (in team retro or casual conversation) that they changed their plan for a given user story after seeing it.
OuttaBox retweeted
I hear a lot from testers who discover problems late in development, and who get grief for bringing them up. There's a way around that: produce a coverage outline and a risk list. At the beginning of the project or ASAP, post them in places where people will see and read them.











