Terasology / Terasology/ModuleTestingEnvironment
CrashReporter should not be enabled
Open
Nobody has claimed this yet.
Good First Issue
- Dominant language
- Java
- Stars
- 3
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
As amusing as it is to see Crash Reporter's dialog pop up for a moment when a test case crashes, it's not an appropriate thing for an MTE test to do by default and it makes things extra noisy when it tries to do it in the headless CI environment.
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
No file or test entry point is named. Locate where CrashReporter is enabled in the MTE test setup, then run the relevant test in a headless environment; done means test crashes no longer open the dialog by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100