Add automated E2E testing infrastructure #3
Conversation
This commit introduces an end-to-end testing framework for the Fedora CoreOS configuration. The framework uses QEMU to boot a VM with the generated Ignition configuration and then runs a series of tests to validate that the system is working correctly. The following changes are included: - A new 'test/' directory containing the testing scripts. - A shared 'test/lib.sh' script for managing the QEMU VM and running SSH commands. - Individual test scripts for Cockpit and Tailscale. - A central 'test/run_all_tests.sh' script to orchestrate the tests. - A new 'test' target in the 'justfile' to run the tests. - A workaround for a seccomp issue in the development environment by adding unconfined podman recipes to the 'justfile'.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This change introduces an end-to-end testing framework for the Fedora CoreOS configuration. It includes a new
test/directory with scripts for testing Cockpit and Tailscale, a shared library for managing the QEMU VM, and a newtesttarget in thejustfileto orchestrate the tests. It also includes a workaround for a seccomp issue in the development environment.PR created automatically by Jules for task 7378289337395327752 started by @gliu20