If you could define a test using groovy then it would open up that aspect to non-developers since it would not require access to or understanding of the classes in the magic.test source package. It would then allow scripters and play-testers to focus on specific play mechanics. The groovy test scripts could be posted on the forum for discussion and sharing. The scripts could be loaded directly from the UI or specified via command line, in which case a limited version of Magarena would run that only loads the cards specified in the test and displays the duel screen. All other functionality would be disabled while running in this mode.
If you could define a test using groovy then it would open up that aspect to non-developers since it would not require access to or understanding of the classes in the
magic.test
source package. It would then allow scripters and play-testers to focus on specific play mechanics. The groovy test scripts could be posted on the forum for discussion and sharing. The scripts could be loaded directly from the UI or specified via command line, in which case a limited version of Magarena would run that only loads the cards specified in the test and displays the duel screen. All other functionality would be disabled while running in this mode.