Currently Online

Latest Posts

Changes in RegressionTests

Revision Differences of Revision 2

When you think your branch is ready for merging, there are two tests you can run to make sure that your code sticks to our coding style, and to test for a bunch of possible regression bugs. ¶

## Running Codecheck Manually ¶


We have codecheck rules that will help you stick to our coding style guidelines. These are run automatically whenever you compile a debug build, but they can be hard to see now, because cmake creates a lot of output around them. However, you can run the checks manually: ¶

`cmake/codecheck/CodeCheck.py src/* | grep -v "src/third_party"` ¶


## Running Regression Tests Manually ¶

Some tests can be run automatically wile compiling debug builds, but not all of them. We have some automated scenarios that will check for regression bugs. You can run all of them with ¶

`./regression_test.py -b ./widelands` ¶

or you can run just specific tests, for example: ¶

`./widelands --scenario=test/maps/lua_testsuite.wmf` ¶

Have a look at the tests directory for individual tests you can run.