Advice for a new tester
Hello everyone, my name's Robert. I have been asked to create a QA/Testing system for our desktop software. I'm relatively new to software development in general (about 1 year) and I was won...
Forum Discussion
"So, since you're an "Agile" shop, part of the "work" that you do before something is "done" is to test... YOU are the QA guy... YOU determine what needs to be tested. You are the "person" who does it and who has that feed back. Remember the manifesto: people over procedure. So, if someone is asking you to test something, you determine what it is, when it gets done, how it gets done, etc. Anything else is not Agile."
I think that's the snag we're going to run into. I've only been with the company a short time and my superiors already have an idea of what they want tested and how. Also, their knowledge of the system is far superior to mine.
My idea for these initial stages is to have a standardized way of submitting test cases with prerequisites, initial system state, test steps, test data, etc.
This way, we can at least move in the direction they want.
They may know the system better... but you're the tester... in an Agile shop, it is the person who determines their work.
Question: Are their documented requirements, user stories, epics, feature descriptions, specifications, etc? If so, you should be able to use those to construct test cases without having to depend upon someone else. At least use them to review the submitted test cases and determine if they make sense or if they need revision.
