I've been given the job of making our Android app work after

Read it, fix stuff, use git in case you fuck up. How is this difficult?

I'm using git of course. It's the worry of releasing it and breaking something in production seeing as there's no tests.

I don't understand the codebase and it's a fucking mess, spaghetti code. I need to add tests to make sure I don't knock anything out. I don't know how to do this.

Where to even start??

>>57499532
>I don't know how to do this
Why the fuck were you given the job? Mismanagement? You should at least be hitting this shit in a team if you've no experience of wading knee-deep in somebody elses shit. Curry scented shit at that.

You'll have to start the arduous process of refactoring and working tests into it, try not to hang yourself in the process. Or do, it'll be less painful.

>>57499641
I volunteered. I think the writing is on the wall for our org so I might as well level up my skills while I can in a relatively pressure-free environment.

When you create an Android project from scratch with Android Studio it sets up basic tests for you, if you want to check how it's done. JUnit is used for unit tests and Espresso for automating UI tests.

>>57500219
Thanks, man. That's the kind of thing I was after.

Is Appium no good for UI tests? When I've been looking, it keeps popping up, and using Selenium, which I'm familiar with from my Java days.

>>57500253
Never heard of Appium. Having tried both, I feel Selenium is not integrated as good as Espresso, which is also easier in my opinion.

Great. I'll take a look as Espresso now.

Thanks for the pointers!