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

Ability to avoid a new nuxt instance for each test file #923

Open
3 of 4 tasks
acidjazz opened this issue Aug 22, 2024 · 0 comments
Open
3 of 4 tasks

Ability to avoid a new nuxt instance for each test file #923

acidjazz opened this issue Aug 22, 2024 · 0 comments
Labels
enhancement New feature or request pending triage

Comments

@acidjazz
Copy link

Describe the feature

I have a project where I've written multiple test files, each with their own setup() inside the top describe()

describe('/api/pen', async () => {
  await setup(setupConfig())
...

When I run these tests it creates a nuxt instance for each test file, demonstrated here: https://github.com/fumeapp/bio/actions/runs/10505024117/job/29101731333#step:12:48

I'm not sure if I have this setup incorrectly, or maybe if there was a way to have all test files share the same nuxt instance?

P.S. I am working on a potential GH action version that will run nuxt in the background and allow a possible setup({host: ...}) version, if i get this working i'll share it.

Additional information

  • Would you be willing to help implement this feature?
  • Could this feature be implemented as a module?

Final checks

@dosubot dosubot bot added the enhancement New feature or request label Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pending triage
Projects
None yet
Development

No branches or pull requests

1 participant