The link at https://wiki.qemu.org/Testing#User_mode_emulation is broken. --[[User:Ehabkost|Ehabkost]] ([[User talk:Eh
199 bytes (29 words) - 22:01, 14 November 2017
== [[Testing/CI|Continuous Integration]] ==
* [[Testing/QemuIoTests|qemu-iotests]], a regression test suite for the block layer cod
9 KB (1,420 words) - 12:16, 12 July 2021
-
0 bytes (0 words) - 19:30, 13 August 2017
== Testing Linux usermode emulation with the Linux Test Project ==
# skiplist for QEMU testing
5 KB (875 words) - 18:07, 20 October 2016
...al -device mechanism. It needs a control unit type especially reserved for testing. As only numbers are used for real control unit types, 0xffff looks like a
From the guest side, this looks like a normal ccw device. Testing might be done via a custom Linux kernel driver, the kvm-test infrastructure
1 KB (223 words) - 08:46, 18 September 2017
-
2 KB (298 words) - 10:00, 12 October 2016
= [[Testing/CI/TroublesomeTests|Troublesome Tests]] =
{{:Testing/CI/TroublesomeTests}}
1 KB (191 words) - 12:36, 19 March 2019
#REDIRECT [[Testing/CI/Travis]]
31 bytes (4 words) - 15:49, 13 March 2019
-
641 bytes (106 words) - 14:52, 7 August 2017
This docker image can then be used for cross build testing with the normal docker test stanzas:
5 KB (738 words) - 09:54, 26 April 2021
-
31 KB (3,354 words) - 14:39, 8 July 2020
...ports a number of different public [[Testing/CI | CI systems]] to maximise testing coverage of code submitted to QEMU.
By testing code via these CI systems prior to submission, contributors can reduce the
7 KB (1,076 words) - 16:57, 12 May 2021
-
1 KB (204 words) - 18:22, 15 February 2013
-
2 KB (271 words) - 17:13, 21 July 2021
-
6 KB (789 words) - 14:54, 29 May 2023
-
2 KB (184 words) - 14:57, 14 February 2020
-
565 bytes (93 words) - 14:27, 3 April 2014
'''DEPRECATED:''' we are in the process of deprecating Travis in favour of [[Testing/CI/GitLabCI|GitLab's CI system]]
== Testing Changes to Travis ==
1 KB (230 words) - 12:24, 15 February 2021
'''DEPRECATED:''' We have now migrated all our cross-compile tests to the [[Testing/CI/GitLabCI|GitLab CI]] architecture.
...ble is used mostly to do our cross compile testing. It uses the existing [[Testing/DockerBuild|docker]] infrastructure to build out major architectures. The c
1,003 bytes (142 words) - 11:34, 16 February 2021
=QEMU 0.14 Release Testing=
Add yourself to volunteer for QEMU 0.14 release testing.
3 KB (435 words) - 05:13, 19 May 2011
...ary that includes an initramfs with busybox, network config and strace for testing
1 KB (176 words) - 12:21, 27 January 2020
-
625 bytes (91 words) - 14:50, 6 October 2020
=QEMU 0.15 Release Testing=
Add yourself to volunteer for QEMU 0.15 release testing.
2 KB (297 words) - 16:56, 13 October 2011
-
2 KB (255 words) - 21:28, 16 April 2015
-
426 bytes (68 words) - 11:58, 25 March 2019
| Debian testing || ? || <b><font color="green">rc2</font></b> || <b><font color="green">rc2
* Comprehensive libvirt testing [LuizCapitulino]
7 KB (1,052 words) - 16:41, 29 November 2011
-
655 bytes (82 words) - 17:13, 9 July 2015
...rvice that perform continuous testing of the QEMU master branch as well as testing of each patch series that is submitted to the mailing list. Patchew also co
1 KB (182 words) - 11:03, 1 August 2019
| Debian testing || ? || ? || ? || ? || ? || ?
* Comprehensive libvirt testing
4 KB (549 words) - 13:08, 28 August 2012
...figure out which commit caused the breakage. This is primarily a tool for testing the toolchains but it could come up with QEMU regressions as well.
1 KB (207 words) - 14:49, 14 July 2020
| [[Testing/CI/GitLabCI|GitLab CI]]
| Majority of CI testing (builds x86 & cross), various check targets
1 KB (200 words) - 16:35, 10 May 2021
[{{PagesStartingWith|'''Testing/'''}} All testing pages]
⇒ [{{PagesStartingWith|Testing/}} All testing pages]
732 bytes (96 words) - 09:13, 10 January 2019
= Testing plan =
Please see the [[Planning/0.14/Testing|testing page]].
423 bytes (56 words) - 09:57, 7 February 2017
This template can be used to embed a build status button for [[Testing/CI/Travis]] with an link:
{{TravisCIStatus|user=stsquad|repo=qemu|branch=testing/next}}
631 bytes (92 words) - 09:35, 23 October 2019
** Testing|Testing QEMU
371 bytes (43 words) - 10:45, 17 February 2017
This template can be used to embed a build status button for [[Testing/CI/CirrusCI]] with an link:
{{CirrusCIStatus|user=stsquad|repo=qemu|branch=testing/next}}
682 bytes (97 words) - 11:05, 20 May 2019
#REDIRECT [[Testing/DockerBuild]]
33 bytes (3 words) - 09:05, 12 October 2016
#REDIRECT [[Testing/CI/Travis]]
31 bytes (4 words) - 15:49, 13 March 2019
#REDIRECT [[Testing/System Images]]
35 bytes (4 words) - 09:07, 12 October 2016
This template can be used to embed a build status button for [[Testing/CI/CirrusCI]] with an link:
{{ShippableCIStatus|id=5885eac43b653a0f00fa97f5|user=stsquad|repo=qemu|branch=testing/next}}
888 bytes (133 words) - 15:45, 22 October 2019
{{CustomCIStatus|user=stsquad|repo=qemu|branch=testing/next}}
{{CustomCIStatus|user=stsquad|repo=qemu|branch=testing/next}}
1 KB (197 words) - 10:12, 30 June 2021
...inaro mainly on ARM related bits. I also have an interest in improving the testing of the code base. I'm known as stsquad on #qemu.
Various testing updates (docker, tcg tests, coverage). My testing/next branch also tends to collect various miscellaneous patches to fix mino
3 KB (421 words) - 19:59, 9 March 2022
'''DEPRECATED:''' We have now migrated all our cross-compile tests to the [[Testing/CI/GitLabCI|GitLab CI]] architecture.
...ble is used mostly to do our cross compile testing. It uses the existing [[Testing/DockerBuild|docker]] infrastructure to build out major architectures. The c
1,003 bytes (142 words) - 11:34, 16 February 2021
'''DEPRECATED:''' we are in the process of deprecating Travis in favour of [[Testing/CI/GitLabCI|GitLab's CI system]]
== Testing Changes to Travis ==
1 KB (230 words) - 12:24, 15 February 2021
= [[Testing/CI/TroublesomeTests|Troublesome Tests]] =
{{:Testing/CI/TroublesomeTests}}
1 KB (191 words) - 12:36, 19 March 2019
= QMP Testing TODO =
kvm-autotest is going to be used to do all client-side QMP testing.
2 KB (388 words) - 08:17, 12 October 2016
...as designed and engineered rigorously. Following a systematic methodology, testing and debugging facilities were built into FVD from day one to automatically
* On the observation of the lack of a method for testing race conditions (I/O order and callback order) in QEMU block drivers, an ev
2 KB (253 words) - 14:45, 11 October 2016
...al -device mechanism. It needs a control unit type especially reserved for testing. As only numbers are used for real control unit types, 0xffff looks like a
From the guest side, this looks like a normal ccw device. Testing might be done via a custom Linux kernel driver, the kvm-test infrastructure
1 KB (223 words) - 08:46, 18 September 2017
'''Summary:''' Improve the REST API to retrieve patch metadata, testing results, etc. from [http://patchew.org patchew.org]
Patchew is an open source CI project to automate testing of patches submitted as emails on mailing lists. Currently Patchew has a s
967 bytes (146 words) - 15:35, 20 March 2018
...Summer of Code in 2016 on the MTTCG project. He has continued working and testing it for most of the remaining year until all the MTTCG patches were merged.
225 bytes (39 words) - 04:50, 7 March 2017
...rvice that perform continuous testing of the QEMU master branch as well as testing of each patch series that is submitted to the mailing list. Patchew also co
1 KB (182 words) - 11:03, 1 August 2019
=== Guest ABI automated testing ===
compatibility, we have no automated testing to detect common
1 KB (218 words) - 18:51, 21 January 2019
* QMP: [[ToDo/QMP|infrastructure]] and [[ToDo/QMPTesting|testing]]
441 bytes (57 words) - 09:12, 10 January 2019
==Testing==
Testing AES-128-CBC cipher:
3 KB (450 words) - 19:41, 30 September 2023
RISU (Random Instruction Sequence generator for Userspace testing) is a tool
for testing CPU instructions with randomly generated opcodes. RISU generates random CPU
2 KB (311 words) - 08:11, 11 March 2022
...m inputs to find bugs that lead to crashes or other program failures. Fuzz testing is a popular technique for finding security bugs.
2 KB (288 words) - 06:58, 25 February 2022
...tested against the program in order to find crashes and other bugs. Fuzz testing complements hand-written test suites by exploring the input space of a prog
...hardware registers randomly to make the device respond. QEMU has a device testing interface called "qtest" that accepts read/write and other commands over a
3 KB (448 words) - 15:15, 17 May 2019
=QEMU 0.15 Release Testing=
Add yourself to volunteer for QEMU 0.15 release testing.
2 KB (297 words) - 16:56, 13 October 2011
=QEMU 0.14 Release Testing=
Add yourself to volunteer for QEMU 0.14 release testing.
3 KB (435 words) - 05:13, 19 May 2011
...m inputs to find bugs that lead to crashes or other program failures. Fuzz testing is a popular technique for finding security bugs.
2 KB (340 words) - 07:01, 25 February 2022
| Tag qemu-1.0-rc1. [[Planning/1.0/Testing|Test Day]]
761 bytes (113 words) - 07:37, 4 November 2011
...e project is to build a driver framework in libqos to enable combinatorial testing. For more information, see [[Features/qtest_driver_framework]].
760 bytes (114 words) - 15:35, 20 March 2018
===Testing===
* Alex Bennée (ARM testing, base enabling tree)
4 KB (568 words) - 10:14, 4 August 2021
...ary that includes an initramfs with busybox, network config and strace for testing
1 KB (176 words) - 12:21, 27 January 2020
* I do some basic sanity testing. This involves booting a few guests, verifying networking works, etc. Thi
...e variety of guests and scripts locally to do this and I choose the set of testing to do based on previous experience of what fails.
3 KB (524 words) - 00:04, 20 May 2013
...figure out which commit caused the breakage. This is primarily a tool for testing the toolchains but it could come up with QEMU regressions as well.
1 KB (207 words) - 14:49, 14 July 2020
== [[Testing/CI|Continuous Integration]] ==
* [[Testing/QemuIoTests|qemu-iotests]], a regression test suite for the block layer cod
9 KB (1,420 words) - 12:16, 12 July 2021
Also see [[Planning/2.4/Testing]].
882 bytes (126 words) - 16:12, 21 October 2015
RISU (Random Instruction Sequence generator for Userspace testing) is
a tool intended to assist in testing the implementation of models of
3 KB (401 words) - 09:48, 4 February 2021
...ports a number of different public [[Testing/CI | CI systems]] to maximise testing coverage of code submitted to QEMU.
By testing code via these CI systems prior to submission, contributors can reduce the
7 KB (1,076 words) - 16:57, 12 May 2021
* Get qemu-img compiling and start testing where it fails
758 bytes (105 words) - 01:35, 19 July 2013
Also see [[Planning/2.3/Testing]].
931 bytes (133 words) - 11:24, 30 July 2015
Also see [[Planning/2.0/Testing]].
949 bytes (134 words) - 20:30, 6 August 2014
existing QMPOutputVisitor, as well as debugging/testing migration via a well
== (old) Testing ==
8 KB (1,202 words) - 16:21, 24 April 2014
== Testing ==
4 KB (549 words) - 12:39, 22 March 2022
...erent targets (x86, mips, powerpc, ...). Images can be obtained from the [[Testing]] page.
== Testing your changes ==
7 KB (1,227 words) - 07:18, 18 November 2021
=== Testing and CI ===
3 KB (277 words) - 09:09, 1 May 2024
== Testing ==
...data is prepared. We can use the space time to fill the cache queue. In my testing, the read speed can be improved from 0.9k/s to 500k/s
6 KB (994 words) - 16:08, 17 October 2016
Create a new guest (dpdk.img) for DPDK testing and then launch it:
===Testing vhost-user-net with DPDK testpmd===
8 KB (1,079 words) - 17:00, 1 February 2023
| [[Planning/1.2/Testing|Test Day]]. Community effort to shake out v1.2.0-rc bugs.
1 KB (159 words) - 15:38, 11 October 2016
