spinframework / spinframework/spin
e2e-tests: Print logs on test failure
Open
Nobody has claimed this yet.
enhancement
testing
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
Currently many e2e test failures just report e.g. 200 != 500. It would be helpful to dump logs on assertions failure, which I think should be possible within the framework but my attempt here ended up failing; I think because of a deadlock between the controller and spin process.
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.
Research direction
Start with the e2e test framework and the failed attempt in commit cd577be03f0cfebd2b7d1b12091e254df453abec. Reproduce an assertion failure and investigate the reported controller–Spin process deadlock. Done means failing e2e assertions dump relevant logs without hanging or masking the test failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100