From me to you11 top tips for QA from a Dev perspective

@blundell_apps

git - the simple guidehttp://rogerdudler.github.io/git-guide/

First you want to get the code on your machine

Gradle build systemhttp://gradle.org/getting-started-android/#developer

Then you want to build the code (build your demo or release candidate apps)

Reading Android Logshttp://developer.android.com/tools/debugging/debugging-log.html

WHEN the app crashes you want to read the logs so you can get insight

Un-obfuscating Logshttp://proguard.sourceforge.net/manual/retrace/examples.html

Reading the logs from a release candidate needs them to be translated first

Battery Historianhttps://github.com/google/battery-historian

Sometimes the app doesn’t crash, but it drains the devices battery a hell of a lot!

Automated Performance Testing Codelabhttps://codelabs.developers.google.com/codelabs/android-perf-testing/index.html

Scrolling lists for 3 hours to see if the app survives is boooring & hard to reproduce.

Understanding & Finding Memory leaks https://www.youtube.com/watch?v=_CruQY55HOk

I watch this video every time I need to investigate a memory issue

Stetho - A debug bridge for Android applicationshttp://facebook.github.io/stetho/

Makes manipulating device databases easy

Espresso Android Integration Testing Framework https://google.github.io/android-testing-support-library/docs/espresso/index.html

Acceptance, Functional, BDD tests

KIF iOS Integration Testing Frameworkhttps://github.com/kif-framework/KIF

Acceptance, Functional, BDD tests

Vysor - display your phone on your desktophttp://www.vysor.io/

Being able to record a video or a gif of the bug you’ve managed to find helps a dev 100x more on a Jira story.

We’re hiring Automated QA (developer in test)https://novoda..com

Come talk to me 1)To get involved2)To tell me where all

the QA are hiding! :-)