what's the difference between run test and debug test?
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Description
I write a test which need a usb, and I have a monitor tool to get all the telegrams send through usb.
Now, the problem is when I debug the test, the test result and the telegrams which are monitored are finished at same time, however, if I run this test directly, the test result(green mark) is end before monitor every time, telegrams are keep sending at the tool until the right number(e.g. 1000 telegrams in total) in this situation.
I want to know the reason. Thanks.
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 the USB-backed test in both run and debug modes while observing the monitor tool and its telegram count. Determine why the test result is reported before monitoring finishes in direct runs, then document the distinction and expected synchronization behavior; the issue names no files or tests to inspect.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100