From nobody Sun Feb 8 09:22:40 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1646927549; cv=none; d=zohomail.com; s=zohoarc; b=X74D19M/O4Yct6sJmS/q92xG2MbuoUlXOxv7U0h9ypQL4bZOtnHrE0HNDW11TfBRxAKTM3zrmz8i3TWoAubgmiqVF5W1/xYv4x5kmpayE5V46ysEG6YhWMZC1vnsnJzsLtrfFCpZtZgkzipXKuAaF9KT7lTshcUoKfWQRt6nj+g= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1646927549; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=oPIZYA9aX9p6ODZjQ+OFa49NxHYyeK8xyzZZ2KL3ceQ=; b=IZNmxwatkL3W9i+LdS3innjZF89xTmINrbwF4+1atgJJtjcZTiD4dgMpzpHUdgqTPiajpKjBu2ZmMJW2JnWoP93fs7k1+DnZe0Zu5a57ZjmThZ3L8x1GgQ4BePIYWgjINsN9Ddp5TUgRlf3Jwon04ZTRUySHbhghCrlDkKNaVLQ= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.zohomail.com with SMTPS id 16469275499741015.3204342027144; Thu, 10 Mar 2022 07:52:29 -0800 (PST) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-480-50XXegcVMqOAj7NdT7KFmQ-1; Thu, 10 Mar 2022 10:52:27 -0500 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D858E18E5345; Thu, 10 Mar 2022 15:52:24 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id C4537C15E6F; Thu, 10 Mar 2022 15:52:24 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 97A91195FD66; Thu, 10 Mar 2022 15:52:24 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 392C7195FD6C for ; Thu, 10 Mar 2022 15:52:23 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id D47A37C029; Thu, 10 Mar 2022 15:52:22 +0000 (UTC) Received: from speedmetal.redhat.com (unknown [10.40.208.30]) by smtp.corp.redhat.com (Postfix) with ESMTP id 330257C02A for ; Thu, 10 Mar 2022 15:52:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1646927549; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=oPIZYA9aX9p6ODZjQ+OFa49NxHYyeK8xyzZZ2KL3ceQ=; b=ZFLAVjrVQNFeoFsjG+erJCC0JSNNwBAyelFUE5PgHNYvB1bpuQGxxuwd6U7mxQvAN5cvyw puINph4c4l0dRuxN1Xvx3duRkguyUlSSGEHzDUnSxWMZCK+bdlFGsYoVgD092FpttrJZ2l OO1lpakWO+u1UqyOoejKYsPcYAEcUMU= X-MC-Unique: 50XXegcVMqOAj7NdT7KFmQ-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 7/8] docs: Convert 'testtck' page to rST Date: Thu, 10 Mar 2022 16:51:29 +0100 Message-Id: <2f8108cca1aa17c105eedb88cd7eab9be577b95f.1646927156.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1646927550899100001 Content-Type: text/plain; charset="utf-8" Signed-off-by: Peter Krempa --- docs/meson.build | 2 +- docs/testtck.html.in | 40 ---------------------------------------- docs/testtck.rst | 37 +++++++++++++++++++++++++++++++++++++ 3 files changed, 38 insertions(+), 41 deletions(-) delete mode 100644 docs/testtck.html.in create mode 100644 docs/testtck.rst diff --git a/docs/meson.build b/docs/meson.build index cdf78a04b4..d6b944a156 100644 --- a/docs/meson.build +++ b/docs/meson.build @@ -56,7 +56,6 @@ docs_html_in_files =3D [ 'remote', 'storage', 'testsuites', - 'testtck', 'tlscerts', 'uri', 'windows', @@ -112,6 +111,7 @@ docs_rst_files =3D [ 'submitting-patches', 'support', 'testapi', + 'testtck', ] # list of web targets to build for docs/web rule diff --git a/docs/testtck.html.in b/docs/testtck.html.in deleted file mode 100644 index 137586682b..0000000000 --- a/docs/testtck.html.in +++ /dev/null @@ -1,40 +0,0 @@ - - - - -

libvirt TCK : Technology Compatibility Kit

-

The libvirt TCK provides a framework for performing testing - of the integration between libvirt drivers, the underlying virt - hypervisor technology, related operating system services and system - configuration. The idea (and name) is motivated by the Java TCK.

-

In particular the libvirt TCK is intended to address the following - scenarios:

-
    -
  • Validate that a new libvirt driver is in compliance - with the (possibly undocumented!) driver API semantics
    • -
  • Validate that an update to an existing driver does not - change the API semantics in a non-compliant manner
    • -
  • Validate that a new hypervisor release is still providing - compatibility with the corresponding libvirt driver usage
    • -
  • Validate that an OS distro deployment consisting of a - hypervisor and libvirt release is configured correctly
    • -
-

Thus the libvirt TCK will allow developers, administrators and users - to determine the level of compatibility of their platform, and - evaluate whether it will meet their needs, and get awareness of any - regressions that may have occurred since a previous test run.

-

For more details you can look at:

- -

Libvirt-TCK is maintained using - a GIT - repository, and comment, patches and reviews are carried - on the libvir-list development list.<= /p> - - diff --git a/docs/testtck.rst b/docs/testtck.rst new file mode 100644 index 0000000000..51de095657 --- /dev/null +++ b/docs/testtck.rst @@ -0,0 +1,37 @@ +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +libvirt TCK : Technology Compatibility Kit +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + +The libvirt TCK provides a framework for performing testing of the integra= tion +between libvirt drivers, the underlying virt hypervisor technology, related +operating system services and system configuration. The idea (and name) is +motivated by the Java TCK. + +In particular the libvirt TCK is intended to address the following scenari= os: + +- Validate that a new libvirt driver is in compliance with the (possibly + undocumented!) driver API semantics +- Validate that an update to an existing driver does not change the API + semantics in a non-compliant manner +- Validate that a new hypervisor release is still providing compatibility= with + the corresponding libvirt driver usage +- Validate that an OS distro deployment consisting of a hypervisor and li= bvirt + release is configured correctly + +Thus the libvirt TCK will allow developers, administrators and users to +determine the level of compatibility of their platform, and evaluate wheth= er it +will meet their needs, and get awareness of any regressions that may have +occurred since a previous test run. + +For more details you can look at: + +- The initial `mail from Daniel + Berrange `__ + presenting the project. +- The `page describing + VirtTCK `__ the inclus= ion of + libvirt-TCK as a Fedora Feature. + +Libvirt-TCK is maintained using `a GIT +repository `__, and comment, patch= es and +reviews are carried on the `libvir-list `__ development list. --=20 2.35.1