* Add QTest for issue validation
* Add file-existence check for test
* Update acl_roles_handler.cpp
* Appease clang
* Only look for unittest files
* Where art thou?
* Change root directory when running test
* Fix pathing on Windows CI
* Windows please just accept this path
* Too many CDs
* Bash is evil.
* Wildcard moment
* I swear to god Bill Gates why does your OS suck so much?
* Add cache, use working-directory
* Maybe? Maybe not? Who the fuck cares at this point
* Fix library path
Holy shit these tests almost work on Windows.
* FUCKING HELL
* Where art thou? 2nd Edition
* Edited wrong one
* Re-add execution code
* Remove Linux stuff
* Do it in batch
Bash is evil.
* Set to CMD
* I am now expected
* Missing libs
Should be good enough 🤷
* Powershell my beloved, save me
* Adjust pathing (again)
* Add some debug info
* Powershell syntax shenanigans
* I distrust Github Actions now
* I swear my windows is licensed, please work
* More debug info
* More debug
* For the love of all that is holy why the fuck do you not work
* Cheap path hack
* Upload test folder for debug
* Set Execution Policy<
Apparently tests on the Windows CI never worked???
* Remove debug information
* Does this even work? If not, fuck
* Try older Windows runner
* Comment out non-functional Windows QTest action
* Note that Linux is still functional, so QTest for Windows has to be conducted trough QtCreator till a solution is found.
* Unbreak-test
* Use latest runner version
Co-authored-by: TrickyLeifa <date.epoch@gmail.com>
This allows people who grab the git repo to be able to immediately use
the Qt help files for Akashi, without having to build them and needing
`qhelpgenerator` or even Doxygen.
Doxygen documentation can be generated by calling `doxygen Doxyfile` in
the project's folder.
Furthermore, a Qt help file is also generated if `qhelpgenerator` is in
the path.
