=== Testing and CI ===
12 KB (1,752 words) - 14:51, 19 April 2023
.... If you are starting out you can download the OpenRISC test image from [[Testing/System_Images]]. The test image may be gzipped, so be sure to gunzip it fi
5 KB (783 words) - 21:34, 4 July 2022
...image manipulation. This is a good foundation API for building integration testing systems, richer QEmu-based applications, and so forth.
7 KB (1,011 words) - 08:14, 13 April 2021
=== Testing ===
14 KB (2,072 words) - 20:38, 28 April 2020
* The cipher test suite will automatically skip testing algorithms that have been disabled in the underlying OS crypto library at b
=== Testing and CI ===
14 KB (2,091 words) - 09:34, 7 May 2024
...is needed (Now supported on most architectures, tested mainly on x86, some testing on Power and aarch64, s390 support being worked on)
6 KB (885 words) - 12:28, 16 March 2017
...to describe the steps needed to setup a development machine for vhost-user testing.
5 KB (696 words) - 15:11, 11 October 2016
* When running <tt>make check-avocado</tt>, the Avocado testing framework and pycdlib must be present if the build tree was configured with
=== Testing and CI ===
15 KB (2,193 words) - 13:57, 18 December 2023
=== Testing and CI ===
13 KB (1,888 words) - 07:16, 11 April 2022
'''Note: Here we are running both instances on the same Machine for testing, change the IP Addresses if you want to run it on two Hosts'''
6 KB (789 words) - 18:43, 6 June 2020
For testing only, you can ignore the aforementioned requirements
Current required until testing is complete. There are some COLO
25 KB (4,019 words) - 14:39, 20 July 2015
* Updated aarch64 container for bullseye based compiler for testing newer features
=== Testing ===
18 KB (2,670 words) - 01:26, 7 May 2022
=== Testing and CI ===
14 KB (2,074 words) - 14:12, 15 August 2023
* testing and stabilizing host pass-through of various devices
The task consists of identifying open issues and use cases by testing them against various guest systems, then fixing the deficits, and proposing
15 KB (2,288 words) - 15:07, 16 February 2016
It continues to lack any sort of unit-testing framework with the QEMU source tree, however.
This is an open-ended project to design/implement a unit-testing framework to address this. This could potentially be done using python, or
25 KB (3,900 words) - 10:50, 22 March 2016
...to add on_error to the existing block-stream command, if only to ease unit testing. Concerns about the stability of the API can be handled by adding introspe
8 KB (1,370 words) - 14:10, 18 February 2013
'''Summary:''' Apply the afl-fuzz fuzz testing tool to qemu-img and submit patches fixing bugs discovered with afl-fuzz.
...oject is suitable for candidates interested in software security, software testing, compilers, and disk image file formats.
18 KB (2,911 words) - 10:51, 22 March 2016
See also [[Testing/DockerBuild]] for more information.
7 KB (1,051 words) - 13:31, 6 October 2022
'''Summary:''' Apply the afl-fuzz fuzz testing tool to qemu-img and submit patches fixing bugs discovered with afl-fuzz.
...oject is suitable for candidates interested in software security, software testing, compilers, and disk image file formats.
25 KB (4,050 words) - 10:36, 23 March 2017
can dedicate their time to implementing and testing. If there is no previous
9 KB (1,281 words) - 10:12, 9 September 2016
