Extras testing, step by step

After some weeks using extras-testing and as the first people have the devices in their hands, one complain I heard is, that the documentation on how to use extras-testing might be not sufficient for some users. This is the reason for this little overview with questions and answers around the testing repository, hoping that this will help and promote the testing activity a bit.

Why testing the applications?
A nice description about the testing-process you can find in the wiki.

Which kind of places are there to get applications and what is the difference?

There exist three different community driven repositories:

  • extras:
    This is the place where the end-user can find applications, which are ready and tested.
  • extras-testing:
    Here are applications, which might have some issues and should not be for the real end-user usage. Applications you find here are meant to be proofed by experienced users, to ensure their quality or find possible blockers. This could be you, but be aware of possible risks.
  • extras-devel:
    Applications you find here are just meant for people who know what they are doing. They can be in pre-alpha status and should not be installed by normal end-users. You should know what you are doing by enabling this repository.

I’m aware of what I’m doing now, but what are the first steps, if I want to test an application?

After creating a backup, add the extras-testing repository. Therefore open the Application Manager and follow these steps:

1. Open the menu and click on “Application Catalogues”

2. Add the extras-testing repository (Web address: http://repository.maemo.org/extras-testing)

3. If you have the  extras-devel repository enabled, disable it with the “Disabled” checkbox to check possible dependency issues:

Now I can start testing, but what to look for?

Besides the obvious problems like battery drain, crashes, performance etc. you can find here a good summary of what you should look at, if you want to test applications.

I have reached an opinion about the application, but how to continue?

1. It is necessary to have an account on maemo.org. If you don’t have already one, you can register here.

2. You find the QA queue of applications, which are in extras-testing here. Find the application you just have tested and vote for it!

I hope this makes the testing-process a bit clearer and activates the people, who are able to help to join the group of testers ;)

Advertisements

6 Responses to “Extras testing, step by step”


  1. 1 Viipottaja November 28, 2009 at 1:33 pm

    This is nice. However, can you please try to make sure this kind of advice is more regularly where it needs to be, i.e. at the source, rather than “hidden” in blogs like yours? :) ps. I have not checked if this guidance is now where it needs to be so I my comment might be moot.

  2. 2 Bratag November 28, 2009 at 11:26 pm

    Thanks for the guide and the concise description about what each repository is for and how to follow up after testing.

    I am sure that there will be a few people that say “Oh I am experienced” and brick their phone – but hopefully most people will stick within their limits and we will see some quality testing going on.

  3. 3 Ricky Cadden November 29, 2009 at 11:31 pm

    Great guide, though I wish the Maemo community would make it easier to report testing/bugs on the device itself. I realize that can all be done on the browser, but it’s not immediately obvious, IMO. Perhaps applications from the testing/devel repos should have a ‘Report Bugs’ link in the menu options or something?

    • 4 danielwilms November 30, 2009 at 8:01 am

      Hi,

      maybe you could add this idea to the brainstorm?!? Sounds interesting at least. I am working at the moment on a download client but right now it is just for end-user and extras. But I’m anyway planning to separate the back-end, which handles the communication to the server as a library. As soon as the sign-on part works it might be simple to realize something like this more easily. Help is always welcome ;) But this is connected as well to the SSO, which should come ASAP. Feel free to contact me about this, if you want to help or if you just need updates on the status of the different projects.

      Cheers Daniel

  4. 5 ossipena November 30, 2009 at 7:42 am

    Hello, I will grab the screenshots and other material to maemo wiki

    http://wiki.maemo.org/Help_testing_software

    please contact me if you want it removed from wiki. I will add your blog as a source naturally.

    • 6 danielwilms November 30, 2009 at 7:51 am

      Hi,
      great that you do that. Thanks for the support, otherwise I would have done that, but I hadn’t time on Friday to do so. But maybe you could put it as a sub-page of the existing extras-testing page like the QA checklist. E.g. Extras-testing/Step-by-step_guide or something like that? But this is just a suggestion to keep the information together.

      Thx that you help out there.

      Daniel


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s





%d bloggers like this: