Testcases for Ares 0.2 - Printable Version +- Renegade Projects Network Forums (https://forums.renegadeprojects.com) +-- Forum: Inject the Battlefield (https://forums.renegadeprojects.com/forumdisplay.php?fid=60) +--- Forum: Ares General Discussion (https://forums.renegadeprojects.com/forumdisplay.php?fid=19) +--- Thread: Testcases for Ares 0.2 (/showthread.php?tid=2147) |
Testcases for Ares 0.2 - SoundMachine - 01.07.2012 Hello everyone! With this topic I would like to ask if there are some solid test cases that need to be tested for the ''ready to test'' brances. Basicly I am looking for bugs that are 'fixed' but need to be verified. If I may be honest, the bugtracker is really hard to understand at a first glimpse and it does not really describe testable scenarios for me, just a list of bugs that needs to be fixed. I hope I can provide some help! Regards, SoundMachine P.S: Please don't go hard on me since this is my first post and I only want to help RE: Testcases for Ares 0.2 - Nighthawk - 01.07.2012 Hello SoundMachine. Here's a quick rundown of what the statuses on Launchpad's bugtracker mean: On the left hand side is the priority of a bug. Should be obvious what that means - important things are high, lessly-important things are lower. On the right hand side is the status of a reported bug. There are a few of these:
Any current bugs that have been fixed and need verified should be under the "Fix Committed" heading. However, we also need to investigate the general stability of Ares - how various features interact, whether the game throws a tantrum if you use a certain combination of stuff, and so on. If you encounter such issues, check to see if they've been reported, and if they haven't, report them yourself. At the moment, there aren't many untested specific bugs left - stability testing is the major thing that needs dealt with. Lastly, if you can confirm to us that things are working as they should be, then also let us know about that too. This doesn't go on the bugtracker, and instead goes in a LaunchPad question topic here. Later Edit: This is more for existing testers rather than you, SoundMachine, but if you've been using our old tracker, this could apply to you too. For any major fans of the original tracker, the new statuses are slightly different to the old ones, but here's how they relate:
RE: Testcases for Ares 0.2 - Renegade - 07.07.2012 @SoundMachine: There still haven't been secondary confirmations/answers to the questions on the list of 0.2 test branch questions to answer. It would be much appreciated if you could look into that. As for general testing, as well as the question of why a list of "testable scenarios" is missing, please see this previous post by me. While the sentiment expressed in that post regarding lists of things to test remains the same, that does not mean that we're opposed to structured testing. Feel free to take the lead and come up with an organized approach. The more people you can mobilize, the better. Nighthawk can create a mailing list for the Ares Testing Corps if one is needed, and there's an Ares wiki at github. Ultimately, though, if I may be honest, I don't see how the bug tracker is "really hard to understand"... It's a bug tracker. It tracks bugs. You go to it, it shows you a list of bugs. If you want to see more bugs, there's a search box at the top and pagination at the bottom. You have sort controls and the ability to filter by status or tag at the right, and "Report a bug" is, in bold, within the first 200px of the page. To see a bug's details, click on its title. Is there any problem in particular you're having? @Nighthawk: Your status-explanations are unfortunately incorrect:
See also |