Describe the process you have at work.
Almost no automation when I got here and there's no unit testing. Some devs test a little and some just throw the code over the wall. I support two teams, one web and one .Net. The web product had some automation and I added on to it, but database has changed already and UI is going to change so all that is now useless. Starting over with that. .Net product is old and is sloppy as far as naming objects because it predates automated testing so they saw no need for names or ids. I make a little progress there and then have to wait for a dev to update objects so I can see them.
So testing atm is manual. Look in the backlog, see what's coming and if there is documentation (usually not) or existing test cases (sometimes). Chase down the dev for a demo. Write test cases we need. Get that testing done and pass it on for deployment. Put that in the backlog for automation.
Is there anything you would like to change in your process?
Everything? Lol. We are moving towards agile but so far that's just getting us sprints and not getting me any details in tickets.
What steps should a successful testing process have?
Communication. That covers everything I want.
Do you use any KPIs to measure your testing process? Which ones?
There's a count of how many tickets everyone closes (devs and all) but I don't know if anyone actually looks at it. I'm moving up the list. :)
