“Is your feature ready for QA” checklist

So you’ve finally finished a feature, cleaned up the code, opened a pull request…only to have a QA engineer come up to you with “Umm, have you tried this on *whatever device here like tablet/old API/new API*?”. Has this ever happened to you? It sure has with me and my colleagues and if you’re not a perfect developer (are there?) this might have happened to you too. So this inspired me to write a checklist that you should go through before opening a pull request. By the way, if you haven’t seen it yet, Github has introduced the draft pull requests now, so you can open one for review, but not merging. I think it’s a pretty cool and useful thing exactly for such case: when all together the feature and logic is final, but you just need to check those business things.

I’m writing from an Android developers perspective, but I think this can be easily translated to other fields like iOS/Web too… read full article on chililabs.io