My question would then be, how do I best teach it? I am a QE guy, mostly doing Selenium based automation, but because we are hiring generalist devs much faster

My question would then be, how do I best teach it? I am a QE guy, mostly doing Selenium based automation, but because we are hiring generalist devs much faster than QE people, I would really like to teach them the QE mindset, because I have seen too often that they try to work around a problem, than to highlight it in a good bug report. Context, currently I am in a ~6 person QE team with ratio ~1 QE to 6 developers, still just a small team in a growing corporation, our product people are constantly pushing on rapid release cycle and I have heard "We will fix our failing integration test suites after the the release, now we don't have time." In the end we mostly do manual checking of the new features, where we often can persuade our product guys to drop few too broken off the release change-log. Only way we have so far been able to improve the testing situation was with putting rest of the team in front of a choice between spending ~50 man/days on manual regression testing or increasing our coverage ... Anybody else in similar situation?