upstream/wesnoth
1
0
Fork 0
mirror of https://github.com/wesnoth/wesnoth synced 2024-09-20 07:51:33 +00:00
Code Issues Packages Projects Releases Wiki Activity
7380885226
wesnoth/wml_test_schedule

1007 lines
28 KiB
Plaintext
Raw Normal View History

add sanity checks for unit test mechanism also, reorganize the test schedule file
2014-05-11 05:57:49 +00:00
#
# Sanity checks of the unit test system
#
0 test_return
1 test_return_fail
0 test_assert
1 test_assert_fail
Add a Lua unit_test module only available in [test] scenarios (#5708) It contains fire_wml_menu_item along with a set of new assert functions
2021-04-26 01:04:50 +00:00
0 test_lua_return
1 test_lua_return_fail
8 test_lua_return_victory
7 test_lua_return_defeat
0 test_lua_assert
1 test_lua_assert_fail
1 test_lua_assert_fail_in_fired_event
0 test_lua_assert_compare
1 test_lua_assert_compare_fail1
1 test_lua_assert_compare_fail2
1 test_lua_assert_compare_fail3
1 test_lua_assert_compare_fail4
1 test_lua_assert_compare_fail5
1 test_lua_assert_compare_fail6
1 test_lua_assert_compare_fail7
1 test_lua_assert_compare_fail8
1 test_lua_assert_compare_fail9
0 test_lua_assert_errors1
1 test_lua_assert_errors2
1 test_lua_assert_errors3
0 test_lua_assert_errors4
1 test_lua_assert_errors5
0 test_lua_assert_errors6
1 test_lua_assert_errors7
0 test_lua_assert_errors8
1 test_lua_assert_errors9
add sanity checks for unit test mechanism also, reorganize the test schedule file
2014-05-11 05:57:49 +00:00
2 empty_test
Add a unit test for wesnoth.current.synced_state The edge-case of calling evaluate_single within an unsynced event was surprising, and I'm not sure it's correct. However, as we're about to release the 1.16 branch I think it's better to include that as a test that the API doesn't change during the stable branch.
2021-07-05 10:31:15 +00:00
0 test_end_turn
Document last batch of unit tests.
2022-11-30 22:42:04 +00:00
9 there_is_no_test_with_this_name
Add berserk weapon special abilities tests (#8973) Changes: * CHECK_STRIKES macro now takes a comma-delimited list of strike counts for when units have a different number of strikes for different weapons, and updates the existing usage in the attacks tests * Fixed a typo in the attacks_zero test * Adds tests for berserk as a weapon special ability. Berserk's handling differs from attacks as a weapon special ability: * A value less than 1 is treated as effectively infinite rounds of combat (undocumented) * The cumulative attribute is handled differently - in some cases it sums the values instead of using the highest single value whereas for attacks it always uses the highest single value Also now exclude data/tests/ from scons pot-update since it was hitting the argument limit for number of arguments to a script.
2024-06-16 01:20:54 +00:00
0 check_strikes_once
10 check_strikes_twice_fail
Add a unit test for wesnoth.current.synced_state The edge-case of calling evaluate_single within an unsynced event was surprising, and I'm not sure it's correct. However, as we're about to release the 1.16 branch I think it's better to include that as a test that the API doesn't change during the stable branch.
2021-07-05 10:31:15 +00:00
#
# The synchronisation mechanism
#
fixup wml_test_schedule the break_replay test now successfully fails.
2014-05-14 01:04:19 +00:00
4 break_replay_with_lua_random
add fixed_lua_random_replay test
2014-05-14 01:27:17 +00:00
0 fixed_lua_random_replay_with_sync_choice
Handle out-of-bounds side numbers in Lua's sync.evaluate_multiple Change the C++ to show a Lua error instead of crashing with an assert.
2022-12-06 16:09:59 +00:00
9 test_synced_side_number
Add a unit test for wesnoth.current.synced_state The edge-case of calling evaluate_single within an unsynced event was surprising, and I'm not sure it's correct. However, as we're about to release the 1.16 branch I think it's better to include that as a test that the API doesn't change during the stable branch.
2021-07-05 10:31:15 +00:00
0 test_synced_state
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
#
wml test for cve-2018-1999023 this test whether we succesfully prevent the exceution and parsing of precompiled lua chunks, which can be used to break the lua sandbox. This test does not cover all affected functions in particular not the ai code that loads lua chunks. (cherry-picked from commit 6b13a63bb0999e1c494a4236a5d565306db5a0b9)
2018-07-24 00:11:40 +00:00
# Security test
#
0 cve_2018_1999023
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
9 cve_2018_1999023_2
wml test for cve-2018-1999023 this test whether we succesfully prevent the exceution and parsing of precompiled lua chunks, which can be used to break the lua sandbox. This test does not cover all affected functions in particular not the ai code that loads lua chunks. (cherry-picked from commit 6b13a63bb0999e1c494a4236a5d565306db5a0b9)
2018-07-24 00:11:40 +00:00
#
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
# Test Check Victory (If this isn't working other tests may have dubious value)
#
2 check_victory_basic_timeout
1 check_victory_basic_macro_check
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 check_victory_basic
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
1 check_victory_basic_fail
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 check_victory_basic_two
8 check_victory_basic_ai
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
1 check_victory_basic_ai_fail
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 check_victory_basic_ai_two
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
1 check_victory_one_no_units_fail_one
1 check_victory_one_no_units_fail_two
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 check_victory_one_no_units
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
1 check_victory_two_no_units_fail_one
1 check_victory_two_no_units_fail_two
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 check_victory_two_no_units
8 check_victory_always_one
8 check_victory_always_two
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
1 check_victory_always_no_units_fail
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 check_victory_always_no_units
Add unit tests for check victory function Mainly focused on defeat_condition field right now... woudl be good to add some that test victory_when_enemies_defeated.
2014-05-22 21:21:53 +00:00
1 check_victory_always_fail
1 check_victory_never_fail_one
1 check_victory_never_fail_two
1 check_victory_never_fail_three
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 check_victory_never_pass
7 check_victory_never_ai_fail
add sanity checks for unit test mechanism also, reorganize the test schedule file
2014-05-11 05:57:49 +00:00
#
Add a unit test for the preprocessor's #ifdef handling This one's surprising, but it's the behavior of 1.16, so add a test for the current behavior even though I wonder if it should change in 1.17.
2022-11-22 15:13:03 +00:00
# Preprocessor
#
0 test_preprocessor_ifdef_in_arg
#
add sanity checks for unit test mechanism also, reorganize the test schedule file
2014-05-11 05:57:49 +00:00
# WML API tests
#
rename wml unit tests tests should have helpful names and not numbers
2014-05-11 05:38:09 +00:00
0 two_plus_two
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
10 two_plus_two_fail
rename wml unit tests tests should have helpful names and not numbers
2014-05-11 05:38:09 +00:00
0 order_of_nested_events
add a wml unit test for {CLEAR_VARIABLE} macro
2014-12-29 05:39:14 +00:00
0 test_clear_one
0 test_clear_two
add unit test for basic unit map functionality
2014-05-17 02:23:48 +00:00
0 test_unit_map
rename wml unit tests tests should have helpful names and not numbers
2014-05-11 05:38:09 +00:00
0 unit_spawns_at_nearest_vacant_hex
0 units_offmap_goto_recall
Add a unit test for the behavior of [unit]id= recalling units Answers a question raised in PR #4999. This also passes on 1.14.
2020-11-19 07:24:44 +00:00
0 recall_by_unit_tag
add test_move unit tests
2014-05-17 01:25:23 +00:00
0 test_move
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
9 test_move_fail_1
9 test_move_fail_2
9 test_move_fail_3
9 test_move_fail_4
9 test_move_fail_5
9 test_move_fail_6
register the tests of {MOVE_UNIT} macro with the test schedule
2014-10-18 20:02:14 +00:00
0 test_move_unit
WIP: Test [move_unit] moving back to the starting hex
2019-12-12 07:41:55 +00:00
0 test_move_unit_in_circle
Add a unit test for [move_unit]location_id with an occupied hex (cherry picked from commit ba1767f8b90a4ca34cf8ef2abbc03cf98fd488f8)
2022-03-22 13:54:36 +00:00
0 test_move_unit_to_occupied_location
Rewrite the WML unit test for sighted events The old version's [event]name=sighted had a {RETURN} statement in it, which meant the test stopped on the first sighting. Most of the test wasn't testing anything.
2021-05-03 22:31:12 +00:00
0 sighted_on_move
Replace deprecated share_maps and share_view with share_vision. Closes #6496. share_maps=yes -> share_vision=shroud share_view=yes -> share_vision=all
2022-02-08 12:42:12 +00:00
0 move_skip_no_sighted_no_share_vision
0 move_skip_ally_sighted_no_share_vision
0 move_skip_all_sighted_no_share_vision
0 move_skip_no_sighted_yes_share_vision
0 move_skip_ally_sighted_yes_share_vision
0 move_skip_all_sighted_yes_share_vision
unit tests for giving gold in prestart
2014-05-26 23:06:00 +00:00
0 set_gold_in_prestart_one
0 set_gold_in_prestart_two
add tests of modify_turns tag
2014-05-27 00:02:05 +00:00
0 modify_turns_one
0 modify_turns_two
0 modify_turns_three
0 modify_turns_four
add replace_schedule in prestart test
2014-05-27 00:14:16 +00:00
0 replace_schedule_prestart
add test of [modify_unit] facing= attribute
2014-05-27 03:34:48 +00:00
0 modify_unit_facing
Remove the fast path of [modify_unit] (#6223) Always use the "slow path", because it stores and unstores the unit, triggering the desired side effects of unstoring a unit. Fixes issue #5133, and tests that with the new unit test. Fixes bug #4978, that changing the facing wasn't updating the display. This corresponds to 1.16's commit 13c5d8a96ead8d2a7f0435f60b8ec7f7e0af0972, that commit merely disabled the fast path to be a minimal change.
2021-11-05 20:39:38 +00:00
0 modify_unit_which_recall_list
Fix modify_unit recall_cost indexing issue Fix issue #7159 apply_to recall_cost to use 0 based side index instead of 1 based side Add test for issue #7159 modify_unit recall_cost
2023-04-21 11:32:02 +00:00
0 modify_unit_recall_cost
Fix [store_unit]'s stored coordinates for recalls Units on the recall list might have x,y coordinates that are on the map, which therefore need to be replaced with "recall,recall" within [store_unit]. The existing code created a temporary variable, changed the coordinates, and then returned the unchanged original instead of the temporary. Add a new test that `[put_to_recall_list]` followed by `[modify_unit]` doesn't move the unit back to the map. (cherry picked from commit 096d8aba1474e9c6583d240e7eedbcd66957f327)
2022-01-09 12:44:43 +00:00
0 put_to_recall_and_modify
Fix #8460 [effect] apply_to=variation (#8475) * Fix #8460 [effect] apply_to=variation Previously the code could apply the variation effects last, so that codes like ``` [effect] apply_to=variation .. [/effect] [effect] apply_to=hitpoints heal_full=yes [/effect] ``` Would not set the unit hitpoints to the new variations hitpoints because the variation effect was applied after the healing effect. In 1.16 this worked because healing was applied a little too often but that lead also to bugs like #8342 * f prev * f prev * f prev * f prev * f prev * Create modification_effect_type_variation.cfg * Update wml_test_schedule
2024-03-07 00:25:59 +00:00
0 effect_type_variation_full_heal
0 effect_type_variation_no_heal
unit tests for defining custom event handlers in events and firing
2014-06-21 20:58:40 +00:00
0 event_handlers_in_events_1
0 event_handlers_in_events_3
0 event_handlers_in_events_2
Convert some fail-on-success unit tests to pass-on-success (#4597)
2019-11-25 13:28:03 +00:00
0 event_handlers_in_events_4
unit tests for defining custom event handlers in events and firing
2014-06-21 20:58:40 +00:00
0 event_handlers_in_events_5
0 event_handlers_in_events_6
0 event_handlers_in_events_7
0 event_handlers_in_events_8
Add event unit tests for dynamic filters and names (#6785)
2022-06-22 02:25:01 +00:00
0 event_handlers_in_events__delayed
0 event_handlers_in_events__delayed__dynamic_name
0 event_handlers_in_events__delayed__dynamic_filter
0 event_handlers_in_events__immediate
0 event_handlers_in_events__immediate__dynamic_name
0 event_handlers_in_events__immediate__dynamic_filter
Add more unit tests for nested event handlers and a few other things
2021-04-08 01:28:00 +00:00
0 event_remove_test
0 event_repeat_test
Add unit tests for auto-scoped variables in events
2021-04-08 01:28:27 +00:00
0 event_test_auto_variables_side_turn
0 event_test_auto_variables_xy
0 event_test_auto_variables_units
0 event_test_auto_variables_weapons
0 event_test_auto_variables_damage
0 event_test_auto_variables_owner
Add some event filter tests
2021-04-09 13:53:08 +00:00
0 event_test_filter_condition
0 event_test_filter_side
0 event_test_filter_unit
[1.17] add [filter_ability] in [filter] events and [effect]remove_ability and [filter_ability_active] in [filter] events see https://forums.wesnoth.org/viewtopic.php?p=681371#p681371 in forum the type of ability used is also filtered.
2022-10-14 18:49:17 +00:00
0 event_test_filter_ability
Add tests for ranges and negative values in ability filters Changed to use "-" instead of ".." as the separator by octalot, but I believe newfrenchy83 prefers "..".
2023-08-06 12:14:40 +00:00
0 event_test_filter_ability_interval_number
0 event_test_filter_ability_neg_value
[1.17] add [filter_ability] in [filter] events and [effect]remove_ability and [filter_ability_active] in [filter] events see https://forums.wesnoth.org/viewtopic.php?p=681371#p681371 in forum the type of ability used is also filtered.
2022-10-14 18:49:17 +00:00
0 event_test_filter_ability_no_match
Add tests for ranges and negative values in ability filters Changed to use "-" instead of ".." as the separator by octalot, but I believe newfrenchy83 prefers "..".
2023-08-06 12:14:40 +00:00
0 event_test_filter_ability_no_match_neg_prefix
add [filter_wml] to filter abilities like [experimental_filter_ability], [experimental_filter_ability_active] or [overwrite][experimental_filter_specials] adding a sub-filter should make it possible to take into account the sub_tags of the abilities in the checking
2024-05-18 13:29:16 +00:00
0 event_test_filter_ability_wml
0 event_test_filter_ability_wml_no_match
[1.17] add [filter_ability] in [filter] events and [effect]remove_ability and [filter_ability_active] in [filter] events see https://forums.wesnoth.org/viewtopic.php?p=681371#p681371 in forum the type of ability used is also filtered.
2022-10-14 18:49:17 +00:00
0 event_test_filter_ability_active
0 event_test_filter_ability_active_inactive
repair detects non-existent default attribute value Fix https://github.com/wesnoth/wesnoth/issues/7923 .when we want to detect an ability with value=0-20 and an ability with add=15 is present, this is detected because the system assigns a value of 0 when 'value' is not present, and so the system matches abilities that do not use 'value' or even no numerical value at all. it is therefore necessary to decide that the absence of an attribute is a non-correspondence to the criteria.
2023-09-29 12:49:16 +00:00
0 event_test_filter_ability_with_value_by_default
0 event_test_filter_ability_no_match_by_default
Modify 'apply_to' in an ability filter to do an inclusion check for resistance abilities Instead of needing to contain the exact string from the ability, 'apply_to' in the filter is now taken as a comma-separated list, where all elements need to be present in the ability. For example if we filter for apply_to=fire,arcane given an ability [resistance]apply_to=arcane, fire, cold, it will match. For an ability [resistance]apply_to=arcane, impact, cold, this will not match because 'fire' is missing.
2024-06-07 16:08:43 +00:00
0 event_test_filter_ability_apply_to_resistance
add 'ability_id_active' attribute to filter (#5739) Add 'ability_id_active' attribute to filter Until now, only the type of ability could be filtered with activity, and id only for unit who have ability, same if she's inactive.
2021-05-03 19:38:05 +00:00
0 test_ability_id_active
0 test_ability_id_not_active
Add some event filter tests
2021-04-09 13:53:08 +00:00
0 event_test_filter_attack
Add a test for attack_filter with melee-only vs ranged-only units A new test of what happens when a unit with only a ranged weapon fights a unit with only a melee weapon. This commit is just the test, it depends on the engine fix in a previous commit. This only tests the filtering so far. There should probably be another additional test to check what the combat results are, however that would need an ability such as the Deep Elves' Stardust that passively affects the amount of damage taken. It can't be tested with Slows, as that needs the defender to hit with a weapon first.
2023-04-17 09:54:40 +00:00
0 event_test_filter_attack_no_defense
check alternative_type and replacement_type when filtering on type Also move them from being attributes of [damage] to [damage_type], to avoid infinite recursion when determining what the damage type should be.
2023-11-10 22:35:57 +00:00
0 event_test_filter_attack_type
Fix a bug in [event][filter_attack] when trying to use special_id/type_active to detect a special whose activity is conditional. (#7509) When we try to trigger an event conditioned by the use of a special whose activity is subject to a condition, we cannot use special_active because the specials are always considered inactive. Additionally, abilities used as weapons possessed or taught by a leadership are also not detectable in [event][filter_attack]. This PR is there to remedy this double problem. Also remove matches_special_filter and directly use matches_filter.
2023-04-11 17:34:28 +00:00
0 event_test_filter_attack_specials
More unit tests for attack_filter Add `first_time_only=no` to some existing tests, and verify that events that should only trigger once do trigger exactly once. A new test of `[filter_attack]` when an event lacks attack data. In testing, I found that it used to trigger a warning that I thought was useless code, and had removed during 88439d6427a81a6b131acd8b0f7bf04b2d981d71's review. I think removing it is still good, at the time that the filter was checked it would have warned "attempt to filter attack for an event with no attack data."
2023-04-13 19:51:43 +00:00
0 event_test_filter_attack_on_moveto
Fix a bug in [event][filter_attack] when trying to use special_id/type_active to detect a special whose activity is conditional. (#7509) When we try to trigger an event conditioned by the use of a special whose activity is subject to a condition, we cannot use special_active because the specials are always considered inactive. Additionally, abilities used as weapons possessed or taught by a leadership are also not detectable in [event][filter_attack]. This PR is there to remedy this double problem. Also remove matches_special_filter and directly use matches_filter.
2023-04-11 17:34:28 +00:00
0 event_test_filter_attack_opponent_weapon_condition
New ability recursion tests using a four cycle Using four abilities instead of two means the C++ checking_tag mechanism needs to handle multiple values, or needs to be supported by recursion counting. The branching test lets one level of recursion finish, and then tries to go deeper. This tests for bugs where a recursion detection tool in the engine gets its count reset when exiting one level of recursion.
2024-06-22 14:07:34 +00:00
9 event_test_filter_attack_opponent_weapon_condition_no_triggered
9 event_test_filter_attack_student_weapon_condition
Unit tests for the new filter options
2021-04-11 22:10:59 +00:00
0 event_test_filter_wfl
0 event_test_filter_wfl2
0 event_test_filter_lua_serializable
0 event_test_filter_lua_dynamic
9 event_test_filter_lua_dynamic_break_save
Unit tests for each way of assigning an action to an event handler
2021-04-11 05:33:55 +00:00
0 event_test_action_wml
0 event_test_lua
0 event_test_lua_advanced
0 event_test_lua_repeat
9 event_test_lua_break_save
Fix load_string() ignoring the passed chunk name (#6794) Complete with a unit test! The test results in PASS_BY_VICTORY if it fails, which is a bit weird, but it does work.
2022-06-24 05:49:28 +00:00
0 test_lua_name
Add documentation to more WML unit tests.
2022-10-23 19:15:58 +00:00
0 filter_vision_all_no_side
0 filter_vision_all_side_2
0 filter_vision_all_side_4
0 filter_vision_side_1_side_4
0 filter_vision_side_2_side_4
0 filter_vision_side_3_side_4
0 filter_vision_side_4_side_1
0 filter_vision_side_4_side_3
0 filter_vision_side_4_not_side_2
0 filter_vision_not_side_5
Add unit tests for the Lua shroud functions
2021-07-25 22:18:40 +00:00
0 test_shroud_init
0 test_shroud_place_wml
0 test_shroud_place_lua
0 test_shroud_place_lua_data
Update the shroud unit tests and add a few more for cases new in 1.16
2021-07-26 00:00:41 +00:00
0 test_shroud_override_all
0 test_shroud_override_data
Add unit tests for the Lua shroud functions
2021-07-25 22:18:40 +00:00
0 test_shroud_remove_wml
0 test_shroud_remove_lua
Update the shroud unit tests and add a few more for cases new in 1.16
2021-07-26 00:00:41 +00:00
0 test_shroud_remove_lua_data
Add unit tests for the Lua shroud functions
2021-07-25 22:18:40 +00:00
0 test_shroud_modify_wml
0 test_shroud_modify_lua
Add test for #3663
2018-10-27 20:40:03 +00:00
0 scatter_units
Add documentation to more WML unit tests.
2022-11-01 03:06:39 +00:00
0 dave_has_ally_bob
0 dave_has_enemy_alice
0 dave_not_has_ally_steve
0 dave_has_enemy_sides
0 not_dave_has_ally_charlie
fix bug #23130 (xp modifier not working), add unit tests Reverts commit e85c37e161795794e1ae6d2c6b59377a16988c10 which was an error. I chose to use a scoped_pointer this time around because the definition of play_controller should not actually depend on the complete definition of unit_type.
2015-01-02 23:03:24 +00:00
0 xp_mod_1
0 xp_mod_2
0 xp_mod_3
Added a new unit test for [role]
2015-06-10 20:07:28 +00:00
0 test_role_1
0 test_role_2
0 test_role_3
Improved the [role] unit test A new unit test, called 'test_role_lua' was added, to ensure that the [role] tag could be used from Lua. Also, in the first unit test the types list is stored in a variable, to ensure that variable substitution works as intended
2015-06-13 19:23:40 +00:00
0 test_role_lua
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
0 events-test_nonfilterable
0 events-test_filterable1
0 events-test_filterable2
0 events-test_filterable3
0 events-test_victory
0 events-test_defeat
0 events-test_die
Add tests for pre_attack event.
2022-08-09 04:18:43 +00:00
0 events-test_pre_attack_base
0 events-test_pre_attack_change_weapon
Fix [store_unit_defense] and add [store_unit_defense_on], add unit test The existing tag has a confusing name - it returns the chance to be hit rather than the defense, for example 30 would be returned for a unit on 70% terrain. The new tag returns a higher-is-better value.
2020-10-28 18:35:52 +00:00
0 test_store_unit_defense_on
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
9 test_store_unit_defense_deprecated
Fix [special_note] duplication when unstoring units The movetype's special notes were becoming a new note for the individual unit. Clean up the documentation on some of movetype's functions, as they had documentation in both the .hpp and the .cpp.
2022-11-21 19:57:23 +00:00
0 special_note_from_movetype
0 special_note_individual_unit
Add basic achievements functionality. (#7237) * Add basic achievements functionality. This reads the mainline achievements.cfg and then all the achievements of each installed add-on. This is intentionally handled separately from other WML loading so that: a) All achievements and their status are able to be displayed on the main menu right after Wesnoth starts and regardless of which add-ons are active. b) Add-ons can add additional achievements to other content, whether UMC or mainline. For example, a modification that adds more achievements for mainline campaigns. Marking something as achieved is handled by the new [set_achieved] tag and whether an achievement has been completed can be checked via [has_achievement]. There is no attempt to prevent people from manually editing which achievements they've accomplished. NOTE: These are *not* in any way related to Steam achievements!
2023-01-21 16:32:45 +00:00
0 has_achievement
Add new attacks_used key to [attack] (#7351)
2023-02-04 18:55:04 +00:00
0 test_movement_used
0 test_attacks_used
Prevent duplicate advancements from being added to unit type (#7743) * Add myself to Miscellaneous Contributors * types: Add unit tests over adding advancements
2023-07-09 03:08:10 +00:00
0 no_duplicate_advancements
0 add_advancement
Add tests for [harm_unit] This is testing experience=yes and experience=no, with the expectation that some new values for that attribute will be added afterwards. Adds a new generic macro ASSERT_UNIT_HP_XP. Looking thorugh the ability tests, ASSERT_UNIT_HP (without the XP) could be a heavily-used macro, but it wouldn't be used by this particular commit, so I'm not adding it in this commit.
2024-01-02 11:35:51 +00:00
0 harm_unit_survivable_experience_no
Support [harm_unit]experience values kill/attack/defend/fight/yes/no (#8231)
2024-01-18 10:32:18 +00:00
0 harm_unit_survivable_experience_unset
Add tests for [harm_unit] This is testing experience=yes and experience=no, with the expectation that some new values for that attribute will be added afterwards. Adds a new generic macro ASSERT_UNIT_HP_XP. Looking thorugh the ability tests, ASSERT_UNIT_HP (without the XP) could be a heavily-used macro, but it wouldn't be used by this particular commit, so I'm not adding it in this commit.
2024-01-02 11:35:51 +00:00
0 harm_unit_survivable_experience_yes
Support [harm_unit]experience values kill/attack/defend/fight/yes/no (#8231)
2024-01-18 10:32:18 +00:00
0 harm_unit_kill_no_experience_attack
0 harm_unit_kill_no_experience_attack_defend
0 harm_unit_kill_no_experience_attack_kill
0 harm_unit_kill_no_experience_defend
0 harm_unit_kill_no_experience_defend_kill
0 harm_unit_kill_no_experience_fight
0 harm_unit_kill_no_experience_kill
0 harm_unit_kill_no_experience_no_attack_defend_kill
Add tests for [harm_unit] This is testing experience=yes and experience=no, with the expectation that some new values for that attribute will be added afterwards. Adds a new generic macro ASSERT_UNIT_HP_XP. Looking thorugh the ability tests, ASSERT_UNIT_HP (without the XP) could be a heavily-used macro, but it wouldn't be used by this particular commit, so I'm not adding it in this commit.
2024-01-02 11:35:51 +00:00
0 harm_unit_kill_no_experience_no
Support [harm_unit]experience values kill/attack/defend/fight/yes/no (#8231)
2024-01-18 10:32:18 +00:00
0 harm_unit_kill_no_experience_unset
Add tests for [harm_unit] This is testing experience=yes and experience=no, with the expectation that some new values for that attribute will be added afterwards. Adds a new generic macro ASSERT_UNIT_HP_XP. Looking thorugh the ability tests, ASSERT_UNIT_HP (without the XP) could be a heavily-used macro, but it wouldn't be used by this particular commit, so I'm not adding it in this commit.
2024-01-02 11:35:51 +00:00
0 harm_unit_kill_no_experience_yes
Support [harm_unit]experience values kill/attack/defend/fight/yes/no (#8231)
2024-01-18 10:32:18 +00:00
0 harm_unit_kill_split_experience_attack
0 harm_unit_kill_split_experience_attack_defend
0 harm_unit_kill_split_experience_attack_kill
0 harm_unit_kill_split_experience_defend
0 harm_unit_kill_split_experience_defend_kill
0 harm_unit_kill_split_experience_fight
0 harm_unit_kill_split_experience_kill
0 harm_unit_kill_split_experience_no_attack_defend_kill
Add tests for [harm_unit] This is testing experience=yes and experience=no, with the expectation that some new values for that attribute will be added afterwards. Adds a new generic macro ASSERT_UNIT_HP_XP. Looking thorugh the ability tests, ASSERT_UNIT_HP (without the XP) could be a heavily-used macro, but it wouldn't be used by this particular commit, so I'm not adding it in this commit.
2024-01-02 11:35:51 +00:00
0 harm_unit_kill_split_experience_no
Support [harm_unit]experience values kill/attack/defend/fight/yes/no (#8231)
2024-01-18 10:32:18 +00:00
0 harm_unit_kill_split_experience_unset
Add tests for [harm_unit] This is testing experience=yes and experience=no, with the expectation that some new values for that attribute will be added afterwards. Adds a new generic macro ASSERT_UNIT_HP_XP. Looking thorugh the ability tests, ASSERT_UNIT_HP (without the XP) could be a heavily-used macro, but it wouldn't be used by this particular commit, so I'm not adding it in this commit.
2024-01-02 11:35:51 +00:00
0 harm_unit_kill_split_experience_yes
0 harm_unit_kill_yes_experience_no
Support [harm_unit]experience values kill/attack/defend/fight/yes/no (#8231)
2024-01-18 10:32:18 +00:00
0 harm_unit_kill_yes_experience_unset
Add tests for [harm_unit] This is testing experience=yes and experience=no, with the expectation that some new values for that attribute will be added afterwards. Adds a new generic macro ASSERT_UNIT_HP_XP. Looking thorugh the ability tests, ASSERT_UNIT_HP (without the XP) could be a heavily-used macro, but it wouldn't be used by this particular commit, so I'm not adding it in this commit.
2024-01-02 11:35:51 +00:00
0 harm_unit_kill_yes_experience_yes
Add some unit tests for [terrain_mask]
2021-02-28 02:24:47 +00:00
# Terrain mask tests
0 test_terrain_mask_simple_nop
0 test_terrain_mask_simple_set
0 test_terrain_mask_simple_underlay
0 test_terrain_mask_simple_overlay
0 test_terrain_mask_simple_name
Rename test_terrain_mask_simple_name_fail to ..._ignore I want to reserve names ending `_fail` or containing `_fail_` for tests that do not expect the `TEST_PASS` status.
2023-05-06 08:29:55 +00:00
0 test_terrain_mask_simple_name_ignore
Add some unit tests for [terrain_mask]
2021-02-28 02:24:47 +00:00
0 test_terrain_mask_align_odd_on_odd
0 test_terrain_mask_align_odd_on_even
0 test_terrain_mask_align_even_on_odd
0 test_terrain_mask_align_even_on_even
0 test_terrain_mask_align_raw_on_odd
0 test_terrain_mask_align_raw_on_even
0 test_terrain_mask_deprecated_border_no
0 test_terrain_mask_deprecated_border_yes
0 test_terrain_mask_rule_basic
Document last batch of unit tests.
2022-11-30 22:42:04 +00:00
0 test_terrain_mask_file
add sanity checks for unit test mechanism also, reorganize the test schedule file
2014-05-11 05:57:49 +00:00
#
add a wml unit test for lua dofile
2014-12-05 20:30:12 +00:00
# LUA
#
0 lua_dofile
add a unit test for wesnoth.require
2014-12-07 04:32:29 +00:00
0 lua_require
add a unit test for lua get_sides return object
2014-12-26 06:07:57 +00:00
0 lua_get_sides
fixup wesnoth.wml_conditionals, add unit tests
2015-04-10 18:16:21 +00:00
0 test_wml_actions
0 test_wml_conditionals
Added unit tests about which WML tag names Lua API accepts
2018-01-17 21:23:13 +00:00
0 lua_wml_tagnames
Support negative numbers in ranges Adds support for using these in the weapons and ability filters: * "-1", which was previously treated as an parse error (no number before the separator). * "-3--1" * "-infinity" as the lower number in the range, provided a different upper number is given. This treats "-infinity" (with no other number), "-infinity--infinity", "infinity" (with no other number) and "infinity-infinity" as errors. It seems unlikely that someone would intend to use a filter that can't match any reasonable number. The range "-infinity-infinity" will be parsed successfully. I don't see a use case for that, but nor do I see a reason to add extra C++ to reject it. However, it's not added to the schema, as I think it's good for the schema to give a warning when someone creates a filter which will accept every value (including accepting the default, so "-infinity-infinity" accepts the unset value too). Includes new unit tests for the C++ and the Lua stringx.parse_range functions. The next commit adds more WML tests, but is kept separate to credit the author. This started as a change to move common filter functions from unit.cpp to somewhere that they could be reused for other config-based filters. In the process a missing feature was found and added, the move is still included in a single Git commit because the move was required in order to make these functions accessible to the Boost unit tests. Two CodeBlocks project files additionally get src/utils/any.hpp added, which was in one of them but missing from the other two. I noticed because these are alphabetically at the start of the src/utils file list. Thanks to @CelticMinstrel for the review comments and Xcode project updates.
2023-08-06 11:51:49 +00:00
0 test_parse_range
Add a unit test for scoped arrays The existing test for scoped vars is both copied and renamed.
2023-01-23 16:52:49 +00:00
0 test_scoped_array
0 test_scoped_scalar
Add the Plan Unit Advance modification to mainline.
2021-01-30 07:42:03 +00:00
0 as_text
Add a versions userdata for a cleaner way to compare and manipulate game versions
2020-09-28 03:28:05 +00:00
0 test_lua_version_api
add a wml unit test for lua dofile
2014-12-05 20:30:12 +00:00
#
test [store_locations], and try to characterize [find_path]
2014-05-28 00:28:05 +00:00
# Pathfinding
#
0 store_locations_one
Allow '1-infinity' in ranges, and tighten the schema's validation of ranges Fixes #4253. The schema's validation of ranges now rejects negative numbers, because the C++ code doesn't support them (both before and after this commit): * utils::parse_range("-7") will return {0,0}, because std::stoi("") throws invalid_argument. * src/map/location.cpp will parse it as -7, but that will never match an on-map coordinate
2019-08-20 16:18:34 +00:00
0 store_locations_range
Add [find_path] option "nearest_by", and simple_find_path test Adding this is issue 2 of #4177, changing the behavior when [find_path] is given a SLF which matches multiple hexes. The map and tests here should be easy enough for manually editing them. It duplicates some of the functionality of the existing characterize_pathfinding tests, however those tests need their expected values to be calculated and can't be changed by hand. '''nearest_by''': {DevFeature1.15|2} possible values "movement_cost" (default), "steps", "hexes". If the [destination] SLF matches multiple hexes, the one that would need the least movement points to reach may not be the one that's closest as measured by '''hexes''', or closest as measured by steps, from the starting point. Behavior in 1.14 depended on which hex was checked first.
2019-07-22 10:44:44 +00:00
0 simple_find_path
disable a wml unit test that occasionally takes too long "characterize_pathfinding_one"
2014-10-10 22:14:33 +00:00
# This test occasionally takes too long... (FIXME): 0 characterize_pathfinding_one
re-enable some tests related to pathfinding that were disabled In relation to bug #23188 and PR # 364
2015-03-01 03:49:03 +00:00
0 characterize_pathfinding_reach_1
0 characterize_pathfinding_reach_2
0 characterize_pathfinding_reach_3
0 characterize_pathfinding_reach_4
0 characterize_pathfinding_reach_5
0 characterize_pathfinding_reach_6
0 characterize_pathfinding_reach_7
test [store_locations], and try to characterize [find_path]
2014-05-28 00:28:05 +00:00
#
Add unit tests for movement and vision costs Includes changing the terrain costs, and aliased terrains. Can be cleanly cherry-picked to 1.14.
2019-07-20 16:01:14 +00:00
# Movement types, and modifying them
#
0 test_elf_movement
0 test_orc_movement
0 test_elf_fast_cave_movement
0 test_elf_fast_hills_movement
0 test_elf_fast_cave_and_hills_movement
0 test_orc_fast_cave_movement
0 test_orc_fast_forest_movement
0 test_elf_slow_cave_movement
0 test_elf_longsighted_movement
0 test_orc_longsighted_movement
0 test_elf_longsighted_fast_cave_movement
0 test_elf_fast_cave_longsighted_movement
0 test_elf_vision
0 test_elf_fast_cave_vision
0 test_elf_fast_hills_vision
0 test_elf_longsighted_cave_vision
0 test_elf_longsighted_cave_and_hills_vision
0 test_elf_longsighted_cave_slow_cave_vision
Add a unit test for resistances (using the standard 6 damage types) I'm working on a bugfix for the [resistance_defaults] tag, for which the unit test is going to be out-of-tree until we support some method of testing it without affecting other tests. The version here is the part of that which can be in-tree, because it doesn't change the core unit's stats.
2020-11-27 12:39:53 +00:00
0 test_resistances
Unit tests for [effect]apply_to=movement and [effect]apply_to=vision These would also pass on 1.14, checking that movement does affect vision if and only if vision hasn't been modified separately. The comments talk about an [effect]also_apply_to_vision= attribute which hasn't been added yet, the aim of these tests is to regression test that attribute when it is added.
2021-01-14 02:43:41 +00:00
# [effect]apply_to=movement and [effect]apply_to=vision
0 effect_move_affects_vision
0 effect_move_ignores_vision
Add attribute apply_to_vision to [effect]apply_to=movement When processing [effect]apply_to=movement, if apply_to_vision is 'yes' (which is the default) then the vision points will change by the same amount. Previously, it sometimes affected vision and sometimes didn't; for most cases where it makes a difference, I expect it to be a change from unanticipated behavior to expected behavior. Please refer to the new unit test added in this commit for more detailed docs; that test is also a rough draft for the Wiki update needed when this merges. The reason it sometimes affected vision was that the special value of -1 vision points was interpreted as "use the value of the max movement points instead". The special value of -1 is still supported and frequently used, and refactor that is out of scope for this commit - it's easy to check when the code path changed in this commit is used, however it's considerably more complex to find all routes that create a unit with vision set to -1. I'm expecting one add-on, Rebirth In Nature, to need a large update for this; as well as a trivial change needed to the Add Creature Pack. There are several mods that have their own handling for vision, recalculate the values frequently, and are expected to continue working as before, as they'll just overwrite any changes that the engine makes. * Proper Flying Mod / Proper Vision Mod * LotI * Blessed Altar Mod * Shards Era's `CALCULATE_WEAPONS_ONLY` macro * Castle of Evil Spirit Rebirth In Nature is an RPG-style campaign that expects the player's unit to have vision separated from movement along with right-click menus that change the character's movement, this will probably need `apply_to_vision=no` in many places. OTOH, its `item_id=mobility` uses `apply_to=movement` followed by `apply_to=vision` to implement in 1.14 what this change will make default behavior in 1.16. There are a few sharpshooter units which have vision better than their movement. If given a buff which boosts their movement, this will give them a buff to vision too; likely a change towards expected behavior. * Archaic Era's Royal Ranger * Ageless Era's Royal Ranger and Dwarvish Forest Sniper * Eastern Europe at War's Yacht and Great Yacht * Era of More Units's Lone Wolf * Southernerns has several sharpshooters * WWII Era has several sharpshooters * War of Dominions has some guard towers with very low movement Silver Age has abilities that modify vision based on time-of-day, but unlike the Proper Flying Mod and LotI these are done by adding and removing objects that add or subtract one vision point, these should be unaffected by this change. Unrelated to that, it declares values for `[unit_type]vision=` even when the value is the same as max moves - like the sharpshooters this means that buffs to their movement wouldn't have buffed their vision but now do. There are few units with vision less than movement. Generally these seem to be missile weapons that are represented as units, and they probably won't meet any apply_to=movement statements - even if a movement power-up is available, the player would probably choose a different unit. The Add Creature Pack has two creatures (the Cactose Elder and Carnivore Fatal Plant) that have reduced vision, along with AMLAs that increase those units' movement; these AMLAs will need to use `apply_to_vision=no`. These two creatures are used in Castle of Evil Spirit, but they won't get enough experience to get an AMLA there. Fixes #3356.
2021-01-14 07:34:46 +00:00
0 effect_move_separated_vision
Unit tests for [effect]apply_to=movement and [effect]apply_to=vision These would also pass on 1.14, checking that movement does affect vision if and only if vision hasn't been modified separately. The comments talk about an [effect]also_apply_to_vision= attribute which hasn't been added yet, the aim of these tests is to regression test that attribute when it is added.
2021-01-14 02:43:41 +00:00
0 effect_vision
Make [store_reachable_locations]range=vision calculate vision Previously it calculated max movement, and then added the adjacent hexes. This version should correctly handle: * units with vp different to max mp * units with vision costs different to movement costs * jamming by enemy units Draft changelog entry for this: * `[store_reachable_locations]range=vision` now calculates vision, instead of using movement costs and max movement points (issue #4179)
2021-04-14 10:40:15 +00:00
# [store_locations]
0 store_reachable_locations_vision
Add unit tests for movement and vision costs Includes changing the terrain costs, and aliased terrains. Can be cleanly cherry-picked to 1.14.
2019-07-20 16:01:14 +00:00
#
Add wesnoth.colors[name].pango_color and use it in the multiplayer turns-over dialog
2021-04-27 13:02:17 +00:00
# General information queries
#
0 test_lua_colors
0 test_lua_colors_hexadecimal
#
add unit test for berzerk + firststrike interaction
2014-05-17 03:53:28 +00:00
# Attack calculations & codepath tests
add sanity checks for unit test mechanism also, reorganize the test schedule file
2014-05-11 05:57:49 +00:00
#
Separate unit test results from scenario victory/defeat. 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.
2020-04-02 22:15:11 +00:00
8 alice_kills_bob
8 bob_kills_alice_on_retal
8 alice_kills_bob_levelup
8 bob_kills_alice
8 alice_kills_bob_on_retal
8 alice_kills_bob_on_retal_levelup
rename wml unit tests tests should have helpful names and not numbers
2014-05-11 05:38:09 +00:00
0 test_grunt_tod_damage
add some [time_area] unit tests
2015-01-05 07:34:09 +00:00
0 test_time_area_damage
0 test_time_area_prestart
More unit test documentation.
2022-11-22 01:41:05 +00:00
0 test_berserk_firststrike
Add documentation to more WML unit tests.
2022-10-23 19:15:58 +00:00
0 feeding_on_living
0 feeding_on_dead
fix [firststrike] special with apply_to=opponent crashes Wesnoth 1.17.x (#6574) As reported on the forum in https://forums.wesnoth.org/viewtopic.php?p=672374#p672374 If a unit with "last strike" ([firststrike] special with apply_to=opponent, on any of its attacks) was targeted by other unit for attack, wesnoth crashed. Fix similar problems for other weapon specials like poisons, when two users of specials with apply_to=opponent fought, one fighter only could be poisoned or slowed. * Add a unit test for poison * Add a unit test for firststrike and laststrike
2022-04-08 00:30:14 +00:00
0 firststrike_and_laststrike
Refactor the backstab unit test Based on Pentarctagon's documentation addition, and also improving the encapsulation of the test to take a boolean value for whether the ability should be active instead of the expected damage total.
2022-01-22 15:50:33 +00:00
0 backstab_active_with_accomplice_behind_bob
Backstab unit tests: check that backstab works in a free-for-all The units on the outsides of a backstab don't have to be allied to each other, they just have to be enemies of the victim. That's hardcoded into the AI via attack.cpp's backstab_check() function, hence a unit test to check that WEAPON_SPECIAL_BACKSTAB activates in that situation. Add a new map with 4 sides all on separate castles. This is a variation of the generic 2p unit test map, extended in the south with a horizontal reflection of existing map. Add a MAP_FILE argument to COMMON_KEEP_A_B_C_D_UNIT_TEST, because it's the same setup except for the map file.
2024-01-24 19:49:41 +00:00
0 backstab_active_with_free_for_all
Refactor the backstab unit test Based on Pentarctagon's documentation addition, and also improving the encapsulation of the test to take a boolean value for whether the ability should be active instead of the expected damage total.
2022-01-22 15:50:33 +00:00
0 backstab_inactive_with_triangular_formation
0 backstab_inactive_with_statue_behind_bob
0 backstab_inactive_with_bobs_ally_behind_bob
Unit tests for [drains], [poison] and [slow], with apply_to=opponent Slightly different to PR #6582, which was the 1.16 version of this. The five lines that were labelled `preserving known bug` are changed to test that it's been fixed. Here `apply_to=opponent` means that the weapon special gives the opponent the ability, the unit that should get poisoned or slowed is the unit that has the weapon special. There's a known bug in 1.16, that `apply_to=opponent` check the wrong unit to see it it's `unpoisonable`, `undrainable` etc. It also checks the wrong unit to see if it's already poisoned or slowed, so a battle between two units that both have reverse-poison results in at most one being poisoned. Most of the credit for this is Newfrenchy's, as he's already written a fix and a WML based test. This commit uses a Lua test instead to test more combinations of statuses. This adds a `COMMON_KEEP_A_B_UNIT_TEST` macro, which is a counterpart to the `GENERIC_UNIT_TEST` macro that starts the leaders next to each other, ready to attack. The `A_B` is because I'm planning a multiple-side variant too. There's no test for [petrify], as simulate_combat doesn't provide a stat for it. This tests only 3 of the 6 abilities whose behavior changed in 650f70405ff. My thoughts on testing the others are: * [firststrike]'s test is in 650f70405ff. * [drains], [poison] and [slow] are tested here. * [petrify] ends combat, it's also not exposed in simulate_combat's stats. * [plague] triggers after combat ends.
2022-04-07 20:46:34 +00:00
0 reflexive_drains
0 reflexive_poison
0 reflexive_slow
Unit tests for changing abilites with filters in [event]name=attack The existing backstab tests' common code is moved to a utility file for reuse in other tests, because it can be used to check whether a weapon special was active during the damage calculations. Git's diff can show a lot of lines being deleted, but that's just because it's showing a file being copied, and then half of each copy being removed.
2022-10-02 08:28:46 +00:00
0 replace_special_with_filter_in_attack_event_active
0 replace_special_with_filter_in_attack_event_inactive
Add WML unit test for unupgradable (#3336) * Add WML unit test for unupgradable * Follow [do_command] requirements (cherry picked from commit 739df85e1d0e7f382bc5c5664d29c36204ba8d0f)
2018-07-22 21:51:22 +00:00
0 swarm_disables_upgrades
fix [firststrike] special with apply_to=opponent crashes Wesnoth 1.17.x (#6574) As reported on the forum in https://forums.wesnoth.org/viewtopic.php?p=672374#p672374 If a unit with "last strike" ([firststrike] special with apply_to=opponent, on any of its attacks) was targeted by other unit for attack, wesnoth crashed. Fix similar problems for other weapon specials like poisons, when two users of specials with apply_to=opponent fought, one fighter only could be poisoned or slowed. * Add a unit test for poison * Add a unit test for firststrike and laststrike
2022-04-08 00:30:14 +00:00
0 poison_opponent
add 'unslowable' and 'unpetrifiable' status (#5788)
2021-05-27 17:35:49 +00:00
0 unslowable_status_test
0 unpetrifiable_status_test
Add a second unit test for TEST_FORCE_CHANCE_TO_HIT It should work even when the macro appears in the same event as the attack; this tests that. The new one uses the COMMON_KEEP macro, but I've left the existing one unchanged, except for the renaming.
2024-09-13 06:10:44 +00:00
0 test_force_chance_to_hit_macro_nested
0 test_force_chance_to_hit_macro_toplevel
Add exclusive unit traits handling similar to require_amla (#7109)
2023-01-19 18:49:39 +00:00
0 trait_exclusion_test
0 trait_requirement_test
[1.17] add [filter_ability] in [filter] events and [effect]remove_ability and [filter_ability_active] in [filter] events see https://forums.wesnoth.org/viewtopic.php?p=681371#p681371 in forum the type of ability used is also filtered.
2022-10-14 18:49:17 +00:00
0 test_remove_ability_by_filter
Add priority and filter to overwrite specials (#7746) using overwrite_specials alone means that we have only two possibilities, either one_side is chosen and in this case if the ability used as a weapon carrying the attribute is applied to the unit (apply_to=self), the other abilities are the same type applied also to 'self' not carrying the attribute will be overwritten, but those of the opponent with apply_to=opponent will be kept in the list; or else both_sides is chosen and all abilities of the same type that do not carry the attribute will be overwritten. To be able to use the attribute in abilities like [damage] for example, it is necessary to be able to be even more selective as for a 'charge' type leadership with multiply=2.5 but which must not be combined with the classic charge and without overwriting the aute [damage] as backstab, [overwrite_filter] to only match damage with apply_to=both and active_on=offense is then interesting. adding priority allows you to select that it ability can use its overwrite_specials attribute while the others can be overwritten in the same way as an ability without the attribute. Finally, this system makes it unnecessary to limit the use of the attribute to abilities used as weapons but also to special weapons.
2023-10-08 15:09:31 +00:00
0 test_overwrite_specials_filter
Add a unit test for a weapon-special activating mid-attack A weapon with poison, which does extra damage to poisoned opponents. This tests that the weapon-special's filter is checked on each strike, instead of being tested once and then cached during the battle. (cherry picked from commit 55aa8b44cfd561d0d97f254312f395cebc8ccc6e)
2024-06-06 17:39:49 +00:00
0 damage_recalculation_mid_attack
add a 'replacement_type' and 'alternative_type' attribute in [damage] special or ability who modify the type of attack used (#7865) At the suggestion of @stevecotton, I propose a special 'replacement_type' and 'alternative_type' attribute capable of modifying the type of attack used when the conditions are met. Also make Holy water combine arcane damage with native type of weapon Like holy water imbued ordinary weapon, it's seem logic what arcane damage dominant what if more efficient what original type(water can't altered pierce or blading of spear or sword)
2023-10-25 13:10:52 +00:00
0 damage_type_test
check alternative_type and replacement_type when filtering on type Also move them from being attributes of [damage] to [damage_type], to avoid infinite recursion when determining what the damage type should be.
2023-11-10 22:35:57 +00:00
0 damage_type_with_filter_test
add a 'replacement_type' and 'alternative_type' attribute in [damage] special or ability who modify the type of attack used (#7865) At the suggestion of @stevecotton, I propose a special 'replacement_type' and 'alternative_type' attribute capable of modifying the type of attack used when the conditions are met. Also make Holy water combine arcane damage with native type of weapon Like holy water imbued ordinary weapon, it's seem logic what arcane damage dominant what if more efficient what original type(water can't altered pierce or blading of spear or sword)
2023-10-25 13:10:52 +00:00
0 damage_secondary_type_test
fix tag_name check deficiencies The tag_name check is deficient for two reasons: 1.when apply_to=both is used, in the case of [damage_type] [filter_opponent][filter_weapon]type= will check the modified type for application to the owner and the original type for application to the opponent, hence a risk of infinite recursion, especially if [filter_self][filter_weapon]type= is used in the same weapon. 2. in the case of apply_to=attacker/defender, the check for [filter_attacker/defender] must take into account both the value of the variable is_attacker but also the application AFFECT_SELF/OTHER, otherwise in the case apply_to=defender with [filter_defender][filter_weapon]type=, and[filter_attacker][filter_weapon]type= otherwise we end up in the same configuration as for apply_to=both Finally tag_name is renamed check_if_recursion to mean that this variable is used to ensure that a recursion cannot be set up even if https://github.com/wesnoth/wesnoth/commit/743b146efc1e9c643a601317de491dcadffc760b prevents it from causing a crash but with an error log
2024-07-22 14:22:39 +00:00
0 damage_type_apply_to_both_filter_self_opponent
0 damage_type_apply_to_attacker_filter_attacker_defender
New ability recursion tests using a four cycle Using four abilities instead of two means the C++ checking_tag mechanism needs to handle multiple values, or needs to be supported by recursion counting. The branching test lets one level of recursion finish, and then tries to go deeper. This tests for bugs where a recursion detection tool in the engine gets its count reset when exiting one level of recursion.
2024-06-22 14:07:34 +00:00
9 event_test_filter_damage_type_recursion
9 four_cycle_recursion_branching
9 four_cycle_recursion_by_id
9 four_cycle_recursion_by_tagname
Fix recursion ability count version (#9296) I use the same method what in master for weapon special recursion.
2024-09-07 14:45:26 +00:00
9 ability_cycle_recursion_by_id
9 filter_self_ability_cycle_recursion_by_id
9 adjacent_abilities_recursion_by_id
Fix attack::damage_type bug for ability resistance When [damage_type] is used but the opponent uses the resistance ability against the added type, the ability filter only detected the original type and the new type was not affected.
2024-04-04 16:01:36 +00:00
0 negative_resistance_with_two_attack_types
0 positive_resistance_with_two_attack_types
0 taught_resistance_with_two_attack_types
Select alternative damage type based on opponent resistances If two [damage_type]alternative_type= are used with two different types, the chosen type displayed in the pre-combat window will be the one to which the opponent is most vulnerable. That type will then also be used in the attack if it is stronger than the original/replacement_type. In the sidebar (report) all alternative_types are displayed. --------- Co-authored-by: Gunter Labes <soliton@wesnoth.org>
2024-04-21 11:05:03 +00:00
0 taught_resistance_with_three_attack_types
Add some more unit test documentation. Also split some larger tests into multiple smaller tests.
2022-11-12 05:44:37 +00:00
0 swarms_filter_student_by_type
0 swarms_effects_not_checkable
0 filter_special_id_active
0 filter_ability_special_id_active
0 filter_special_id_not_exists
Create test for special_id_active in the style of eoma_beam (#7713) Test created to verify that special_id_active does not work in 1.16.0. https://github.com/inferno8/wesnoth-Era_of_Magic/issues/30 https://github.com/inferno8/wesnoth-Era_of_Magic/pull/54
2023-07-04 09:28:39 +00:00
0 special_id_active_lua_function
Add some more unit test documentation. Also split some larger tests into multiple smaller tests.
2022-11-12 05:44:37 +00:00
0 leadership_when_other_has_special
0 leadership_when_other_has_no_special
0 effect_increase_attacks
0 opponent_weapon_has_no_special
0 opponent_weapon_has_special
0 student_teacher_are_same
Add a test for formulas in taught abilities Originally by gfgtdf, this was cherry-picked from gfgtdf's PR #7589, with modifications. COMMON_KEEP_A_B_UNIT_TEST gains support for optional args SIDE1_LEADER and SIDE2_LEADER.
2023-06-24 19:20:54 +00:00
0 teacher_damage_formula
Add unit tests for weapon-special calculations Covers the math for [attack]add=, [attack]divide=, [attack]multiply= and [attack]sub=. The behavior is the same in 1.16. * 5 + 2 = 7 * 5 - 3 = 2 * 5 + 2 - 3 = 2. Yes it does, that's half of why this unit test exists ... * 5 + 2 + 3 = 8 * 5 + 3 + 2 = 8 * 5 + 2 - (-3) = 7 * 3 * 3.34 = 10 * 3 * 3.334 = 9. ... and that's the other half of why this unit test exists.
2022-12-28 13:40:46 +00:00
# Math operations in ability or specials tags
0 special_calculation_add
0 special_calculation_add2_add3_cumulative
0 special_calculation_add3_add2_cumulative
0 special_calculation_add_multiply_combined
0 special_calculation_add_multiply_separated
0 special_calculation_add_sub_combined
0 special_calculation_add_sub_cumulative
0 special_calculation_add2_sub_minus3_cumulative
0 special_calculation_add_sub_separated
0 special_calculation_add_sub_with_ids
0 special_calculation_divide
0 special_calculation_divide_float_2dp
0 special_calculation_divide_float_3dp
0 special_calculation_divide_multiply_combined
0 special_calculation_divide_multiply_separated
0 special_calculation_multiply_float_2dp
0 special_calculation_multiply_float_3dp
0 special_calculation_sub
Test calculations of abilities with add and sub Fix a typo in the add_sub_separated test, because it was testing exactly the same code as add_sub_cumulative. Add two new tests and clarify documentation, because in these tests the order of the abilities determines whether the add or sub value is used, it isn't that sub always overrides add.
2024-09-07 11:50:55 +00:00
0 special_calculation_sub_add_cumulative
0 special_calculation_sub_add_separated
Add unit tests for weapon-special calculations Covers the math for [attack]add=, [attack]divide=, [attack]multiply= and [attack]sub=. The behavior is the same in 1.16. * 5 + 2 = 7 * 5 - 3 = 2 * 5 + 2 - 3 = 2. Yes it does, that's half of why this unit test exists ... * 5 + 2 + 3 = 8 * 5 + 3 + 2 = 8 * 5 + 2 - (-3) = 7 * 3 * 3.34 = 10 * 3 * 3.334 = 9. ... and that's the other half of why this unit test exists.
2022-12-28 13:40:46 +00:00
0 special_calculation_sub2_sub3_cumulative
0 special_calculation_sub3_sub2_cumulative
0 test_add_in_leadership_abilities
0 test_sub_in_leadership_abilities
Unit tests for deterministic unit facings
2014-05-27 15:30:13 +00:00
#
# Deterministic unit facing tests
0 recruit_facing_enemy_one
0 recruit_facing_enemy_two
0 recruit_facing_leader
0 recruit_facing_center
add lua function "fire_wml_menu_item" and unit tests for menu items this commit also changed slightly the way that wml menu events are synced. previously they were run via "run_in_synced_context", now they are run via "run_in_synced_context_if_not_already", which makes it safe to fire them from lua (a synced context).
2015-01-06 01:34:12 +00:00
#
# Interface tests
#
0 test_wml_menu_items_1
Document last batch of unit tests.
2022-11-30 22:42:04 +00:00
0 test_wml_menu_items_2
add lua function "fire_wml_menu_item" and unit tests for menu items this commit also changed slightly the way that wml menu events are synced. previously they were run via "run_in_synced_context", now they are run via "run_in_synced_context_if_not_already", which makes it safe to fire them from lua (a synced context).
2015-01-06 01:34:12 +00:00
0 test_wml_menu_items_3
Added some conditional unit tests
2015-04-02 21:31:13 +00:00
#
# Conditional tests
#
0 check_conditionals_1
0 check_conditionals_2
Fix SUF $this_unit only working within [filter_wml]
2015-09-19 04:16:29 +00:00
# Standard Unit Filter tests
0 filter_this_unit_wml
0 filter_this_unit_tl
Separate unit test statuses for WML exceptions and strict warnings (#4599) This is part of working out whether a subset of the "fail" tests could be run in one Wesnoth instance. To run a test that returns TEST_FAIL_BROKE_STRICT with any other test would require a mechanism to reset lg::broke_strict()'s flag. All tests that fail with an {ASSERT} will also set the lg::broke_strict() flag, the tests with the new status are only those that would pass without the strict flag. In the SUF tests, change a test from fail-on-success to breaks-strict, rename the formula tests and add some comments. The rename is because "fai" is "Formula AI", an obsolete name for WFL.
2019-12-22 18:11:48 +00:00
0 filter_this_unit_formula
0 filter_formula_unit
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
9 filter_formula_unit_error
Add tests for [store_locations] with an SUF Prompted by a discussion over [filter_weapon][not] when a unit has no usable weapon.
2024-08-16 18:35:33 +00:00
0 store_locations_with_unit_filter
0 store_locations_and_or_not_unit_filter
Implement [break], [continue], [return] tags (they take no arguments)
2015-09-17 21:46:41 +00:00
# Interrupt tag tests
0 check_interrupts_break
0 check_interrupts_return
0 check_interrupts_continue
0 check_interrupts_break_global
Add unit tests for [break] and [return] during [fire_event] Fixes #7084.
2022-11-02 10:45:54 +00:00
0 check_interrupts_break_nested_event
0 check_interrupts_return_nested_command
0 check_interrupts_return_nested_event
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
9 check_interrupts_continue_global
Fix erroneous handling of [break]/[continue] in [elseif]
2015-09-23 04:25:12 +00:00
0 check_interrupts_elseif
0 check_interrupts_case
Finally fix all the [for] issues. Probably. (With unit tests to back it up!) - Fixes [for]step=0 - Fixes [for]start,stop=0,0 - Fixes [for]start,end,step=0,1,-1 - Probably fixes several other things too
2015-10-06 16:40:12 +00:00
# For-loop tests
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
9 forloop_all_zero
9 forloop_step_zero
Finally fix all the [for] issues. Probably. (With unit tests to back it up!) - Fixes [for]step=0 - Fixes [for]start,stop=0,0 - Fixes [for]start,end,step=0,1,-1 - Probably fixes several other things too
2015-10-06 16:40:12 +00:00
0 forloop_once_positive
0 forloop_once_negative
0 forloop_twice_matched
0 forloop_twice_unmatched
0 forloop_empty_array
0 forloop_array
0 forloop_array_reverse
0 forloop_step_large_positive
WML unit tests for simple aspects
2016-03-13 05:37:11 +00:00
0 forloop_step_large_negative
Add WML unit tests for [for] tag
2017-06-22 02:18:24 +00:00
0 for_defaults
0 for_start2
0 for_end2
0 for_end2_step2
0 for_end-2
0 for_end-2_step-2
Support [foreach]array=this_item, nested loops using the default name Since a0ee38a49, the inner this_item was still in scope when the inner loop writes changed data back to the outer loop's variable, which meant that changes were silently ignored. A lot of the changes in wml-flow.lua are just indentation because of the extra block.
2023-01-23 16:52:49 +00:00
0 foreach_mutate_nested
WML unit tests for simple aspects
2016-03-13 05:37:11 +00:00
# AI Config Parsing tests
0 test_basic_simplified_aspect
0 test_basic_abbreviated_aspect
0 test_basic_standard_aspect
0 test_basic_composite_aspect
0 test_basic_lua_aspect
0 test_basic_composite_facet
0 test_basic_lua_facet
0 test_basic_composite_default_facet
0 test_basic_lua_default_facet
# AI Modification tests
0 test_modify_ai_delete_facet
0 test_modify_ai_change_facet
0 test_modify_ai_replace_facet
0 test_modify_ai_add_facet
0 test_modify_ai_change_default_facet
0 test_modify_ai_nested_facets
0 test_modify_ai_composite_default_facets
Added some event unit tests by @Pentarctagon Tests event execution order and events with variable names.
2018-01-01 21:17:56 +00:00
0 test_modify_ai_change_aspect
Add a unit test for wesnoth.create_side
2019-11-18 19:36:19 +00:00
# Changing the number of sides
0 test_create_side
Added some event unit tests by @Pentarctagon Tests event execution order and events with variable names.
2018-01-01 21:17:56 +00:00
# Event tests
Add unit tests for interpolated event names and end_turn Move `event_name_variable_substitution` to the top of the file, as it's testing that the event triggers at all, before the tests that check which order the events are triggered in. The old `order_of_variable_events1` seemed to be a combination of two tests that should exist, but the code didn't quite test either of them. This replaces it with a new `order_of_variable_events1` and `order_of_variable_events3`. Docs partially written by Pentarctagon, this started as a review comment on the documentation PR.
2022-11-23 13:52:51 +00:00
0 event_name_variable_substitution
Added some event unit tests by @Pentarctagon Tests event execution order and events with variable names.
2018-01-01 21:17:56 +00:00
0 order_of_variable_events1
Convert some fail-on-success unit tests to pass-on-success (#4597)
2019-11-25 13:28:03 +00:00
0 order_of_variable_events2
Add unit tests for interpolated event names and end_turn Move `event_name_variable_substitution` to the top of the file, as it's testing that the event triggers at all, before the tests that check which order the events are triggered in. The old `order_of_variable_events1` seemed to be a combination of two tests that should exist, but the code didn't quite test either of them. This replaces it with a new `order_of_variable_events1` and `order_of_variable_events3`. Docs partially written by Pentarctagon, this started as a review comment on the documentation PR.
2022-11-23 13:52:51 +00:00
0 order_of_variable_events3
0 premature_end_turn1
2 premature_end_turn2
Add a unit test for the event-handler reordering bug This test would fail without the fix from the previous commit.
2024-01-20 21:49:40 +00:00
0 events_test_priority_in_same_name
Implement event priority For any given event name, events execute in order of decreasing priority. Priority is a real number, and may be assigned via the `priority` attribute for the WML [event] tag, or through the Lua APIs: - wesnoth.game_events.add({priority = number}) - wesnoth.game_events.add_repeating(name, action, [priority]) Note that delayed variable substitution is not currently supported in the WML attribute.
2023-05-02 05:53:10 +00:00
0 events_test_priority_vs_origin
0 events_test_same_priority
0 events_test_multi_int
0 events_test_multi_float
0 events_test_lua_events_add_priority_vs_origin
0 events_test_lua_events_add_repeating_priority_vs_origin
Test fire_event of kill unit on recall list (#7283)
2023-01-16 12:25:09 +00:00
0 kill_fires_events
Healing: Add a unit test.
2018-10-20 23:13:50 +00:00
# Game mechanics
Unit tests to evaluate behavior with max_experience=0 and with no advancements (#7344)
2023-02-04 12:14:44 +00:00
0 zero_experience
Fix increase by percentage returns 1 if experience is equal to zero (#8425) Using `[effect]app/y_to,increase=experience,"40%"` on a unit with 0 XP used to give that unit 1 XP, because of a minimum in the C++.
2024-02-19 12:49:09 +00:00
0 increase_zero_experience_by_percentage
Unit tests to evaluate behavior with max_experience=0 and with no advancements (#7344)
2023-02-04 12:14:44 +00:00
0 unit_no_advancements
add test for no [side]s in [scenario]
2023-05-06 17:10:06 +00:00
0 no_sides
Add a bunch of tests for heals. (#8074) Covers only attributes, not filters.
2023-11-30 10:09:52 +00:00
# heal ability tests
0 heal
0 heal_with_filter
0 heal_positive_value
0 heal_negative_value
0 heal_zero
0 heal_add
0 heal_add_divide
0 heal_add_multiply
0 heal_add_sub
0 heal_affect_self
0 heal_affect_enemies
0 heal_affect_everybody
0 heal_divide
0 heal_high_fraction
0 heal_low_fraction
0 heal_multiply
0 heal_multiply_divide
Test multiplying by a fractional value.
2023-12-07 06:07:33 +00:00
0 heal_multiply_fraction
Add a bunch of tests for heals. (#8074) Covers only attributes, not filters.
2023-11-30 10:09:52 +00:00
0 heal_no_value
0 heal_sub
0 heal_sub_divide
0 heal_sub_multiply
0 heal_wfl_other
0 heal_wfl_self
0 heal_poison_slowed
0 heal_poison_cured
0 heal_no_poison
0 heal_two_cumulative_yes_same_id
0 heal_two_cumulative_yes_unique_id
0 heal_two_cumulative_no_same_id
0 heal_two_cumulative_no_unique_id
0 heal_two_cumulative_mixed_same_id
0 heal_two_cumulative_mixed_unique_id
max_value negative tests.
2023-12-18 05:42:35 +00:00
0 heal_max_value
Add some more abilities' tests (hides, skirmisher, teleport)
2024-01-01 11:34:08 +00:00
# regenerate ability tests
add a bunch of regenerate tests (#8079) mostly the same as the heals tests, since they're basically the same ability with different defaults.
2023-12-06 05:15:26 +00:00
0 regenerate_positive_value
0 regenerate_negative_value
0 regenerate_zero
0 regenerate_add
0 regenerate_add_divide
0 regenerate_add_multiply
0 regenerate_add_sub
0 regenerate_affect_self_no
0 regenerate_affect_enemies
0 regenerate_affect_everybody
0 regenerate_divide
0 regenerate_high_fraction
0 regenerate_low_fraction
0 regenerate_multiply
0 regenerate_multiply_divide
Test multiplying by a fractional value.
2023-12-07 06:07:33 +00:00
0 regenerate_multiply_fraction
add a bunch of regenerate tests (#8079) mostly the same as the heals tests, since they're basically the same ability with different defaults.
2023-12-06 05:15:26 +00:00
0 regenerate_no_value
0 regenerate_sub
0 regenerate_sub_divide
0 regenerate_sub_multiply
0 regenerate_wfl_other
0 regenerate_wfl_self
0 regenerate_poison_slowed
0 regenerate_poison_cured
0 regenerate_no_poison
0 regenerate_two_cumulative_yes_same_id
0 regenerate_two_cumulative_yes_unique_id
0 regenerate_two_cumulative_no_same_id
0 regenerate_two_cumulative_no_unique_id
0 regenerate_two_cumulative_mixed_same_id
0 regenerate_two_cumulative_mixed_unique_id
max_value negative tests.
2023-12-18 05:42:35 +00:00
0 regenerate_max_value
Add some more abilities' tests (hides, skirmisher, teleport)
2024-01-01 11:34:08 +00:00
# resistance ability tests
add a bunch of resistance ability tests (#8105)
2023-12-15 15:59:01 +00:00
0 resistance_negative_value
0 resistance_zero
0 resistance_add
0 resistance_add_divide
0 resistance_add_multiply
0 resistance_add_sub
0 resistance_affect_self_no
0 resistance_affect_enemies
0 resistance_affect_everybody
0 resistance_divide
0 resistance_high_fraction
0 resistance_low_fraction
0 resistance_multiply
0 resistance_multiply_divide
0 resistance_multiply_fraction
0 resistance_no_value
0 resistance_sub
0 resistance_sub_divide
0 resistance_sub_multiply
0 resistance_wfl_other
0 resistance_wfl_self
0 resistance_two_cumulative_yes_same_id
0 resistance_two_cumulative_yes_unique_id
Unit test cumulative resistance with a base value These tests clarify what "cumulative" means for non-leadership abilites, which since Wesnoth 1.1.3 doesn't seem to fit the English word. For cumulative abilities, if the base value from the unit is higher that the ability's value, then the base value is used instead. In the case of a Skeleton with 40% base resistance, "cumulative=yes" is equivalent to "value,cumulative=40,no". In all of these cases, a single ability's value is used; "cumulative" doesn't mean that the values from multiple abilities interact. This is all when using value=, not when using add= or sub=. (cherry picked from commit 9b2016a4afb466985047b6907b1cefc794e46e76)
2024-04-11 02:15:16 +00:00
0 resistance_two_cumulative_yes_unique_id_skeletal
add a bunch of resistance ability tests (#8105)
2023-12-15 15:59:01 +00:00
0 resistance_two_cumulative_no_same_id
0 resistance_two_cumulative_no_unique_id
Unit test cumulative resistance with a base value These tests clarify what "cumulative" means for non-leadership abilites, which since Wesnoth 1.1.3 doesn't seem to fit the English word. For cumulative abilities, if the base value from the unit is higher that the ability's value, then the base value is used instead. In the case of a Skeleton with 40% base resistance, "cumulative=yes" is equivalent to "value,cumulative=40,no". In all of these cases, a single ability's value is used; "cumulative" doesn't mean that the values from multiple abilities interact. This is all when using value=, not when using add= or sub=. (cherry picked from commit 9b2016a4afb466985047b6907b1cefc794e46e76)
2024-04-11 02:15:16 +00:00
0 resistance_two_cumulative_no_unique_id_skeletal
add a bunch of resistance ability tests (#8105)
2023-12-15 15:59:01 +00:00
0 resistance_two_cumulative_mixed_same_id
0 resistance_two_cumulative_mixed_unique_id
Unit test cumulative resistance with a base value These tests clarify what "cumulative" means for non-leadership abilites, which since Wesnoth 1.1.3 doesn't seem to fit the English word. For cumulative abilities, if the base value from the unit is higher that the ability's value, then the base value is used instead. In the case of a Skeleton with 40% base resistance, "cumulative=yes" is equivalent to "value,cumulative=40,no". In all of these cases, a single ability's value is used; "cumulative" doesn't mean that the values from multiple abilities interact. This is all when using value=, not when using add= or sub=. (cherry picked from commit 9b2016a4afb466985047b6907b1cefc794e46e76)
2024-04-11 02:15:16 +00:00
0 resistance_two_cumulative_mixed_unique_id_skeletal
add a bunch of resistance ability tests (#8105)
2023-12-15 15:59:01 +00:00
0 resistance_max_value
add min_value to [resistance] (#8722) max_value is used to limit the increase in resistance with the "resistance" capability, but there was no equivalent for its reduction. To be able to add min_value without redoing the "resistance" checking for the umpteenth time, I prefer to modify effect:: so that the checking of these two attributes is done at the same time as the other numerical attributes and keep the door open to a possible generalization of the proceed
2024-04-11 02:48:41 +00:00
0 resistance_min_value
Unit test cumulative resistance with a max_value In 1.19 since 82499d07857885263d2617560b4754c20e34f16f, this will apply a max_value of 15, which will also be the combined value. The same test has surprising result on 1.18, the max_value attributes get added together for a total max_value of 47, but the values don't, so the single highest value of 30 is used. (the corresponding 1.18 commit is 9632febdb54824bdf27428fddb93de18c374b845)
2024-04-12 07:27:24 +00:00
0 resistance_cumulative_max_value
add a bunch of resistance ability tests (#8105)
2023-12-15 15:59:01 +00:00
0 resistance_negative_max_value
0 resistance_apply_to_blade
0 resistance_apply_to_non_blade
0 resistance_apply_to_invalid
0 resistance_active_on_offense
0 resistance_active_on_defense
0 resistance_active_on_both
0 resistance_no_max_value
0 resistance_no_value_no_max_value
0 resistance_no_value_no_max_value_add
Add some more abilities' tests (hides, skirmisher, teleport)
2024-01-01 11:34:08 +00:00
# leadership ability tests
add a bunch of leadership ability tests (#8125)
2023-12-18 00:29:27 +00:00
0 leadership_negative_value
0 leadership_zero
0 leadership_add
0 leadership_add_divide
0 leadership_add_multiply
0 leadership_add_sub
0 leadership_affect_self_no
0 leadership_affect_enemies
0 leadership_affect_everybody
0 leadership_divide
0 leadership_high_fraction
0 leadership_low_fraction
0 leadership_multiply
0 leadership_multiply_divide
0 leadership_multiply_fraction
0 leadership_no_value
0 leadership_sub
0 leadership_sub_divide
0 leadership_sub_multiply
0 leadership_wfl_other
0 leadership_wfl_self
0 leadership_two_cumulative_yes_same_id
0 leadership_two_cumulative_yes_unique_id
0 leadership_two_cumulative_no_same_id
0 leadership_two_cumulative_no_unique_id
0 leadership_two_cumulative_mixed_same_id
0 leadership_two_cumulative_mixed_unique_id
0 leadership_max_value
0 leadership_active_on_offense
0 leadership_active_on_defense
Add some more abilities' tests (hides, skirmisher, teleport)
2024-01-01 11:34:08 +00:00
# illuminates ability tests
add a bunch of illuminates tests. (#8139)
2023-12-23 18:07:45 +00:00
0 illuminates_active_on_defense
0 illuminates_active_on_offense
0 illuminates_add
0 illuminates_add_divide
0 illuminates_add_multiply
0 illuminates_add_sub
0 illuminates_affect_allies
0 illuminates_affect_enemies
0 illuminates_affect_everybody
0 illuminates_affect_self_no
0 illuminates_divide
0 illuminates_high_fraction
0 illuminates_low_fraction
0 illuminates_max_value
0 illuminates_min_value
0 illuminates_min_value_no_max_value
0 illuminates_multiply
0 illuminates_multiply_divide
0 illuminates_multiply_fraction
0 illuminates_negative_max_value
0 illuminates_negative_min_value
0 illuminates_negative_value
0 illuminates_no_max_value
0 illuminates_no_value
0 illuminates_sub
0 illuminates_sub_divide
0 illuminates_sub_multiply
0 illuminates_two_cumulative_mixed_same_id
0 illuminates_two_cumulative_mixed_unique_id
0 illuminates_two_cumulative_no_same_id
0 illuminates_two_cumulative_no_unique_id
0 illuminates_two_cumulative_yes_same_id
0 illuminates_two_cumulative_yes_unique_id
0 illuminates_wfl_other
0 illuminates_wfl_self
0 illuminates_zero
0 illuminates_value_neutral
0 illuminates_value_chaotic
0 illuminates_value_liminal
0 illuminates_value_day_uncapped
0 illuminates_value_day_capped
0 illuminates_value_night
0 illuminates_value_deep
Add some more abilities' tests (hides, skirmisher, teleport)
2024-01-01 11:34:08 +00:00
# skirmisher ability tests
0 skirmisher
0 no_skirmisher
0 skirmisher_adjacent_enemies
0 skirmisher_adjacent
# hides ability tests
0 hides_self
0 hides_nobody
# teleport ability tests
0 teleport_simple
0 no_teleport
0 teleport_no_tunnel
0 teleport_adjacent_allies
0 tunnel_filter_teleport_unit
0 tunnel_target_teleport_unit_fail
0 tunnel_target_teleport_unit_succeed
0 tunnel_source_teleport_unit_fail
0 tunnel_source_teleport_unit_succeed
add a bunch of attacks tests
2024-01-05 15:40:03 +00:00
# attacks ability tests
9 attacks_negative_value
0 attacks_zero
0 attacks_add
0 attacks_add_divide
0 attacks_add_multiply
0 attacks_add_sub
damage ability tests (#9137)
2024-07-31 00:06:38 +00:00
0 attacks_affect_allies
add a bunch of attacks tests
2024-01-05 15:40:03 +00:00
0 attacks_affect_self_no
0 attacks_affect_enemies
0 attacks_affect_everybody
0 attacks_divide
0 attacks_high_fraction
0 attacks_low_fraction
0 attacks_multiply
0 attacks_multiply_divide
0 attacks_multiply_fraction
0 attacks_no_value
0 attacks_sub
0 attacks_sub_divide
0 attacks_sub_multiply
0 attacks_wfl_other
0 attacks_wfl_self
0 attacks_two_cumulative_yes_same_id
0 attacks_two_cumulative_yes_unique_id
0 attacks_two_cumulative_no_same_id
0 attacks_two_cumulative_no_unique_id
0 attacks_two_cumulative_mixed_same_id
0 attacks_two_cumulative_mixed_unique_id
0 attacks_max_value
0 attacks_overwrite_specials_one_side
0 attacks_overwrite_specials_both_sides
0 attacks_overwrite_specials_two_both_sides
0 attacks_overwrite_specials_two_one_side
0 attacks_overwrite_specials_mixed
Add berserk weapon special abilities tests (#8973) Changes: * CHECK_STRIKES macro now takes a comma-delimited list of strike counts for when units have a different number of strikes for different weapons, and updates the existing usage in the attacks tests * Fixed a typo in the attacks_zero test * Adds tests for berserk as a weapon special ability. Berserk's handling differs from attacks as a weapon special ability: * A value less than 1 is treated as effectively infinite rounds of combat (undocumented) * The cumulative attribute is handled differently - in some cases it sums the values instead of using the highest single value whereas for attacks it always uses the highest single value Also now exclude data/tests/ from scons pot-update since it was hitting the argument limit for number of arguments to a script.
2024-06-16 01:20:54 +00:00
# berserk ability tests
0 berserk_negative_value
0 berserk_zero
0 berserk_add
0 berserk_add_divide
0 berserk_add_multiply
0 berserk_add_sub
damage ability tests (#9137)
2024-07-31 00:06:38 +00:00
0 berserk_affect_allies
Add berserk weapon special abilities tests (#8973) Changes: * CHECK_STRIKES macro now takes a comma-delimited list of strike counts for when units have a different number of strikes for different weapons, and updates the existing usage in the attacks tests * Fixed a typo in the attacks_zero test * Adds tests for berserk as a weapon special ability. Berserk's handling differs from attacks as a weapon special ability: * A value less than 1 is treated as effectively infinite rounds of combat (undocumented) * The cumulative attribute is handled differently - in some cases it sums the values instead of using the highest single value whereas for attacks it always uses the highest single value Also now exclude data/tests/ from scons pot-update since it was hitting the argument limit for number of arguments to a script.
2024-06-16 01:20:54 +00:00
0 berserk_affect_self_no
0 berserk_affect_enemies
0 berserk_affect_everybody
0 berserk_divide
0 berserk_high_fraction
0 berserk_low_fraction
0 berserk_multiply
0 berserk_multiply_divide
0 berserk_no_value
0 berserk_sub
0 berserk_sub_divide
0 berserk_sub_multiply
0 berserk_wfl_other
0 berserk_wfl_self
0 berserk_two_cumulative_yes_same_id
0 berserk_two_cumulative_yes_unique_id
0 berserk_two_cumulative_no_same_id
0 berserk_two_cumulative_no_unique_id
0 berserk_two_cumulative_mixed_same_id
0 berserk_two_cumulative_mixed_unique_id
0 berserk_max_value
0 berserk_overwrite_specials_one_side
0 berserk_overwrite_specials_both_sides
0 berserk_overwrite_specials_two_both_sides
0 berserk_overwrite_specials_two_one_side
0 berserk_overwrite_specials_mixed
0 berserk_different_values
chance_to_hit tests (#9093)
2024-07-21 22:30:37 +00:00
# chance_to_hit ability tests
0 chance_to_hit_negative_value
0 chance_to_hit_add
0 chance_to_hit_add_divide
0 chance_to_hit_add_multiply
0 chance_to_hit_add_sub
damage ability tests (#9137)
2024-07-31 00:06:38 +00:00
0 chance_to_hit_affect_allies
chance_to_hit tests (#9093)
2024-07-21 22:30:37 +00:00
0 chance_to_hit_affect_self_no
0 chance_to_hit_affect_enemies
0 chance_to_hit_affect_everybody
0 chance_to_hit_divide
0 chance_to_hit_multiply
0 chance_to_hit_multiply_divide
0 chance_to_hit_no_value
0 chance_to_hit_sub
0 chance_to_hit_sub_divide
0 chance_to_hit_sub_multiply
0 chance_to_hit_wfl_other
0 chance_to_hit_wfl_self
0 chance_to_hit_two_cumulative_yes_same_id
0 chance_to_hit_two_cumulative_yes_unique_id
0 chance_to_hit_two_cumulative_no_same_id
0 chance_to_hit_two_cumulative_no_unique_id
0 chance_to_hit_two_cumulative_mixed_same_id
0 chance_to_hit_two_cumulative_mixed_unique_id
0 chance_to_hit_max_value
0 chance_to_hit_overwrite_specials_one_side
0 chance_to_hit_overwrite_specials_both_sides
0 chance_to_hit_overwrite_specials_two_both_sides
0 chance_to_hit_overwrite_specials_two_one_side
0 chance_to_hit_overwrite_specials_mixed
damage ability tests (#9137)
2024-07-31 00:06:38 +00:00
# damage ability tests
0 damage_negative_value
0 damage_zero
0 damage_add
0 damage_add_divide
0 damage_add_multiply
0 damage_add_sub
0 damage_affect_allies
0 damage_affect_self_no
0 damage_affect_enemies
0 damage_affect_everybody
0 damage_divide
0 damage_high_fraction
0 damage_low_fraction
0 damage_multiply
0 damage_multiply_divide
0 damage_multiply_fraction
0 damage_no_value
0 damage_sub
0 damage_sub_divide
0 damage_sub_multiply
0 damage_wfl_other
0 damage_wfl_self
0 damage_two_cumulative_yes_same_id
0 damage_two_cumulative_yes_unique_id
0 damage_two_cumulative_no_same_id
0 damage_two_cumulative_no_unique_id
0 damage_two_cumulative_mixed_same_id
0 damage_two_cumulative_mixed_unique_id
0 damage_max_value
0 damage_overwrite_specials_one_side
0 damage_overwrite_specials_both_sides
0 damage_overwrite_specials_two_both_sides
0 damage_overwrite_specials_two_one_side
0 damage_overwrite_specials_mixed
damage_type tests
2024-08-01 14:25:28 +00:00
# damage_type ability tests
0 damage_type_replacement_arcane
0 damage_type_replacement_blade
0 damage_type_replacement_cold
0 damage_type_replacement_fire
0 damage_type_replacement_impact
0 damage_type_replacement_pierce
0 damage_type_alternative_arcane
0 damage_type_alternative_blade
0 damage_type_alternative_cold
0 damage_type_alternative_fire
0 damage_type_alternative_impact
0 damage_type_alternative_pierce
0 damage_type_replacement_two
0 damage_type_replacement_three
0 damage_type_alternative_two
0 damage_type_alternative_three
0 damage_type_both_separate_replacement_best
0 damage_type_both_separate_alternative_best
0 damage_type_both_same_replacement_best
0 damage_type_both_same_alternative_best
0 damage_type_many
add disable ability tests
2024-08-12 04:09:54 +00:00
# disable tests
0 disable_ability
0 disable_affect_allies
0 disable_affect_self_no
0 disable_affect_enemies
0 disable_affect_everybody
drains tests
2024-08-24 03:38:11 +00:00
# drains ability tests
0 drains_negative_value
0 drains_zero
0 drains_add
0 drains_add_divide
0 drains_add_multiply
0 drains_add_sub
0 drains_affect_allies
0 drains_affect_self_no
0 drains_affect_enemies
0 drains_affect_everybody
0 drains_divide
0 drains_high_fraction
0 drains_low_fraction
0 drains_multiply
0 drains_multiply_divide
0 drains_multiply_fraction
0 drains_no_value
0 drains_sub
0 drains_sub_divide
0 drains_sub_multiply
0 drains_wfl_other
0 drains_wfl_self
0 drains_two_cumulative_yes_same_id
0 drains_two_cumulative_yes_unique_id
0 drains_two_cumulative_no_same_id
0 drains_two_cumulative_no_unique_id
0 drains_two_cumulative_mixed_same_id
0 drains_two_cumulative_mixed_unique_id
0 drains_default_cumulative_yes
0 drains_default_cumulative_no
0 drains_default_cumulative_both
0 drains_max_value
0 drains_overwrite_specials_one_side
0 drains_overwrite_specials_both_sides
0 drains_overwrite_specials_two_both_sides
0 drains_overwrite_specials_two_one_side
0 drains_overwrite_specials_mixed
firststrike tests
2024-08-28 23:15:11 +00:00
# firststrike tests
0 firststrike_ability
0 firststrike_affect_allies
0 firststrike_affect_self_no
0 firststrike_affect_enemies
0 firststrike_affect_everybody
heal_on_hit tests - results are identical to drains aside from default value
2024-09-01 19:04:19 +00:00
# heal_on_hit ability tests
0 heal_on_hit_negative_value
0 heal_on_hit_zero
0 heal_on_hit_add
0 heal_on_hit_add_divide
0 heal_on_hit_add_multiply
0 heal_on_hit_add_sub
0 heal_on_hit_affect_allies
0 heal_on_hit_affect_self_no
0 heal_on_hit_affect_enemies
0 heal_on_hit_affect_everybody
0 heal_on_hit_divide
0 heal_on_hit_high_fraction
0 heal_on_hit_low_fraction
0 heal_on_hit_multiply
0 heal_on_hit_multiply_divide
0 heal_on_hit_multiply_fraction
0 heal_on_hit_no_value
0 heal_on_hit_sub
0 heal_on_hit_sub_divide
0 heal_on_hit_sub_multiply
0 heal_on_hit_wfl_other
0 heal_on_hit_wfl_self
0 heal_on_hit_two_cumulative_yes_same_id
0 heal_on_hit_two_cumulative_yes_unique_id
0 heal_on_hit_two_cumulative_no_same_id
0 heal_on_hit_two_cumulative_no_unique_id
0 heal_on_hit_two_cumulative_mixed_same_id
0 heal_on_hit_two_cumulative_mixed_unique_id
0 heal_on_hit_max_value
0 heal_on_hit_overwrite_specials_one_side
0 heal_on_hit_overwrite_specials_both_sides
0 heal_on_hit_overwrite_specials_two_both_sides
0 heal_on_hit_overwrite_specials_two_one_side
0 heal_on_hit_overwrite_specials_mixed
petrifies tests
2024-09-06 20:40:18 +00:00
# petrifies tests
0 petrifies_ability
0 petrifies_affect_allies
0 petrifies_affect_self_no
0 petrifies_affect_enemies
0 petrifies_affect_everybody
plague tests
2024-09-10 04:33:49 +00:00
# plague tests
0 plague_ability
0 plague_affect_allies
0 plague_affect_self_no
0 plague_affect_enemies
0 plague_affect_everybody
0 plague_no_type
0 plague_without_priority
When starting or loading a game, warn if the next scenario is unknown Check that the scenario's next_scenario= exists, and display a warning if it would lead to an "Unknown Scenario" error. This also checks any [endlevel] tags in events. The error message includes the id of the missing scenario, but is mainly a recommendation to check the forums and report a bug in the campaign. This version has a short, one-size-fits-all, text for the error message.
2021-06-07 09:36:28 +00:00
# Warnings about WML
0 unknown_scenario_false_positives
0 unknown_scenario_interpolated
Prevents logging of duplicate deprecation messages and messages missing timestamps. Fixes #5942
2021-07-18 04:35:04 +00:00
9 unknown_scenario_1_0
Document last batch of unit tests.
2022-11-30 22:42:04 +00:00
9 unknown_scenario_1_0_last
9 unknown_scenario_1_1
9 unknown_scenario_2_0
9 unknown_scenario_1_1_last_null
Fix an off-by-one in mapgen's x and y filters, and add unit tests Fixes the currently suspected root cause of #5108, but requires further testing to confirm that it fixes that issue. Closes #6501 (the question of how to test the mapgen filter). (cherry picked from commit 30f50bac681fda1566f5cee5aad7be6b65cb0fdb)
2021-08-29 15:45:31 +00:00
# Lua API tests
Add documentation to more WML unit tests.
2022-11-01 03:06:39 +00:00
0 lua_functional_reduce
Fix an off-by-one in mapgen's x and y filters, and add unit tests Fixes the currently suspected root cause of #5108, but requires further testing to confirm that it fixes that issue. Closes #6501 (the question of how to test the mapgen filter). (cherry picked from commit 30f50bac681fda1566f5cee5aad7be6b65cb0fdb)
2021-08-29 15:45:31 +00:00
0 lua_map_find
0 mapgen_filter_range
0 mapgen_filter_terrain
allow units.remove_modifications to remove multiple types previously it needed multiple calls to remove multiple types of modifications (which could be slow since each call involves a full rebuild of the unit).
2023-12-12 21:26:39 +00:00
0 test_remove_modifications
Add unit tests for Lua API wesnoth.simulate_combat (cherry picked from commit d96968b2ec0ea3198982fc530ee68054dd19af63)
2022-03-22 13:43:28 +00:00
0 simulate_combat_clone_adjacent
0 simulate_combat_occupied
Reference in New Issue Copy Permalink