GSoC/GCI Archive
Google Code-in 2013 Haiku

Test Pe for Bugs and Issues

completed by: John Paul Aldana

mentors: Richie Nyhus-Smith, Urias McCullough, Philippe Saint-Pierre

You will be ad hoc testing Pe for bugs and other issues for this task. You will need to have the Haiku operating system installed and running in a VM or on your computer. Also you will most likely need to have HaikuPorter and possibly a relevant version of demopackage installed as well. The demopackages are packed full of sounds, images or videos that allow you to check to see if the application can play all relevant media.

You will need to test to see if you can find any bugs in the software. Try to act like a normal user and do the things that they would do with the software. Use the media found in the demopackages to help you find bugs by editing them if needed.

Do all the buttons do what they are expected to do? Is any of text partially obscured? What happens when you change the system font size? Does the software have a modern icon or does it have an old 90s style BeOS icon? Does it have a Haikuports recipe file and can HaikuPorter install it? What happens if you try to open clearly non-supported files, like say trying to play a video in a image viewer?

You will need to search the software's bug tracker to see if the bugs are known about and open new tickets for each bug on there if they are not.

You will also need to keep a journal of what features you tested and what tickets you opened. Plus it might be a good idea to take a screenshot of the bugs and issues that you find and just reference the relevant image in the journal if the bug is difficult to describe.

Then upload the journal here, plus include the links to the bugs you have submitted and any images that you have created.

Your job is to find new bugs, issues or even open enhancements tickets for new features. Therefore you can't use ones that others have already found, they have to be your own.