Getting started as a tester: Difference between revisions

From FreeMind
Jump to navigationJump to search
 
(6 intermediate revisions by 2 users not shown)
Line 2: Line 2:


FreeMind is a fairly large project with a very small development team. We need all the extra testing resources we can get, so if you want to help out, this is one of the best places to start.
FreeMind is a fairly large project with a very small development team. We need all the extra testing resources we can get, so if you want to help out, this is one of the best places to start.


# Let us know that you want to help! Visit the [http://sourceforge.net/forum/forum.php?forum_id=22101 Open Discussion Forum] and tell us.
# Let us know that you want to help! Visit the [http://sourceforge.net/forum/forum.php?forum_id=22101 Open Discussion Forum] and tell us.
# Download the latest beta release of the software [http://sourceforge.net/project/showfiles.php?group_id=7118 here].
# Download the latest beta release of the software [http://sourceforge.net/project/showfiles.php?group_id=7118 here].
# Test! Do everything you can think of to break the application, or just use it the way you plan on using it, and let us know what fails.
# Test! Do everything you can think of to break the application, or just use it the way you plan on using it, and let us know what fails.
# When there's a bug, tell us. You can report bugs in the [http://sourceforge.net/forum/forum.php?forum_id=22101 Open Discussion Forum], or put them into [http://sourceforge.net/tracker/?atid=107118&group_id=7118&func=browse SourceForge's Bug Tracker].
# When there's a bug, tell us; to learn how, see [[reporting bugs]], respecting the rules on [[Handling trackers]].
# You'll find things that you want the software to do that it doesn't do. Those aren't necessarily bugs. You can ask for new features, [http://sourceforge.net/tracker/?group_id=7118&atid=357118 here].
# You'll find things that you want the software to do that it doesn't do. Those aren't necessarily bugs. You can ask for new features, [http://sourceforge.net/tracker/?group_id=7118&atid=357118 here].
# If you are interested in helping with more advanced testing, by writing test scripts, please let us know in the [http://sourceforge.net/forum/forum.php?forum_id=22101 Open Discussion Forum] and someone will contact you about it.
# If you are interested in helping with more advanced testing, by writing test scripts, please let us know in the [http://sourceforge.net/forum/forum.php?forum_id=22101 Open Discussion Forum] and someone will contact you about it.
# Reap the rewards by having better software to work with.
# Reap the rewards by having better software to work with.


== Going further ''<<Proposal>>'' ==


===Reporting bugs===
Once you've gained some knowledge, you can help even more by following this path:
 
The most important thing you can do to help us find and fix the bugs you report, is to make sure that you give us enough information that we can reproduce the bug. Otherwise, we have no way of knowing, for sure, that we've fixed the bug you report.
 
The first thing you should do, when reporting a bug, is double-check your setup, especially if you are just getting started. Make sure you are using the correct version of the Java Runtime Environment. (Currently, FreeMind is compiled and run under Java 1.4. Some of us run it under Java 1.5,  and FreeMind 0.9.0 should work with 1.6 too) Make sure you have your Path and ClassPath variables set correctly.


You can report bugs through the [http://sourceforge.net/forum/forum.php?forum_id=22101 forum], or through [http://sourceforge.net/tracker/?atid=107118&group_id=7118&func=browse SourceForge's Bug Tracker].
# improve the [http://sourceforge.net/tracker/?atid=107118&group_id=7118&func=browse bugs reported] by "normal" users, making sure that they comply to the [[Handling trackers|rules]] and that they contain a clear description of how to reproduce the bug.
# debug the bug and find out where the bug happens in the code, it helps the developers to fix it quickly.
# suggest the required corrections yourself and transform the bug into a [http://sourceforge.net/tracker/?group_id=7118&atid=307118 patch] for the developers to integrate into the FreeMind code.
# become a [[Getting started as a developer|developer]] yourself!


Here are some things that help:
In order to do the above tasks, you'll need additional rights that you should request from one of the Project Admins listed on [http://sourceforge.net/projects/freemind FreeMind's SF page].
* The version of FreeMind you are using.
* What operating system you are running.
* The version and patch level of your OS. (For example XP Professional Service Pack 2)
* What you were trying to do when you got the failure
* A description of the failure
* Clear instructions on how to reproduce the failure
* Sometimes it helps if you send us the actual mindmap where the problem occurred.


--[[User:Rben13|Rben13]] 10:50, 3 Sep 2007 (PDT)
==See also==
* [[Handling trackers]]
* [[Reporting bugs]]


[[Category:Development]]
[[Category:Development]]

Latest revision as of 04:36, 31 December 2009

Getting started as a tester

FreeMind is a fairly large project with a very small development team. We need all the extra testing resources we can get, so if you want to help out, this is one of the best places to start.

  1. Let us know that you want to help! Visit the Open Discussion Forum and tell us.
  2. Download the latest beta release of the software here.
  3. Test! Do everything you can think of to break the application, or just use it the way you plan on using it, and let us know what fails.
  4. When there's a bug, tell us; to learn how, see reporting bugs, respecting the rules on Handling trackers.
  5. You'll find things that you want the software to do that it doesn't do. Those aren't necessarily bugs. You can ask for new features, here.
  6. If you are interested in helping with more advanced testing, by writing test scripts, please let us know in the Open Discussion Forum and someone will contact you about it.
  7. Reap the rewards by having better software to work with.

Going further <<Proposal>>

Once you've gained some knowledge, you can help even more by following this path:

  1. improve the bugs reported by "normal" users, making sure that they comply to the rules and that they contain a clear description of how to reproduce the bug.
  2. debug the bug and find out where the bug happens in the code, it helps the developers to fix it quickly.
  3. suggest the required corrections yourself and transform the bug into a patch for the developers to integrate into the FreeMind code.
  4. become a developer yourself!

In order to do the above tasks, you'll need additional rights that you should request from one of the Project Admins listed on FreeMind's SF page.

See also