Donation

Help us to pay our server!
(: Consider a donation :)



Social Media

  • Facebook
  • Google+

Latest Posts

TestingBranches

Testing Development Builds

If you don't know how to write code, make art or translate, you can still help us by testing the development version of Widelands.

If you can't compile Widelands yourself

If you wish to help with testing Widelands and do not know how to compile, you can still help us by downloading a development build and reporting any bugs you find.

If you can compile

If you know how to compile Widelands or think you can learn, you can help us with testing branches that haven't been included in the current development version yet.

Selecting a branch to test

You can find a list of branches that need testing in the code reviews section on Launchpad. We will sometimes also ask for testing on the forums when we have bigger projects that need thorough testing, or if we're changing the design of something.

Getting the branch

After selecting a branch to test, Launchpad will show you the branch addresses for downloading the branch. They look like:

lp:~widelands-dev/widelands/branchname

The command that we need to use is:

bzr branch <branch_address>.

Open a terminal, use the cd command to get to where you want to keep your branches and then run bzr branch lp:~widelands-dev/widelands/branchname. If this doesn't work, try bzr branch lp:~widelands-dev/widelands/branchname branchname.

More detailed explanations on how to use Bazaar are available in our BzrPrimer.

Compiling and running the branch

For testing, we will want to create a development build. These are the terminal commands that you would most typically run:

cd <branchname>
./compile.sh
./widelands

For more information on how to compile, see Building Widelands.

Testing the branch

Once you have finished compiling your development build, it is time to do the actual testing.

Manual testing

Read the description of the change, then click on anything that you think might be affected in any order that you can think of - be creative. Depending on what the change is, you might also want to test both a single player and a multiplayer game and play with the settings. Some changes will also affect the tutorials, campaigns and scenario maps.

Automated testing and codecheck

We have an automated test suite that you can run with development builds. We have some checks that run over the code itself to make sure that it adheres to our code style. See RegressionTests on how to run these tests.

Reporting your findings

  • If we asked for testing on the forums, you can report your findings in the forum thread.
  • If you tested a ready-made development build, best report the bug in our bug tracker on Launchpad. Search the bugs first to make sure that it hasn't already been reported, and include the Widelands revision number. If you don't want to open an account on Launchpad, you can also tell us about the bug in the forums.
  • If you tested a branch that's undergoing code review, report your findings in the branch's Merge Proposal in the code reviews section on Launchpad.
  • When working on a Merge Request on Launchpad and everything has checked out, use the drop-down box below the comment window to set your vote to "Approve".

See also How to Write a Good Bug Report.