Hot answers tagged agile-testing
The best advice I can give you is to ask the other team what information they need to be successful. I've been in the opposite position where I'm supposed to automate tests others have made. Aside from this being a bad practice, creating too detailed documents or creating the wrong details will only waste both of your teams time. Send over what you have ...
You think it's impossible! Not really. Here is how to accomplish this. Short and sweet. QAs are involved in pointing the stories. You decide in sprint planning/refinement if any automation needs to be done on the story. Everyone including QAs know the effort it's going to take. So, you point them keeping that in mind. And, you mention that as an acceptance ...
You need to redefine what the definition of "done" is for a ticket. A ticket is not complete until manual testing, documentation, and automation are done. Project Managers might get upset at first but it's not hard to win an argument when you tell them the increase quality means.
If your management is so focused on short time returns that it will not invest in increasing your skills to improve your productivity - you should do it anyway in your own free time. All tools and documentation are free, you just invest your time. Of course your progress would be slower, but after some time you should be able to show some results, proving ...
Only top voted, non community-wiki answers of a minimum length are eligible