Let’s take each of the remaining questions in their own thread - would love to see more of a discussion stir up on any of these!
When working with some developers, I get the feeling they view testing as “magic” that requires a tester - even for some basic stuff. How can I help dispel this illusion?
I think I know what you mean. I’ve even had developers who say that the thing that I do (finding bugs where there shouldn’t have been any - with intent) is magic. And some of it really is magic of persistence and practice. But a lot of it is just persistence. Giving an application quality time is magical.
Sometimes I find developers would like to bundle all of the basics of testing into the same magic “why would I do it, you will do it anyway and probably find still issues even after me”.
I find that the only thing that has helped me is pairing, and mobbing. Sharing the experience of what the “magic” is about.
And making sure developers are encouraged to use time on testing is often relevant too. Sometimes they don’t see magic, they see boring work they rather skip with framing it as “magic”.