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

Add CI support to run the automated tests in this repo #1

Open
julianharty opened this issue Jan 31, 2025 · 2 comments
Open

Add CI support to run the automated tests in this repo #1

julianharty opened this issue Jan 31, 2025 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@julianharty
Copy link
Member

The parent project has some automated tests that run as compiled C code. This fork is intended to help explore and test ways to run the automated tests automatically as part of the git commit process.

@julianharty julianharty added the enhancement New feature or request label Jan 31, 2025
@julianharty julianharty self-assigned this Jan 31, 2025
@julianharty
Copy link
Member Author

The linux code is built and run thanks to f12f6f1 and 19fa84b

The test is simple: run make using the project's current and unmodified linux makefile, and then run the demo program that's been created without any parameters which performs some basic sanity checks.

The GitHub Actions are run automatically by GitHub. I've also run them on my local development macbook using the ACT project, installed with homebrew:

brew install act

(See https://nektosact.com/installation/homebrew.html)

act -P ubuntu-latest=-self-hosted

(See https://nektosact.com/usage/runners.html)

@julianharty
Copy link
Member Author

Update

Managed to also get the XCode project to build thanks to d0e3dac and 302667d

The tests write to STDOUT which isn't provided by default by the XCode build actions so there's no record of what was run or the outputs of what was run. I'll see if I can capture the outputs so we can check them.

Notes

There are currently two independent GitHub actions script, one for Linux and the other for MacOS. For the moment that's probably good enough. We might be able to create a matrix build or find another way such as creating a parent Action that calls the per-operating-system scripts.

Improvements

Be fun to add a GitHub Badge to the README (as inspired by https://blog.reds.ch/?p=1956).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant