Reflection about Software Testing
1. From your experience, what characteristics do you need to have in order to become a software tester?
2. What recommended software tool do you use in your daily life at work?
3. How common is it for a software tester to review the source code?
4. How common is it for a software tester to be placed in an agile team?
5. What is the most difficult task to deal with as a software tester?
6. What pitfall does a junior software tester face when s(he) work?
7 “testing is an extremely creative and intellectually challenging task” Is it true and why?
These sound like interview questions and that is OK.
I was wondering why you are asking these questions?
Theres questions are not interview questions. They are based on my reflection.
Originally Posted by bklabel1
I have no experience as a software tester and that is why I'm asking. I strongly believe in knowledge management.
As best as I can answer it off the top of my head.
>>1. From your experience, what characteristics do you need to have in order to become a software tester?
* Patience, the world will seem unnaturally very stupid from your point of view, IE. WTF did the developer forget Y when he's working on X, where Y is the whole point of the project
* Methodological, you need to be able to document every thing you do and reproduce those steps precisely. No one likes a bug report where something "sometimes" happens.
* Have a think skin, It's only natural to only blame the messenger.
* Have integrity, is easy to be tired for a long week, month, etc... and sweep things under the rug.
* Steadfast when needed. Testing tends to be the thing that gets shortcut since it's at the tail end. Estimates are wrong, and development takes longer than it takes, and there's a hard deadline. You need to be always aware of what can be cut and the risks associated, and accurately communicate that.
>>2. What recommended software tool do you use in your daily life at work?
I'm an automation specialist. I tend to use mostly dev tools and frameworks. unit testing, mocking, data factories, etc... Since i deal with web, I tend to also use Selenium and Selenium Grid alot too.
>>3. How common is it for a software tester to review the source code?
Depends on organization and skill set. I tend to review a lot of code because i'm software developer who specializes in tests. My job involves making the code more testable such as creating test harnesses and test hooks, as well as putting together the whole integration pipe line. In past jobs in my Jr years as a QA Eng and Test Lead, I've always reviewed code to point out potential pit falls, however, my code review was not part of the release process. It was mostly out of strategize how to prioritize my tests.
>>4. How common is it for a software tester to be placed in an agile team?
Very common. Most Agile teams will probably run between 3-6dev to tester ratio.
>>5. What is the most difficult task to deal with as a software tester?
The business side. As bearer of bad news, you need to be very good at communicating accurately and not step on anyone's toes. This was my biggest challenge as a test lead. For example, I constantly struggle with putting together requests to buy expensive tools, and justifying why I need more time to perform X activity and why it's needed. When in a time crunch, everyone will think they can do your job better. Ex: "Why can't you do it XXXX way..." etc...
>>6. What pitfall does a junior software tester face when s(he) work?
Not knowing when to hold firm and when to be flexible. As mentioned above, as a Jr, you'll get that "Why don't you do it...". And if you don't have a Sr. or lead to back you up. It's very easy for Jr Tester to bend over backwards changing directions form the test plan and not get anything done. Then working late to make up for it and getting burned out quick.
>>7 “testing is an extremely creative and intellectually challenging task” Is it true and why?
I can't answer this one well. My view is different than most people. I see my career path as one leading to CTO. I'm a very capable full stack developer (who just happens to be paid more for specializing in high scaleability automated tests), I see myself as an observer to see what works and what doesn't for when I start my own company.
how to write good description for bug"missing password on add user"?