Skip to content

docs: improve standalone testing documentation - #31313

Open
Zac-Smucker-Bryan wants to merge 1 commit into
ionic-team:mainfrom
Zac-Smucker-Bryan:standalone-testing-docs-update
Open

docs: improve standalone testing documentation#31313
Zac-Smucker-Bryan wants to merge 1 commit into
ionic-team:mainfrom
Zac-Smucker-Bryan:standalone-testing-docs-update

Conversation

@Zac-Smucker-Bryan

Copy link
Copy Markdown
Contributor

Issue number: resolves #31312


What is the current behavior?

Current docs don't provide recommended testing guidance for accurately testing standalone components. This can create issues because a standalone (custom-elements) build doesn't expose el.componentOnReady(), so any test that reads fixture.nativeElement before hydration in a standalone project has the potential to not be testing what they think they are.

What is the new behavior?

  • Adds a couple of sentences to talk about using the existing componentOnReady helper from @ionic/core in Angular's testing.md file
  • Adds the same standalone guidance to the testing.md files for React and Vue

Does this introduce a breaking change?

  • Yes
  • No

Add context about using exported `componentOnReady` helper to make tests more accurate for custom-element builds.
@Zac-Smucker-Bryan
Zac-Smucker-Bryan requested a review from a team as a code owner July 31, 2026 02:26
@vercel

vercel Bot commented Jul 31, 2026

Copy link
Copy Markdown

@Zac-Smucker-Bryan is attempting to deploy a commit to the Ionic Team on Vercel.

A member of the Team first needs to authorize it.

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.

test: documentation for standalone component testing

1 participant