Difference between revisions of "How to test"
| Line 1: | Line 1: | ||
Here is a guide for testing Freeplane: | Here is a guide for testing Freeplane: | ||
| − | + | There are two stages for a Freeplane release (both stable and unstable). Each new version is uploaded to a testing area prior to release. When one or more tester confirms the version has introduced no major bugs, it will be uploaded to the Sourceforge files sections. At the moment only team members and selected testers are alerted to the pre-release (though it's not hard to find). If you want to test Freeplane here's what to do: | |
| − | + | 1. Download the [https://sourceforge.net/projects/freeplane/ latest release] | |
| − | + | 2. It may be best to create a fresh map or use a testing map. Perform as many functions as you can, via both the menus and hot keys. Particularly try out the new features. Jot down any problems or bugs you encounter and record what you were doing at the time. (Later there will be a systematic test map). | |
| − | + | 3. Report any problems via the [https://sourceforge.net/apps/mantisbt/freeplane/ bug tracker] (under Project-->Bugs) remembering to include as much information as possible, such as the behaviour you encountered, what you were going, your Freeplane and Java version, and your operating system. | |
| + | |||
| + | If you're testing a pre-release please complete the [http://freeplane.sourceforge.net/mediawiki-1.14.1/index.php/Release_smoke_test smoke test]. | ||
Revision as of 03:46, 21 October 2009
Here is a guide for testing Freeplane:
There are two stages for a Freeplane release (both stable and unstable). Each new version is uploaded to a testing area prior to release. When one or more tester confirms the version has introduced no major bugs, it will be uploaded to the Sourceforge files sections. At the moment only team members and selected testers are alerted to the pre-release (though it's not hard to find). If you want to test Freeplane here's what to do:
1. Download the latest release
2. It may be best to create a fresh map or use a testing map. Perform as many functions as you can, via both the menus and hot keys. Particularly try out the new features. Jot down any problems or bugs you encounter and record what you were doing at the time. (Later there will be a systematic test map).
3. Report any problems via the bug tracker (under Project-->Bugs) remembering to include as much information as possible, such as the behaviour you encountered, what you were going, your Freeplane and Java version, and your operating system.
If you're testing a pre-release please complete the smoke test.
