search

Terasology / ModuleTestingEnvironment

3 stars 15 forks source link

CrashReporter should not be enabled #46

Open keturn opened 3 years ago

keturn commented 3 years ago

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.

pree-T commented 2 years ago

May I work on it?

jdrueckert commented 2 years ago

@pree-T Hi there, sure, feel free to give it a try and open a PR with your changes 👍

pree-T commented 2 years ago

How do I resolve this? Can you help me @jdrueckert ?

jdrueckert commented 2 years ago

@pree-T My response to you on the other issue largely applies here too:

How much programming experience in Java do you have? This is marked as a "Good First Issue" but targeting developers that want to get started with Terasology, but do already have development experience. If you don't have a lot of programming experience in Java yet, I'd recommend looking for issues in our module space instead: @Terasology. They are more suitable for beginners.

If you do have experience, do you already have a Terasology workspace set up? If not, please have a look at MovingBlocks/Terasology/wiki/Contributor-Quick-Start to get you started.

In any case I'd recommend to join discord.gg/terasology and ask questions there.