Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test system's FLAG_SET not working as intended #5576

Open
Pawkkie opened this issue Oct 24, 2024 · 0 comments
Open

Test system's FLAG_SET not working as intended #5576

Pawkkie opened this issue Oct 24, 2024 · 0 comments
Assignees
Labels
bug Bug category: battle-tests Related to the automated test environment status: confirmed This bug has been confirmed to exist in the codebase

Comments

@Pawkkie
Copy link
Collaborator

Pawkkie commented Oct 24, 2024

Description

It seems that the test system is clearing flags too aggressively for them to be used properly in tests. I haven't investigated this thoroughly, but by default none of the tests we've written for #5566 were able to function without commenting out one of the ClearFlagAfterTest calls.

My concern with just accepting this as a fix is that I'm not sure the flag is being cleared at all with this approach, as the only test that would fail with the Sleep Clause flag active is DOUBLE_BATTLE_TEST("(DYNAMAX) G-Max Befuddle paralyzes, poisons, or sleeps both opponents") and I think that test is running before any of the Sleep Clause tests have the opportunity to set the flag.

If the sleep clause PR itself can be used for testing in any capacity let us know! :D

The Discord conversation in the dev channel for this starts right around here if that's helpful.

Version

1.9.3 (Latest release)

Upcoming/master Version

No response

Discord contact info

@Pawkkie

@Pawkkie Pawkkie added bug Bug status: confirmed This bug has been confirmed to exist in the codebase category: battle-tests Related to the automated test environment labels Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug category: battle-tests Related to the automated test environment status: confirmed This bug has been confirmed to exist in the codebase
Projects
None yet
Development

No branches or pull requests

2 participants