Once you assign QA to your devs, they will (should) figure out ways to automate as much as possible to reduce the burden that QA has on the team. In my experie

Once you assign QA to your devs, they will (should) figure out ways to automate as much as possible to reduce the burden that QA has on the team. In my experience, QA teams are usually starved of engineering resources, so a lot of things that can be automated are done manually or the automation is janky and constantly breaks. Once these issues are brought to the forefront, it becomes a priority to fix so that your expensive engineers aren't wasting time chasing bugs or fixing broken automation.