`wing test` returns Node.js stack trace when throwing errors for `tf-gcp` platform
Open
Nobody has claimed this yet.
☁️ gcp
🐛 bug
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
I tried this:
wing test --platform tf-gcp <file>.test.w
This happened:
I expected this:
I expected the stack trace to show me where my Wing code failed.
Is there a workaround?
No response
Anything else?
No response
Wing Version
No response
Node.js Version
No response
Platform(s)
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.
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 by reproducing wing test --platform tf-gcp <file>.test.w with a test that throws, then inspect the CLI's error-reporting path and the tf-gcp test entry point. Done means failures show the location in Wing source rather than only a Node.js stack trace; the issue provides no named files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, nodejs
- Domain
- cli, cloud, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100