Starting out with Testing on the Mod

So you want to help out the mod by testing it? But where do you start? As an Alpha-tester you will have been given access to this Github along with a dev version of the mod and also the Discord testing channels and Voice Channel, Here you can discuss with fellow testers and developer team members on where a good area to testing would be. So staying active on these channels and making sure to read up on what's been written there is indeed very recommended. But if your feeling daring you could always check out the Testing column inside the Projects as that would be a good start to help out with some current stuff needing testing. But you could also start playing the new content added to the mod to see if you'd could fin any Bugs or perhaps you'd find that you'll have some Suggestion for it. But always feel free to seek out counsel from the Lead Tester if your feeling unsure where to start or have other questions surrounding what best to focus your efforts on.

• Reporting Bug-Reports & Monitering the Bug Forums One big help as a tester is being active on the Realms in Exile Community channel bug-reports. Here the community write bugs and problem they have. Sometimes their supposed bugs are easy to figure out, as many people tend to have a lot of other mods active and is not working well with ours, so aiding sorting out their problem is extremely helpful. But of course that's not always the case, when finding something that seems to be a genuine bug it would be helpful to trying to recreate this bug for yourself, and if indeed this is the case, then report this as an issue on Github, but if you feeling sure of your bug finding skills you may write an issue without recreating it yourself.

• Bug Finding You've played the dev version or public release and found a Bug, the most efficient way to report this would be to write an Issue on Github. This way it won't be forgotten if you for example write it on discord and later on after you posted it, some people would perhaps want to chat about an other subject, making so your bug report might disappear in a flow of 100 messages. You should try to write a thorough bug report, to the best of your ability as just writing "this is a bug" don't say much. If your feeling unsure how to phrase yourself you can always look on an open or an older closed Issue and there is also the Text Tricks page for tips on how for example posting and hide pictures with more. As of now Alpha-Testers can't label their issues, so after writing your Issue ping the Lead Tester and tell them what you want your issue label as, With it being label as a bug issue the person qualify to fix this Bug might assign themself to the task and also report it solved once it's fixed.

• Suggestion You've tested something out, a new Men at Arms, a new real tag, an event chain or a new character and you feel that something is lacking or could be improved on? Well one way to con-way this would be to write an Issue and ask it to be labeled as a Suggestion. That way if people or someone find's it a good idea they could easily assign themself to that issue to have the idea easily sorted to them.

Good Testing Layout on Issues

It's Important to use good ways to showcase what's needing tested and what needs tested when testing an Issue, going with the example bellow whom use the Pull Request/Issue 971.

Showing a proper developing phase on what the github is about. Then having a proper Testing section with proper check boxes on what's needing tested and possible a How To section to explain how new complicated mechanics works.