Full Regression Test - rpg-sage-creative/rpg-sage GitHub Wiki
This document is to catalog and share all the commands that I use when doing a full test of RPG Sage's Features. When I first started RPG Sage, it was small and manageable.
It has outgrown that phrase.
Why Share This?
By providing the list of all tests I perform, I am keeping myself honest as well as allowing those that haven't been surrounding by the code and features for years a chance to catch my mistakes. Also, this document will provide me a quick and easy way to copy/paste commands to speed up testing (vs. trying to remember all the commands and typing them in manually).
Why No Automated Testing?
Due to the nature of how many of the replies work (ex: dialog deletes the post and posts new content), automated testing of commands is too daunting a task for me to spend time coding currently. Therefore, I still run commands manually and watch both the output and the server logs for issues.
Unit Testing?
I have moved much of the reusable logic to separate github repos, grouped by purpose or theme (ex: string-utils or math-utils) so that I can more easily manage the smaller pieces of code. This has enabled me to put some unit testing in place, within each repo.
The Future?
The plan now is to have any code that doesn't directly interact with Discord into a separate package/repo so that it can be unit tested. Anytime I touch one of these repos/packages, they are unit tested before getting pushed to the main code for use with RPG Sage. Over time, the majority of the code will be unit tested before each build so that my Regression Testing can focus on interactions with data, discord, and input/output.
Test Cases
If you see any test cases that look weird, please ask about them. If you DON'T see any tests cases that should be there, please let us know!