Add integration tests#120
Merged
Merged
Conversation
add full state tracking Add eating food test
Lexer747
force-pushed
the
pr-integration-tests
branch
from
March 17, 2026 22:31
e385e95 to
e875c1d
Compare
Lexer747
marked this pull request as ready for review
March 17, 2026 23:11
ngraves95
approved these changes
Mar 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR chips away at #115 I was heavily inspired by the testing done in the mainline runelite plugins, e.g.
The actual "unit test" part of this is that we now have
src\test\java\com\attacktimer\IntegrationTests.javawhich creates mock objects (using Mockito, same version as runelite) to stub out the client and other APIs which the plugin expects. Then we create a scenario using these mocks to imitate how I expect the sequence of events to occur when the plugin needs to trigger. Then we mock the game ticks while asserting the plugins internal state is expected.The integration test part is more of baselining approach than an actual integration test, but it's a start.
Ideally I find some time to add a test case for each of the variable speed plugins, especially TDs as from my own slayer tasks that code is a bit brittle at times 😅