Closed rfairley closed 4 years ago
Example of basic tests that can be automated: https://github.com/rfairley/console-login-helper-messages/blob/0d6b9c89e3c210640a943d3bae29484ef094cc24/reviewers.md
One approach now is to have kola
external tests, which coreos-assembler
can run either in development or testing environments: https://github.com/coreos/coreos-assembler/blob/master/mantle/kola/README-kola-ext.md
Then the command https://github.com/coreos/coreos-assembler/blob/master/src/cmd-build-fast could be used for local development.
Example of a pipeline: https://github.com/coreos/ignition-dracut/blob/master/.cci.jenkinsfile
This would require adding a make install
target, similar to:
https://github.com/coreos/ignition-dracut/blob/master/Makefile
We'd also want to unify the make install
target with the CLHM RPM specfile at https://src.fedoraproject.org/rpms/console-login-helper-messages/blob/master/f/console-login-helper-messages.spec, to avoid multiple sources of truth.
Automated testing by installing the
console-login-helper-messages*
packages on a vanilla{Fedora/Atomic/CentOS}
system, starting the systemd units, and checking that the expected output is produced at login (bysshd
for motd,agetty
for issue, and by the bash terminal forprofile
) would save time manual testing this.A build of the RPMs, an install, and a test run should trigger once when a PR is opened.