Difference between revisions of "Category:Testing"
m (→Applications: updated links)
|Line 120:||Line 120:|
== Applications ==
== Applications ==
= Support =
= Support =
Revision as of 16:02, 22 August 2009
This is the coordination page for the LXDE Testing Project. We always want to over you good quality and well tested software, but to do so, we need you. We try to find as much bugs as possible, but we can't find every bug, because every computer is set up different. By testing LXDE, you can help to make LXDE more stable. If you want start testing applications, you have to know where to start, that's what this pages are for.
- 1 General Informations
- 2 Applications needed
- 3 Get the application
- 4 Error handling
- 5 Compiling
- 6 Testing
- 7 Special Informations for the applications
- 8 Support
- 9 Links
When you want to test an application you will have to do the tasks, described. First you will have to get the needed software for testing, then you need the application you want to test. When you got the aplication, you have to compile it and then test it. When you found a bug, you'll have to fill in a bug report, if the bug not already exists. Please have a look at the #Special Informations for the applications.
When you test an application, you have to get the latest sources. To do so you need (mostly, if not described diffrent) Subversion (svn) then you will need the build tools provided by your distribution, with automake, if this it packaged seperatly. Finnaly for testing you'll need gdb, the GNU Debugger.
- Build Tools
- GNU Debugger
pacman -S subversion base-devel gdb
Please also have a look at this page for more information on building applications.
Get the application
Have a look at the #Special Informations for the applications for some applications, like libfm and pcmanfm.
First of all you should get the latest code from svn. To do so type in the following
svn co https://lxde.svn.sourceforge.net/svnroot/lxde/trunk/ ./lxde
into a Terminal. You also can use a script for this.
#!/bin/bash # svn_co_lxde.sh # autor maces if [ -z $1 ] then xterm -e $0 copy else echo "starting" echo "------------------" svn co https://lxde.svn.sourceforge.net/svnroot/lxde/trunk/ ./lxde echo "------------------" echo "(program exited with code: $?)" echo "Press return to continue" #to be more compatible with shells like dash dummy_var="" read dummy_var fi exit
The script opens xterm and execute the command above. Make sure to make it executable (chmod 755 ./svn_co_lxde.sh). You now should have the latest code in ./lxde.
Get only one application
If you only want to download one application, you simply have to edit the command in the script above like that:
svn co https://lxde.svn.sourceforge.net/svnroot/lxde/trunk/lxmusic ./lxde/lxmusic
If you arn't sure what adress to use, have a look at the #Special Informations for the applications.
If there are any errors while compiling or testing the application, conntact the developers in IRC or on the mailinglist (not in the forum). Don't post the commandline output in the chat, use a nopaste service instead, for example paste.org. In the Mail it's no problem to paste the output, of course. Report errors like that for all further errors you'll get, If there is no developer online, or doesn't have time, or the developer ask you for that, use the tracker on sf.net and create a bug report. Please be as verbose as possible here and of course speak english.
Create a bug report
If you want to create a bug report, navigate your browser to . Now click on create a new bug report. Fill in the formular and be as verbose as possible in the description. Have a look at the extra hints in the testing topic below. Now click on add. Now you'll have to wait until your bug report is assigned to an developer and gets fixed. Check the comments if the developer needs more information from you, to fix this bug.
Now the first difficult part, compiling the source to an executable application and install it. To do so, you first have to open a terminal in your applications directory:
Now you should run autogen and configure:
Errors should be reported, of course. Check the special informations for extra compiling options for your application. Now continue with building the application:
make sudo make install
Specially during the compiling process, there can be much errors, report them to as descriped above. If everything went well, you are now ready to test the fresh compiled application.
Now you should run the application. But not run it only from terminal, use gdb for it. So do the following:
cd /usr/local/bin/ gdb <application>
Now test as many functions of the application as possible. Or test the functions a developer asked you for. If you find out, that something went wrong, very unespected or the application even crached or freeze, do the steps described below.
What to do if a bug appear
Press control+C to terminate the application, if it's not already terminated and you see "(gdb)". Now type "bt". The informations you get are very important for the developers please attach them to the informations in Error handling.
Special Informations for the applications
Here you'll find speciall informations for the applications, such as other adresses, or special compilling options.
You can get help on the IRC irc.oftc.net #lxde
This category currently contains no pages or media.