I am also seeing Vanilla Javascript Error fail, and not sure exactly what is going on.

I think a better solution might be to remove this logic all together. stories are all snapshot tests, so we already know that the names are present and in the right order because they're in the screenshot. if this logic is flakey, then lets just rely on the snapshot instead.

@aslilac I think the test might actually make sense. It validates that the organizations are listed in the correct order: first the active organization (Omega org), then the remaining organizations alphabetically.

AFAIU, if a bug is introduced where the order of the orgs changes, Chromatic will detect those visual changes in the screenshot, but it won't fail automatically, a reviewer would need to catch it manually. The programmatic assertion ensures the sorting logic works correctly and fails immediately if it breaks.

This new logic fixes the flakiness of the test by querying the .truncate span directly instead of relying on the full textContent (which included the avatar fallback text). The other failing tests in the CI are unrelated to this test and are failing on other builds as well.

After discussing with @aslilac on the best practices around Chromatic tests, the focus should be on visual validation through snapshots rather than programmatic assertions. The snapshot will catch visual changes resulting from any programmatic changes during the Chromatic review process. The programmatic assertions on these tests were redundant and introduced flakiness, so removing them makes the tests more stable while still catching issues through visual diffs.