Usage of EasyMock in Skript tests (Create fake objects like Players) #5033
Labels
completed
The issue has been fully resolved and the change will be in the next Skript update.
enhancement
Feature request, an issue about something that could be improved, or a PR improving something.
priority: lowest
"Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).
unit testing
For issues/PRs related to the Skript unit testing system.
Suggestion
Skript used to use a library called EasyMock. This library essentially allowed Skript to create fake objects to be used in tests. Things like Player objects with written fake field values.
I have added EasyMock back into Skript in my JUnit pull request at #4979 which will allow for JUnit Java code tests to use EasyMock in their written tests.
This suggestion (or more so a reminder for me) is to add some syntaxes to allow Skript side tests to utilize this library.
Why?
This will help us cover tests that involve runtime testing like Player related events, an entity class related syntax, a block class related syntax like spawner events, etc.
Looking for syntax ideas
If you have any syntax ideas, you can post them in this issue and i'll look at them when I go to start on this. Please consider the EasyMock API when coming up with syntaxes.
The text was updated successfully, but these errors were encountered: