At Neotys, we’re all about the future of load testing, especially when it comes to solutions for mobile, video, and cloud. That’s why we were intrigued by this question. Joe Strazzere is a QA blogger who frequently gets questions like this from testers:
“Hi Joe. I love reading your blog I check it daily. I have a question for you. What do you think about Black Box Quality Assurance testing holds in the future? I have 15 years of experience under my belt, but I do not want to shift into Automation testing, I don’t like to code. Do you think that I have future just doing Black Box Testing? Thanks.”
Check out Joe’s answer – and maybe share your own thoughts in the comments section.
Here’s an interview conducted by the folks at uTest with Michael Larsen, a software tester based out of San Francisco. Including a decade at Cisco in testing, he’s also has an extremely varied rock star career (quite literally…more on that later) touching upon several industries and technologies including virtual machine software and video game development.
In Part I of this two-part Testing the Limits interview, uTest talks with Michael on the most rewarding parts of his career, and how most testers are unaware of a major “movement” around them.
Check out the interview here.
Here’s a fun and informative article that carries a serious message for testers. It’s a fictitious conversation between a context driven tester and a competitor with less knowledge of and experience with testing. The tester gave him 10 bad tips on how to do a testing project.
Here’s a few of them:
- ‘First, always make a comprehensive test plan.’
- ‘Second, always make a detailed test strategy and test approach upfront’
- ‘Third, always follow the handbook testing that the organization uses in detail.’
This is worth a read – for the detail behind these 10 tips as well as the entertaining narrative in which they are told. Find the rest of the post here.
Ever been in an interview and someone asks a crazy, impractical question like this one?
Here’s a discussion you may find interesting. The poster wants to know how to approach testing real world objects. The problem that he faced before was getting the list of use cases from interviewer. Whenever he asked what the real world object should do, the interviewer just said, “the way you have used it.”
How would you answer this question? What would your approach be? Read some of the suggested techniques and join the discussion.