[FEATURE] bun run integration-tests should print out the time elapsed for the entire test runner
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- bun, docker, typescript
Research direction
Start in scripts/integration-tests.ts, which is invoked by bun run integration-tests, and inspect where the API and integration test runner start and finish. Run the integration test command before and after the change; done means the output reports elapsed time for the entire runner, including Docker startup and shutdown.
Written by the indexing model from the issue text.
Description
Right now, when you run it, you'll see something like
$ bun run integration-tests
$ bun run scripts/integration-tests.ts
API started, running tests...
bun test v1.2.18 (0d4089ea)
tests/integration/login-flow.test.ts:
✓ Verify Email Flow > If I make a request with an unregistered email, I get an error [503.61ms]
✓ Verify Email Flow > If I make a request with an inactive user, I get an error [466.92ms]
✓ Verify Email Flow > If I make a request with the wrong password, I get an error [739.82ms]
✓ Verify Email Flow > If I make a request with the correct credentials, I get a session ID and refresh token [715.19ms]
tests/integration/register-flow.test.ts:
✓ Register Flow > doesn't store invalid credentials [11.12ms]
✓ Register Flow > stores valid credentials [637.33ms]
6 pass
0 fail
19 expect() calls
Ran 6 tests across 2 files. [4.51s]
Integration tests passed
It would just be nice to know how much time the test running took on top of that to startup and shutdown docker.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from codeforsanjose/TallyUp
-
help wanted priority: high type: question
Difficulty 5/5 Over a week Newbie friendliness 15/100
codeforsanjose/TallyUp#23 · 5 comments ·
-
help wanted
Difficulty 5/5 Over a week Newbie friendliness 38/100
codeforsanjose/TallyUp#22 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
codeforsanjose/TallyUp#20 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
codeforsanjose/TallyUp#18 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
codeforsanjose/TallyUp#17 ·
All issues in codeforsanjose/TallyUp
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100