Wells Fargo Approach to Automation Testing: "The Neglected Stepchild Scenario". Needs dedicated managers and separate wing.
6 replies (most recent on top)
"Yes, in townhalls, management meetings they talk we eliminated QA manual testing, however the reality on the ground is sharp contrast as every team is still doing manual testing and there is no automation. Not sure, managers bluff or giving wrong information to upper management."
This may be true for majority of teams, but it surely is not for all. Automation was part of DOD and always completed within the Story on the last couple of teams I have been part of.
Yes, in townhalls, management meetings they talk we eliminated QA manual testing, however the reality on the ground is sharp contrast as every team is still doing manual testing and there is no automation. Not sure, managers bluff or giving wrong information to upper management.
We’re a fu-k ton out of accessibility compliance. Hope Charlie gets his sh-t pushed in. WF talks about inclusivity without the walk.
They'll just keep saying 'BDD'.
Yeah, we had that. Some genius decided that we didn't need QA anymore and got rid any people with any expertise in testing. I'm kind of surprised we didn't see massive outages and defects.
Do they have an approach now? When I left they had some Selenium. but it only worked with their own config management system that only worked with java net beans. With Wells automated testing was the same as user interface testing. They were few if any unit and integration tests.