{"shas":[["91b6d246fe6a1d612560bbdf32dfbd1d6bc8ec7c","5deb016be0f77dc524fe5f19b55ed343d31d3c66@gmail.com","Be more paranoid about the environment of each unit test\n\nSet the global database reference on each test run. When running all\ntests, the game tests set this reference too.\nClear the ProductionLine cache in the beginning of each test. Clearing\nit at the end is pretty optimistic, as we don't know what code has run\nbefore this test.","squiddy"],["a729e07911dac19ed9a236a060a1d396285b1e16","5deb016be0f77dc524fe5f19b55ed343d31d3c66@gmail.com","Be even more paranoid about the environment of game tests\n\nsetup/teardown of function based tests can't pass arguments to the test, or\nkeep a reference somewhere. If a test fails, we need to reset the session under\nall circumstances, otherwise we break the rest of the tests. The global\ndatabase reference has to be set each time too. Unit tests also use it,\nand we can't predict the order tests run (we should not rely on it anyway).\n\nWhile we're at it, we cut down on some boilerplate and let the decorator\nhandle the creation of a new session. We could use this later to define\ndifferent preconditions for a test, e.g. only a new session, or a\nprebuild settlement, different map etc.","squiddy"],["fee3120aca29671dcf48d7d52867065d9eed1076","5deb016be0f77dc524fe5f19b55ed343d31d3c66@gmail.com","Add simple tests for Lumberjack, Hunter and Fisherman","squiddy"]],"ref":"refs/heads/master","size":3,"head":"fee3120aca29671dcf48d7d52867065d9eed1076","push_id":34181577}