Skip to content

chore: Migrate all packages/create-astro/test to node:test#10084

Merged
ematipico merged 15 commits intowithastro:mainfrom
shoaibkh4n:shoaibkh4n/testing_migration_create_astro
Feb 13, 2024
Merged

chore: Migrate all packages/create-astro/test to node:test#10084
ematipico merged 15 commits intowithastro:mainfrom
shoaibkh4n:shoaibkh4n/testing_migration_create_astro

Conversation

@shoaibkh4n
Copy link
Copy Markdown
Contributor

@shoaibkh4n shoaibkh4n commented Feb 11, 2024

Changes

Migrates all mocha tests to node:test of packages/create-astro/test
Part of ☂️ Move Astro tests to node:test #9873

Testing

All tests passed!

Docs

No docs added as this only affects testing.

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Feb 11, 2024

⚠️ No Changeset found

Latest commit: 6ca6a5a

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.

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

@github-actions github-actions bot added the pkg: create-astro Related to the `create-astro` package (scope) label Feb 11, 2024

expect(context.cwd).to.eq('./foo/bar/baz');
expect(context.projectName).to.eq('baz');
assert.strictEqual(context.cwd, './foo/bar/baz');
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

assert.equal and assert.strictEqual are the same because we import node:assert/strict. Can we use assert.equal like we are doing in the rest of the code base?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

hey, yeah you're right, .equal will be better as it maintains the consistancy through out the codebase. Give me a minute I'll update this.

@shoaibkh4n shoaibkh4n closed this Feb 12, 2024
@shoaibkh4n shoaibkh4n force-pushed the shoaibkh4n/testing_migration_create_astro branch from 4ad1bc0 to 1b528d2 Compare February 12, 2024 14:21
@shoaibkh4n shoaibkh4n reopened this Feb 12, 2024
@shoaibkh4n
Copy link
Copy Markdown
Contributor Author

Hey @ematipico , there is a problem with the nodejs test runner, sometimes it just stuck and lead to timeout. Even I made the description async with a low nesting. Any idea Why thou?

@github-actions github-actions bot added the pkg: astro Related to the core `astro` package (scope) label Feb 12, 2024
@ematipico
Copy link
Copy Markdown
Member

Hey @ematipico , there is a problem with the nodejs test runner, sometimes it just stuck and lead to timeout. Even I made the description async with a low nesting. Any idea Why thou?

No idea, let's see if the concurrency testing allows us to see which test times out and why (I just pushed a commit in your PR)

@shoaibkh4n
Copy link
Copy Markdown
Contributor Author

I noticed the problem after packages/create-astro/typescript.test.js -> typescript: setup package it just stucked just before the start of verify.test.js

@ematipico ematipico merged commit 3007d24 into withastro:main Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pkg: astro Related to the core `astro` package (scope) pkg: create-astro Related to the `create-astro` package (scope)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants