Difference between revisions of "How to test"

From Freeplane - free mind mapping and knowledge management software
m (Added Categories)
m (Text replacement - "http://www.freeplane.org" to "https://www.freeplane.org")
 
(12 intermediate revisions by 7 users not shown)
Line 1: Line 1:
Here is a guide for testing Freeplane:
+
== Freeplane Release Process ==
  
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:  
+
Releasing a stable or unstable version of Freeplane is a two stage process. Each new test version is uploaded to a [https://www.freeplane.org/testversion/ 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 [https://www.freeplane.org/testversion/ testing area].
 +
 
 +
 
 +
== Testing an official release ==
 +
 
 +
If you want to test an official Freeplane release, here's what to do:  
  
 
1. Download the [https://sourceforge.net/projects/freeplane/ latest release]  
 
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).  
+
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 [https://sourceforge.net/apps/mantisbt/freeplane/ 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 [https://www.freeplane.org/testversion/ testing area], or you can check out the latest release from the development repository, and build it.  See the [[How_to_build_Freeplane|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 [https://www.freeplane.org/wiki/index.php/Release_smoke_test smoke test], until unit-tests are available to carry out these tests.
 +
 
  
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.  
+
== Testing the development version ==
 +
If you want to test the next Freeplane version developpers are working on (also called preview version), please refer to [https://www.freeplane.org/wiki/index.php/Freeplane_1.2.x-1.3.x use and download preview version].
  
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].
 
  
[[Category:Testing]] [[Category:Advanced_Users]] [[Category:Team_Freeplane]]
+
[[Category:Coding]]

Latest revision as of 18:57, 18 November 2018

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.


Testing the development version

If you want to test the next Freeplane version developpers are working on (also called preview version), please refer to use and download preview version.