Dealing with third-party keyboard in Android Espresso tests?

Imagine I have a test that types some_text into an instance of EditText. It seems that some third-party keyboards that have auto-capitalisation turned on (e.g., SwiftKey), will enter this text as Some_text instead. The test then fails because what's in the EditText is not what was expected.

I have worked through the documentation, which is probably not as comprehensive for testing as it is for other parts of the API, but I am not sure how to deal with this. Obviously it suggests that the test is not up to scratch... one way to fix it is to put the target string as ALL_CAPS, but I am wondering if there is a less hack-y workaround? Any leads much appreciated!