如何用Espresso测试非Activity中ToastHandler类的自定义Toast？

Great question! Testing a custom Toast managed by a separate ToastHandler class (instead of directly from an Activity) is totally feasible with Espresso. Let me walk you through the approach and code examples:

Core Approach #

Since your Toast is created via a handler holding a Context rather than an Activity instance, we need to:

1. Use a valid test Context (preferably an Activity Context to match real-world theme behavior)
2. Trigger the Toast display through your ToastHandler
3. Target the Toast's view hierarchy correctly (since Toasts live in a system-managed window, not your Activity's view tree)

Step-by-Step Test Implementation #

First, let's assume your custom Toast uses a layout like layout/custom_toast.xml with a TextView (@+id/tv_toast_content) to display messages from your DataStructure.

1. Create a Dummy Test Activity #

To get a valid Activity Context (more reliable than Application Context for theme consistency), create a simple empty Activity for testing:

public class EmptyTestActivity extends AppCompatActivity {}

2. Write the Espresso Test #

Here's the full test class to verify your Toast displays correctly:

import androidx.test.core.app.ActivityScenario;
import androidx.test.espresso.Espresso;
import androidx.test.espresso.matcher.ViewMatchers;
import androidx.test.ext.junit.runners.AndroidJUnit4;
import org.junit.Test;
import org.junit.runner.RunWith;
import static androidx.test.espresso.assertion.ViewAssertions.matches;
import static androidx.test.espresso.matcher.ViewMatchers.withId;
import static androidx.test.espresso.matcher.ViewMatchers.withText;
import static androidx.test.espresso.matcher.RootMatchers.withDecorView;
import static org.hamcrest.Matchers.not;

@RunWith(AndroidJUnit4.class)
public class ToastHandlerTest {

    @Test
    public void testCustomToastDisplaysCorrectly() {
        // Launch the dummy activity to get a valid Context
        ActivityScenario<EmptyTestActivity> scenario = ActivityScenario.launch(EmptyTestActivity.class);
        
        scenario.onActivity(activity -> {
            // Initialize your ToastHandler with the Activity Context
            ToastHandler toastHandler = new ToastHandler(activity);
            
            // Create test data to pass to the Toast
            DataStructure testData = new DataStructure("Hello, Custom Toast!");
            
            // Trigger the Toast display
            toastHandler.createToast(testData);
        });

        // Verify the custom Toast is visible with the correct text
        Espresso.onView(withId(R.id.tv_toast_content))
                // Target the system popup window where Toasts live (exclude Activity's decor view)
                .inRoot(withDecorView(not(scenario.getActivity().getWindow().getDecorView())))
                .check(matches(ViewMatchers.isDisplayed()))
                .check(matches(withText("Hello, Custom Toast!")));
    }
}

3. Optional: Custom Toast Matcher (For System-Style Toasts) #

If your ToastHandler uses the system Toast class with a custom view (instead of a fully custom layout), you can use a dedicated matcher to target Toasts directly:

import android.view.WindowManager;
import androidx.test.espresso.matcher.RootMatchers;
import org.hamcrest.Description;
import org.hamcrest.TypeSafeMatcher;
import android.view.View;
import android.view.WindowManager.LayoutParams;

public class ToastMatcher extends TypeSafeMatcher<View> {
    @Override
    public void describeTo(Description description) {
        description.appendText("is a Toast");
    }

    @Override
    protected boolean matchesSafely(View item) {
        LayoutParams params = (LayoutParams) item.getLayoutParams();
        return params != null && params.type == WindowManager.LayoutParams.TYPE_TOAST;
    }
}

Then use it in your test like this:

Espresso.onView(withText("Hello, Custom Toast!"))
        .inRoot(RootMatchers.isPlatformPopup())
        .check(matches(ViewMatchers.isDisplayed()));

Key Notes & Troubleshooting #

• Context Choice: Always prefer an Activity Context over Application Context for testing—this ensures your Toast uses the same theme as it would in production.
• Async Handling: If your createToast method uses Handler.post or other async operations, use Espresso's IdlingResource to wait for the Toast to render (avoid Thread.sleep unless absolutely necessary).
• Toast Duration: Ensure your Toast has a long enough duration (e.g., Toast.LENGTH_LONG) so Espresso has time to detect it.

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