Contributor Hi, hi! I am Iaron!

[Iaron da Costa Araújo]

• Name: Iaron da Costa Araújo
• Social: GitHub: https://github.com/iaronaraujo Facebook: https://www.facebook.com/iaronaraujo
• From: Brazil
• Skills / Tools: Java, Spring Framework, Backend, Test, Research, Quality Assurance
• Found via: Google Summer of Code
• Interests: I'd really enjoy developing games since I am a gamer since I was 2 years old and it was this passion that drove me to a Computer Science Major. Since I've been recently working on QA and Testing, I would like to begin my contributions to Terasology in that area!
• Extra: I've worked for about a year and a half in a project to create a framework to aid in the experimentation of software testing techniques. During this time I've learned a lot about test case generation, selection and at the ending of the project, I also researched about some tools to generate test cases automatically (Evosuite and Randoop). So, when I was looking at the Gsoc ideas, I really liked this one: https://github.com/MovingBlocks/Terasology/issues/2780
  I have already forked the project and put it on IntelliJ, but I am having problems deciding what my first pull request will be. I saw the bite-size issues but I wanted to know if there are any other issues that I could try to solve, especially ones related to Issue 2780. Thank you!

 

[Cervator]

Yessssssssssssss! More unit testing support pleeeeeeeeeeeease!

Oh. Hi! Welcome

So probably the easiest way to get started on that: write a new unit test! Any unit test! For the engine or a module. It doesn't even have to address a specific issue, we literally need more unit tests everywhere!

We've had a few attempts over time to get more into doing test coverage analysis and such. There is a percentage visible for the main engine job at http://jenkins.terasology.org/view/Statistics/ even, but it hasn't really been enabled for anything else. Help make that percentage go up!

 

[Skaldarnar]

I like unit tests. Especially, when someone else is writing them

And yes, @Cervator is right in saying that any unit test you contribute will help make the project better (and hopefully safer to regression). You might also want to look at (recently) closed issues and figure out if some of the bugs and failures could have been caught by a proper test case. If so, implement it and make a PR - this will at least prevent it from emerging again in the future.

 

[Iaron da Costa Araújo]

Hey, thank you all very much for the feedback! I will try to run some tools like EvoSuite to generate a bunch of unit tests this week. I will also look at the recently closed issues and see if I can create a test suite for them!

Thank you again, you all are so friendly! I really want to be part of this community!