Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up automated testing for the serialization module #581

Merged
merged 7 commits into from
Aug 3, 2023

Conversation

rdw-software
Copy link
Member

This is one of the few modules that can easily be tested (compared to some of the other code). Originally, I was planning to use LuaUnit for this and I also tried WowUnit, but both solutions don't seem appropriate. We'll see if this approach is better, got to start somewhere though. If it works well, then the validation logic could be migrated next. Definitely beats having no tests at all...

As a bonus, it's now easier to decode and test import strings (e.g., those posted for DF items on wowhead) - especially offline.

Some boilerplate is required to get any tests running. Improve later...
This replaces the original LuaUnit-based approach, which is clearly a dead end.
Very incomplete, but it's probably still better than nothing at all.
No idea why I left it in there. Good riddance, I guess?
These are added by the CurseForge packager before creating a release archive, but that doesn't allow testing them locally or pinning their versions. It might be worth embedding some of the smaller dependencies that rarely ever change just to make things more reproducible.

Example: LibStub is tiny and hasn't been updated in 7 years.
@rdw-software rdw-software merged commit dde76af into master Aug 3, 2023
6 checks passed
@rdw-software rdw-software deleted the import-string-tests branch August 3, 2023 05:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant