Searched +full:avocado +full:- +full:system +full:- +full:flaky (Results 1 – 3 of 3) sorted by relevance
1 .. _checkavocado-ref:4 Integration testing with Avocado7 The ``tests/avocado`` directory hosts integration tests. They're usually11 These tests are written using the Avocado Testing Framework (which must be13 class, implemented at ``tests/avocado/avocado_qemu``.34 ``avocado.utils.vmimage`` library)39 - http://avocado-framework.readthedocs.io/en/latest/api/test/avocado.html#avocado.Test40 - http://avocado-framework.readthedocs.io/en/latest/api/utils/avocado.utils.html43 -------------45 You can run the avocado tests simply by executing:[all …]
8 ---------------25 ------------34 On QEMU, unit testing is represented by the 'check-unit' target from 'make'.37 ------------------46 On QEMU, functional testing is represented by the 'check-qtest' target from49 System testing50 --------------52 System tests ensure all application elements mesh properly while the overall53 functionality and performance are achieved [4]_. Some or all system components54 are integrated to create a complete system to be tested as a whole. System[all …]
2 - local: '/.gitlab-ci.d/buildtest-template.yml'4 build-system-alpine:6 - .native_build_job_template7 - .native_build_artifact_template9 - job: amd64-alpine-container12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu13 MAKE_CHECK_ARGS: check-build14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog16 check-system-alpine:19 - job: build-system-alpine[all …]