When you talk to the platform tech lead for your project about how to coordinate what gets automated with what is tested manually and you're pretty sure he's convinced the manual testers treat each new build all like...
When you haven't participated in the sprint demo phase of your team's bi-monthly review ritual and they suddenly ask for a demo of the test automation project and you're all like...
When the senior manager suggests contrary to your professional advice that the right approach is to just get something running on this new project, even if you know it is broken, because you'll magically have time to refactor it later and do it right, so that you can just show some pretty graphs and you're all like...
When your new project is so stuffed full of libraries for the sake of libraries that your debug build is failing on the dex limit, forcing you to ask the developers to make adjustments and they come back with a solution that you just KNOW is going to break all your automation (cough, MULTI-DEX) but you try to listen politely anyway so you're all like...
When you're pulled off of one project just before making a breakthrough on a critical piece of the harness only to be put on another project that has no framework and will ship in a couple months but your manager asks you to make the best of it anyway but you're all like...
When your team lead sees that you've quadrupled the device coverage in your stress tests in a single day and is thus very impressed because he doesn't know about the clone job from existing job feature on Jenkins and you're all like...
Then as you're looking into a potentially blocking conflict between your automation framework and the client app's dependency injection framework, you suddenly realize you might not have enough smoke and or mirrors for the next iteration's demo, you start to formulate what your Plan B will be to fill your time so you're imagining yourself all like...
Comments
Post a Comment