Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: use playwright test runner for adapter-static tests #9873

Merged
merged 3 commits into from
May 9, 2023

Conversation

benmccann
Copy link
Member

This is a less code and easier to understand as it doesn't mix two test frameworks together. If we wanted to switch uvu with vitest this would be one less package to convert and one of the hardest ones to address

@changeset-bot
Copy link

changeset-bot bot commented May 8, 2023

⚠️ No Changeset found

Latest commit: a34be84

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

packages/adapter-static/test/apps/prerendered/test/test.js Outdated Show resolved Hide resolved
packages/adapter-static/test/utils.js Outdated Show resolved Hide resolved
Comment on lines +6 to +8
test('generates HTML files', () => {
expect(fs.existsSync(`${cwd}/build/index.html`)).toBeTruthy();
});
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

feels kinda weird to use playwright for tests like these, no? should we split the tests up, or do you think that adds too much complexity?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, it did feel slightly weird, but there are so few of them. I think it's simpler with just a single test runner. we can always revisit if we add more non-browser tests

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair enough — that weirdness aside, this is much nicer

@Rich-Harris Rich-Harris merged commit a95eaa0 into master May 9, 2023
@Rich-Harris Rich-Harris deleted the adapter-static-tests branch May 9, 2023 16:59
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.

None yet

3 participants