如何在Android Studio中模拟外部及手机数据库进行应用测试？

Hey there! Let's tackle your database simulation problem for your Android app—totally get how frustrating it is when testing hits a roadblock like this, especially after writing so much code. Here are practical tools and approaches to get you unblocked:

一、模拟外部数据库（替代手机端MySQL应用） #

Since the MySQL apps from app stores aren't working for you, you don't actually need to run a database on your phone—your app connects to external databases over the network, so we can set up a mock or local database on your computer instead:

• Local MySQL/MariaDB Server
  Set up a MySQL or MariaDB server on your development computer. Then:

  1. Make sure your Android emulator/physical phone is on the same Wi-Fi network as your computer.
  2. Find your computer's local IP address (e.g., 192.168.x.x on Windows/macOS).
  3. Configure your MySQL server to allow remote connections:
     • Edit the my.cnf/my.ini file to set bind-address = 0.0.0.0 (or your local IP).
     • Grant access to your database user from your phone's IP or any IP: GRANT ALL ON your_db.* TO 'your_user'@'%' IDENTIFIED BY 'your_password';
  4. Update your app's connection string to use your computer's local IP instead of a remote server.

• H2 In-Memory Database
  If you want a lightweight, no-install alternative, use H2's in-memory mode. You can spin up an H2 server locally, which acts just like MySQL for testing. It's great for quick iterations since it doesn't persist data by default (you can enable persistence if needed).

• WireMock (Mock API Layer)
  If you don't need to test actual database logic yet, use WireMock to mock the API endpoints your app uses to interact with the database. You can define static responses or dynamic behavior to simulate success/failure scenarios without touching a real database. This is perfect for testing your app's UI and business logic independently.

二、模拟/调试手机端本地数据库 #

For the database running directly on your Android device (like SQLite), here are the best tools built into Android Studio and third-party options:

• Android Studio Database Inspector
  This is a built-in tool that lets you:

  1. Connect to your running app (emulator or physical device).
  2. View, query, and edit your app's SQLite/Room databases in real time.
  3. Run SQL queries directly and see results instantly.
     Just go to View > Tool Windows > Database Inspector in Android Studio—super handy for debugging local database issues.

• Room Persistence Library (with Testing Support)
  If you're using Room (Google's recommended ORM for Android), you can write instrumented tests that use an in-memory Room database. Add this to your build.gradle:

  androidTestImplementation "androidx.room:room-testing:$room_version"
  

  Then in your tests, initialize Room with Room.inMemoryDatabaseBuilder()—this creates a temporary database that's destroyed after tests run, so you don't have to worry about cleanup.

• SQLite Studio
  A third-party desktop tool that lets you export your app's SQLite database from the device (via Android Studio's Device File Explorer: /data/data/your.package.name/databases/), open it on your computer, edit tables/rows, and import it back to the device. Great for deeper debugging or modifying test data.

Quick Tips #

• Use build variants to switch between test and production database endpoints. For example, create a debug build that connects to your local MySQL server, and a release build that uses the production database.
• For unit tests, mock your database repository layer with Mockito—this lets you test business logic without needing a real database at all.

内容的提问来源于stack exchange，提问作者user9609441