Many more tests and fixes
All checks were successful
Build / Build (push) Successful in 3m12s

This commit is contained in:
2026-08-27 17:11:12 +02:00
parent 32b3ef9c4a
commit d2a82b5fe3
204 changed files with 20255 additions and 242 deletions

View File

@@ -107,6 +107,12 @@ Follow the existing conventions — `Scripts/Moves/DrainTests.cs` and
division, overflow guards).
- Cover the negative cases the description implies (non-contact move → no trigger, holding an
item → no boost, attacker already fainted, null `BattleData`, ...).
- **Write the test even when the behavior is not implemented at all.** A described behavior the
script simply lacks (a missing check, a missing effect, a missing interface) still gets a test
encoding the correct Gen VII behavior — it will fail and be marked `[TestFailing]` in step 5,
which is the point: the gap stays tracked in the suite instead of in a report nobody rereads.
"Not implemented" is never a reason to skip writing the test, and reporting a known deviation
as a prose note instead of a `[TestFailing]` test is not acceptable.
- `LibraryHelpers.LoadLibrary()` is available when a test genuinely needs the full Gen7 library
(e.g. looking up real move data); prefer pure mocks otherwise.