Skip to content

Conversation

steve-the-edwards
Copy link
Contributor

This is based on the confusing overload of the two types of test harnesses that use the runtime directly.

renderForTest is a more accurate name since it is not strictly an 'integration' test (depending on how you define that). And the fact that it is headless is not really pertinent at this level of the API, that was an artifact of originally writing this API to run Android type tests that used Android dependencies but without having to render the UI (since the renderings just come out in the turbine).

We do not have all the facilities of the launchForTestingFrom* methods (such as starting with a snapshot) - but those are not extensively used AFAIK. They are also trivial to add to renderForTest and forward along to renderWorkflowIn. So this is somewhat of a premature deprecation (a soft deprecation), but at least it shows the direction.

Closes #1411.

#1152 will remain because it has more specification of the further work required.

@steve-the-edwards steve-the-edwards merged commit 1935fc7 into main Aug 28, 2025
72 checks passed
@steve-the-edwards steve-the-edwards deleted the sedwards/test-renaming branch August 28, 2025 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename headlessIntegrationTest make usage more clear.
4 participants