How to test
Freeplane Release Process
Releasing a stable or unstable version of Freeplane is a two stage process. Each new test version is uploaded to a testing area prior to release. When one or more tester confirms that the test version has introduced no major bugs, it will be uploaded as an official release to the Sourceforge files section. Otherwise, a new test version will be uploaded. At the moment only team members and selected testers are alerted when new test versions are available, but you are free to periodically check and download any new versions in the testing area.
Testing an official release
If you want to test an official Freeplane release, here's what to do:
1. Download the latest release
2. Create a fresh map or use a testing map, and perform as many functions as you can, via both the menus and hot keys. Particularly try out any new features. Jot down any problems or bugs you encounter and record what you were doing at the time. (In the future there will be a systematic test map and/or unit-tests available).
3. Report any problems via the bug tracker (under Project-->Bugs). Please include as much information as possible:
- what you were doing
- the behavior you encountered
- error or warning messages you got
- your Freeplane and Java versions
- your operating system
ALWAYS SUBMIT:
- a description of steps to reproduce the bug
- the actual results of following these steps
- the expected / desired results
Testing a test version
If you wish to test a bleeding edge test version, replace step 1 above with one of the two following options: you can either download the latest binary archive from the testing area, or you can check out the latest release from the development repository, and build it. See the How to Build Freeplane wiki page for more information on getting the source and building binaries.
Additionally, if you're testing a test version please complete the smoke test, until unit-tests are available to carry out these tests.
