IssueTracker

Hello, I'm posting this here because you have no place to post critical feedback for android studio, or it's been hidden away so that the developers don't have to hear feedback.

Regradless, I feel like I shouldn't need to mock method from public libaries in order to unit test my code.

Why would I have to write a mock for a public library? Plenty of UI development environments allow for seamless unit testing, but android studio is terrible at this. It's so bad I'm reporting it as a bug. It's obsurd that I have to mock android.graphics.Color.valueof just to create a simple unit test for my coding class.

How come third party libaries solve this problem but your own development studio wont? How is seamless intuitive testing not a priority? Maybe this is why so many android apps are so buggy is because of all the extra hurdles added in testing. Anything short of intuitive just bad design, and this just feels like laziness from the developers.

Thanks for nothing!