Testing QEMU

Details about how to test QEMU and how it is integrated into our CI testing infrastructure.

• Testing in QEMU
  • Testing with “make check”
    • Unit tests
    • QTest
    • Writing portable test cases
    • QAPI schema tests
    • check-block
  • QEMU iotests
    • Writing a new test case
    • Debugging a test case
    • Test case groups
  • Container based tests
    • Introduction
    • Docker Prerequisites
    • Podman Prerequisites
    • Quickstart
    • Registry
    • Images
    • Tests
    • Debugging a Docker test failure
    • Options
  • Thread Sanitizer
    • Thread Sanitizer in Docker
    • Building and Testing with TSan
    • TSan Suppressions
    • TSan Annotations
  • docker-binfmt-image-debian-% targets
    • Setting up binfmt_misc
    • Example invocation
  • VM testing
    • Quickstart
    • QEMU binaries
    • Make jobs
    • Debugging
    • Manual invocation
    • Adding new guests
  • Image fuzzer testing
  • Functional tests using Python
  • Testing with “make check-tcg”
    • Running subset of tests
    • Running individual tests
    • TCG test dependencies
  • Other TCG Tests
    • KVM Unit Tests
    • Linux Test Project
  • GCC gcov support
  • Flaky tests
  • References
• QTest Device Emulation Testing Framework
  • Qtest Driver Framework
    • QGraph concepts
    • Creating a new driver and its interface
    • Adding a new test
    • Qgraph API reference
  • QTest Protocol
    • Valid requests
  • libqtest API reference
• Functional testing with Python
  • Running tests
  • Logging
  • Introduction to writing tests
    • The qemu_test.QemuSystemTest base test class
  • QEMUMachine
    • QEMU binary selection
    • Debugging hung QEMU
  • Attribute reference
    • QemuBaseTest
    • QemuUserTest
    • QemuSystemTest
  • Asset handling
  • Skipping tests
    • QEMU_TEST_ALLOW_LARGE_STORAGE
    • QEMU_TEST_ALLOW_UNTRUSTED_CODE
    • QEMU_TEST_FLAKY_TESTS
    • QEMU_TEST_ALLOW_SLOW
• ACPI/SMBIOS testing using biosbits
  • Introduction
  • Description of the test framework
• Continuous Integration (CI)
• Custom CI/CD variables
  • Set variable globally in the user’s CI namespace
  • Set variable manually when pushing a branch or tag to the user’s repository
  • Setting aliases in your git config
  • Variable naming and grouping
  • Maintainer controlled job variables
    • QEMU_JOB_CIRRUS
    • QEMU_JOB_OPTIONAL
    • QEMU_JOB_ONLY_FORKS
    • QEMU_JOB_SKIPPED
    • QEMU_JOB_PUBLISH
    • QEMU_JOB_FUNCTIONAL
  • Contributor controlled runtime variables
    • QEMU_CI
    • QEMU_CI_FUNCTIONAL
  • Other misc variables
    • AARCH64_RUNNER_AVAILABLE
    • AARCH32_RUNNER_AVAILABLE
    • S390X_RUNNER_AVAILABLE
    • CCACHE_DISABLE
• Jobs on Custom Runners
  • Machine Setup Howto
    • Build environment
    • gitlab-runner setup and registration
  • References
• Fuzzing
  • Basics
  • Building the fuzzers
  • Useful libFuzzer flags
  • Generating Coverage Reports
  • Adding a new fuzzer
  • The Generic Fuzzer
  • OSS-Fuzz
  • Building Crash Reproducers
  • Implementation Details / Fuzzer Lifecycle
• Block I/O error injection using blkdebug
  • Background
  • Rules
  • Events
  • State transitions
  • Suspend and resume
• Block driver correctness testing with blkverify
  • Introduction
  • How it works
  • Example