Quick background, i'm a QA analyst with emphasis in test automation



I'm having an issue where I'm not sure where QA fits into scrum. It seems scrum is very developer-centric and I don't know where the most effective spot, within a 3 week scrum, testing fits.

I suppose i'm looking for personal experience, how do you all run your scrums? where does QA fit in? How are deployments handled?

In my opponion it doesnt work and it fucks with the entire process. Trying to cram development and testing into a 1-3 week sprint is ridiculous. Within a sprint, development should be doing test drivendevelopment with unit testing. QA van do their functional tests once development is completed.

The problem within my scrum team is, we will do tdd, and then QA will rewrite our fucking unit tests and call it a day. What's the point?

If we are allotted 2 weeks for a sprint and it takes 1.5 weeks to complete development, how do you expect to do thourough QUALITY assurance testing in the remaining 2 or 3 days? It's insane. The roles should be separate. Smashing them together produces code that has not been tested adequately.

At least your team is tdd. I think you guys should try pair tdd. Where 1dev 1qa take on an item at the same time. Qa decides what cases need to be fulfilled in unit tests and the dev fulfills them.

I guess the argument there is that bugs are a cheaper fix during development.

curiously, what's the qa going to be doing until the developer finishes? afaik it often takes more time to write code than to write test plans for it.

Ideally? Integration and smoke testing the code added from previous sprint I guess. Trying to look busy to validate the need to keep them on salary?

I think ideally, with a mature company whose test automation bed is robust, more test automation.