Non-obvius behavior seems to be an hardest thing in testing. Applied to human beings behavior especially. To developers particularly. Effective working with developers seems to be a too big topic, so my talk should be considered as a very brief quickstart guide. You will learn some "selected by hand" antipatterns in work processes, e.g. why being a "good tester" can lead to "bad" consequences.

Every automated testing system is a solid software project that needs to be deployed and supported. Not every QA engineer has enough skills for that. As lead developer with background in software design, development and deployment, I want to share my practical experience that can help to avoid typical errors.