[🛠️] Feature Request: Automated CI Testing for Publishing

[TheDanniCraft]

Is your feature request related to a problem?

Currently, there is no automated way to run tests before publishing (merging) changes to the repository, which can result in undetected bugs or issues being released.

Who benefits?

Contributors and maintainers of the repository will benefit by ensuring only tested code is published, improving reliability and reducing manual testing overhead.

How important is this feature?

Important

Describe the solution you'd like

Implement automated Continuous Integration (CI) testing that runs on every publishing workflow. This would automatically execute test suites (if present) and block publishing if any tests fail. Integrate with popular CI services like GitHub Actions.

Describe alternatives you've considered

Manual testing before publishing is possible but can be error-prone and time-consuming. Skipping tests risks unstable releases.

Additional context

Automated CI testing is a common best practice in open source and would help maintain the quality of published releases.

[RounakJoshi09]

Hey @TheDanniCraft , I can take on this issue, just one quick question. We currently don’t have any test suites implemented, correct? Should I design the workflow in a way that, if we add a test suite later, this workflow will be used to check tests before publishing ?

Thanks

[TheDanniCraft]

@RounakJoshi09 Yes, exactly. At the moment there are no formal unit tests. The main goal right now is to validate the action itself by running it with different input combinations (which is already a form of testing in practice).

There was an initiative to introduce unit tests in #11, but since it has been inactive for over half a year, feel free to take it over if you would also like to integrate proper unit tests into this workflow.