From nobody Sat May 18 16:18:03 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1579700800; cv=none; d=zohomail.com; s=zohoarc; b=ex4w96hgEgGzyNhAPJRqyX/ni9jlBFjvgNeSmgV+nVtx6oIHD3J0FzQAkiJqD2PCbAkRBORH/bx9Tvm6l/h6jZ+fbSsTlg6liM91FxMnqz7s9RgDD8hJfwoy9e7lfvbLG0rXlGsWjuuNkK+L4W+BA4ZKlEhMvyMJZ98Ts4Z5erk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1579700800; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:Message-ID:Sender:Subject:To; bh=Ts9SCDRNaPPbh7Q2CsxkiDyEIy+bE9Y5C6HVsbgfRqE=; b=AW4QQmMuqKBT1MafJiBFWIN0mLpHUq2bDNMZj57iQ7BIoLiiASHqFkBhkBLjvPqKJxZRVjZYkiR56SthZ0bq9t+eMLgn3lbLdpOXprtIFdYlKa4R5btpL8P17q0QI/SG7PPCQ7IXA6DX0TEjPauZx6X2oQ4lbBiwAJr8Qt/m1RU= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail header.from= (p=none dis=none) header.from= Return-Path: Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) by mx.zohomail.com with SMTPS id 1579700800190165.7899907100516; Wed, 22 Jan 2020 05:46:40 -0800 (PST) Received: from localhost ([::1]:42392 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iuGKq-0008CE-TY for importer@patchew.org; Wed, 22 Jan 2020 08:46:20 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:54544) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iuGJz-0007Zi-SW for qemu-devel@nongnu.org; Wed, 22 Jan 2020 08:45:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iuGJx-0000Ev-KF for qemu-devel@nongnu.org; Wed, 22 Jan 2020 08:45:27 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:23776 helo=us-smtp-1.mimecast.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iuGJx-0000DT-AP for qemu-devel@nongnu.org; Wed, 22 Jan 2020 08:45:25 -0500 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-221-oocPSiI2POSI9Zt6vMAZdg-1; Wed, 22 Jan 2020 08:45:17 -0500 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 611CB107ACC4; Wed, 22 Jan 2020 13:45:16 +0000 (UTC) Received: from thuth.com (ovpn-116-176.ams2.redhat.com [10.36.116.176]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9E5EF5C3FD; Wed, 22 Jan 2020 13:45:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579700724; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=Ts9SCDRNaPPbh7Q2CsxkiDyEIy+bE9Y5C6HVsbgfRqE=; b=Vm5dF52w2krjfHBH31G2KGZA/ID8vKRQVtRG11d+u0PhBk4TFcwz7jR8dhqmKscI3NfBHn UNPKiwF0aUKQyfNRo3PRl3W5/eYv/Fq1p5t08XJEN8cb4G2orGxxvjKebu5oa3qYMcXwb3 2hHP40bXGtkTIzeSrlF1G8riuRELcTQ= From: Thomas Huth To: qemu-devel@nongnu.org Subject: [PATCH] docs/devel: Fix qtest paths and info about check-block in testing.rst Date: Wed, 22 Jan 2020 14:45:11 +0100 Message-Id: <20200122134511.23806-1-thuth@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-MC-Unique: oocPSiI2POSI9Zt6vMAZdg-1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 207.211.31.120 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: qemu-trivial@nongnu.org, Laurent Vivier , =?UTF-8?q?Alex=20Benn=C3=A9e?= , qemu-block@nongnu.org, Paolo Bonzini Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" X-ZohoMail-DKIM: fail (Header signature does not verify) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" The qtests have recently been moved to a separate subdirectory, so the paths that are mentioned in the documentation have to be adjusted accordingly. And some of the iotests are now always run as part of "make check", so this information has to be adjusted here, too. Signed-off-by: Thomas Huth --- docs/devel/testing.rst | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst index ab5be0c729..770a987ea4 100644 --- a/docs/devel/testing.rst +++ b/docs/devel/testing.rst @@ -16,8 +16,8 @@ The usual way to run these tests is: =20 make check =20 -which includes QAPI schema tests, unit tests, and QTests. Different sub-ty= pes -of "make check" tests will be explained below. +which includes QAPI schema tests, unit tests, QTests and some iotests. +Different sub-types of "make check" tests will be explained below. =20 Before running tests, it is best to build QEMU programs first. Some tests expect the executables to exist and will fail with obscure messages if they @@ -79,8 +79,8 @@ QTest cases can be executed with =20 make check-qtest =20 -The QTest library is implemented by ``tests/libqtest.c`` and the API is de= fined -in ``tests/libqtest.h``. +The QTest library is implemented by ``tests/qtest/libqtest.c`` and the API= is +defined in ``tests/qtest/libqtest.h``. =20 Consider adding a new QTest case when you are introducing a new virtual hardware, or extending one if you are adding functionalities to an existing @@ -94,20 +94,20 @@ libqos instead of directly calling into libqtest. Steps to add a new QTest case are: =20 1. Create a new source file for the test. (More than one file can be added= as - necessary.) For example, ``tests/test-foo-device.c``. + necessary.) For example, ``tests/qtest/foo-test.c``. =20 2. Write the test code with the glib and libqtest/libqos API. See also exi= sting tests and the library headers for reference. =20 -3. Register the new test in ``tests/Makefile.include``. Add the test execu= table - name to an appropriate ``check-qtest-*-y`` variable. For example: +3. Register the new test in ``tests/qtest/Makefile.include``. Add the test + executable name to an appropriate ``check-qtest-*-y`` variable. For exa= mple: =20 - ``check-qtest-generic-y =3D tests/test-foo-device$(EXESUF)`` + ``check-qtest-generic-y =3D tests/qtest/foo-test$(EXESUF)`` =20 4. Add object dependencies of the executable in the Makefile, including the test source file(s) and other interesting objects. For example: =20 - ``tests/test-foo-device$(EXESUF): tests/test-foo-device.o $(libqos-obj-= y)`` + ``tests/qtest/foo-test$(EXESUF): tests/qtest/foo-test.o $(libqos-obj-y)= `` =20 Debugging a QTest failure is slightly harder than the unit test because the tests look up QEMU program names in the environment variables, such as @@ -152,8 +152,9 @@ parser (either fixing a bug or extending/modifying the = syntax). To do this: check-block ----------- =20 -``make check-block`` is a legacy command to invoke block layer iotests and= is -rarely used. See "QEMU iotests" section below for more information. +``make check-block`` runs a subset of the block layer iotests (the tests t= hat +are in the "auto" group in ``tests/qemu-iotests/group``). +See the "QEMU iotests" section below for more information. =20 GCC gcov support ---------------- --=20 2.18.1