Loving some of these gems she is dropping:
"The hard part about software is owning it, not writing it"
"Know what your normal looks like, to recognise abnormal"
"Our job as engineers is to develop engineering judgement".
@maaretp some sort of goal should be that the automated tests run on all merges.
QA test should be a daily deploy environment and with success only a button away from automatic deploy to production.
@nemeciii We have had automated test run on all merges, and nowadays there's a decent amount / coverage in them. Continuous exploratory testing in production-like environment feeds into growing automation.
I would absolutely not go back to one deploy per sprint or one deploy per night. We're 3 teams, 20 people.
In about a year, I can move "QA" as you call it to happen while in production.
@maaretp our automated tests run on 39 azure agents with 4-22 pabot processes on each. Test duration including Build & IaC deployments take still about 90 minutes. Hindrances of monolithic architecture hit hard since we can't limit the builds, IaC and tests to the changed parts of the software.
We have over 5000 automated test suites.
We get around 8 PRs merged daily.