TestingAndDebugging
ShawnieBoy edited this page Apr 7, 2015
·
2 revisions
To be written
The application accepts some parameters that will be most useful for testing or debugging purposes.
-Ddebug=true
- Prints debug information to the error output stream.
- Redirect it to a file by adding '2> logfile.txt'.
-DtestGame=<name_of_your_testclass>
- Have a look at some of the classes in src/magic/test/ to get the idea. It's pretty self explanatory.
-DselfMode (and -DrndSeed=<long>
)
-DparseMissing=true
- looks through the
Magarena\scripts_missing
folder and attempts to load each file. An output fileparsedCards.log
contains cards which have successfully parsed, andparsed_errors.log
lists the errors encountered per file. Both are placed in theMagarena\logs
folder.
Home
Getting Started
Upgrading
Command-line arguments
Feedback / Bug Reporting
Contributing
Keyboard shortcuts
Supported deck formats
Themes
Customizing Magarena
Translating Magarena
User Interface
Main Menu Screen
New duel
Deck view
Deck Editor
Mulligan screen
Game screen
Card Explorer
Card Script Viewer
Download images
Preferences
- Basic Structure
- Mana Property
- List of Costs
- List of Abilities
- List of Effects
- List of Conditions
- Table of Timings
- Groovy File Setup
- Groovy Basics
- Groovy Triggers
- Groovy Activations
- Groovy Events and Actions
- Groovy Statics