thefrontside / thefrontside/effectionx
Default timeout in bdd tests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 4
- Avg merge
- 3h 17m
- Merged PRs (30d)
- 1
Description
We have some tests that hang in Windows. I need to figure out how to fix the problem permanently, but I would in the meantime like to prevent tests from hanging by adding a default timeout.
Vitest uses 5s default timeout. I was thinking about applying the same.
@cowboyd Thoughts about constraints for configuration design?
- Do we want timeout to be on by default?
- Does it have to be pure or do we want to configure it via ESM module scope?
- How do we enable it or disable it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the BDD test setup and how Vitest applies its 5-second default timeout. Resolve whether timeouts should be enabled by default and configurable through ESM module scope, then verify that tests no longer hang and that the chosen enable/disable behavior works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100