mirror of
https://github.com/wesnoth/wesnoth
synced 2025-05-05 17:45:38 +00:00
9a0b95f9a0
This adds an additional `test_result` attribute to [endlevel], intended for use with the automated unit tests. This allows for the unit tests to differentiate a pass/fail result separately from scenario victory or defeat, which allows for more accurately determining the outcome of a test as well as addresses the potential, for example, for a scenario to be expect to pass because of the {SUCCEED} macro but instead passes because the scenario ended as a victory through some other method.
Additional unit tests which were the original motivation for this change are also added as part of this. They test, as much as possible, that events are executed at all, and are then also executed in the expected order.
This directory contains both the scenarios used by C++ unit tests and those which are WML unit tests. For the C++ unit tests, it is recommended to reuse the same scenario file as much as possible and just inject WML into it. Injection can be done by adding a config object containing event code and then registering that manually for game_events. WML unit tests are self-contained scenario files to test a specific area of WML. They can be implemented with the GENERIC_UNIT_TEST macro.