Testcases for Ares 0.2

[Renegade]

@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:

• Acknowledged is not identical to Confirmed - Confirmed states the report has been confirmed, whereas Acknowledged only stated that someone from the team had seen them. Acknowledged has no equivalent on LP and was autoconverted to New.
  
• Feedback is equivalent to Incomplete, period. Opinion is an entirely different status, best explained through the words of LP itself:
  

  [...] It is not uncommon on Launchpad to have a bug that deals with an issue that a developer cannot resolve. In Launchpad, we offer a couple of bug statuses that allow a developer to close a bug report without actually doing what is requested in the report: these are Won’t Fix and Invalid.
  
  Often, though, there may still be a discussion. Won’t Fix and Invalid are useful for the developer, and the project, to know that they don’t need to schedule time for a fix. However, they can sometimes — rightly or wrongly — be seen as an attempt to close down to discussion.
  [...]
  Opinion says: there’s a difference of opinion around this bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed.

• Expired bugs are fundamentally the reporter's fault, not the developers'. The primary defining characteristic of an expired bug is that it has been in "Incomplete" state for a long time. It has nothing to do with lack of activity over a long time, but with lack of information over a long time. Quoth Launchpad:

  Launchpad consider bugs ready for expiry if it appears that they have been abandoned. It considers a bug to be abandoned if:

  • it has the "Incomplete" status
    
  • the last update was more than 60 days ago
    
  • it is not marked as a duplicate of another bug
    
  • it has not been assigned to anyone
    
  • it is not targeted to a milestone.
    

  Basically, if there's not enough information to start working on a bug, and there's no sign it's being dealt with anyway, and it just sits there, it expires.
  If the reporter just went ahead and provided more information, it wouldn't expire.
• Won't fix means exactly what it says...which issues are using it otherwise?

See also

• On LP bug statuses
  
• On Opinion in particular
  
• Bug expiry