Instructions for testing commands with MockBukkit #356
Comments
JorelAli
added
enhancement
|
Is there already a plan to incorporate these instructions onto the documentation? I was looking into it myself but I'm having trouble with nms. I am currently trying to copy a little from the plugin-test folder, but a detailed tutorial to avoid having unnecessary bloat would be appreciated |
Yes! When a suitable framework structure has been made and we're ready to release the public testing setup for CommandAPI commands, we'll add it to the main documentation :) |
|
Is there an estimate when this will be available? |
Create `automated-tests-shaded` example project to test using the test toolkit Resolves #356 Alternative idea to current work on `dev/public-test-suite` Attempts to allow developers to test their commands independently of any version or nms stuff. Currently, most of the methods throw an UnimplementedMethodException, but I have implemented enough to get the simple `PingPongCommandTests` file to work as a proof of concept. TODO: - Implement the methods required to test: - `commandapi-bukkit-plugin` based projects - Common arguments - Suggestions - Write documentation - Maybe add a module to more rigorously test the toolkit without cluttering the example project I think if we can get a simple version working and published as a snapshot, users can try it out and identify methods that need to be implemented.
Create `automated-tests-shaded` example project to test using the test toolkit Resolves #356 Alternative idea to current work on `dev/public-test-suite` Attempts to allow developers to test their commands independently of any version or nms stuff. Currently, most of the methods throw an UnimplementedMethodException, but I have implemented enough to get the simple `PingPongCommandTests` file to work as a proof of concept. TODO: - Implement the methods required to test: - `commandapi-bukkit-plugin` based projects - Common arguments - Suggestions - Write documentation - Maybe add a module to more rigorously test the toolkit without cluttering the example project I think if we can get a simple version working and published as a snapshot, users can try it out and identify methods that need to be implemented.
Description
Instructions for testing the CommandAPI with MockBukkit. Some worked examples, how to set up a project for testing, inclusion of the plugin-test dependency and support for plugins that are shading the CommandAPI are all stuff that would need to be done.
Expected code
No response
Extra details
No response
The text was updated successfully, but these errors were encountered: