# tp-libvirt

**Repository Path**: hcy1012/tp-libvirt

## Basic Information

- **Project Name**: tp-libvirt
- **Description**: Libvirt test provider for virtualization test. It contains a lot of test cases related to such as libvirt/libguestfs.
- **Primary Language**: Unknown
- **License**: GPL-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 12
- **Created**: 2021-10-27
- **Last Updated**: 2024-05-31

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

===================================
Libvirt Test Provider for virt-test
===================================

This is the official test provider [1]_ for the following
subtest types:

* Libvirt
* LVSB
* V2V
* Libguestfs

Quick Start Guide
------------------------

1. Fork this repo on github.
2. Create a new topic branch for your work.
3. Create a new test provider file in your virt-test repo,
   like::

    cp io-github-autotest-libvirt.ini myprovider.ini

   ::

    [provider]
    uri: file:///home/foo/Code/tp-libvirt
    [libvirt]
    subdir: libvirt/
    [libguestfs]
    subdir: libguestfs/
    [lvsb]
    subdir: lvsb/
    [v2v]
    subdir: v2v/

   You can choose to temporarily delete the
   `io-github-autotest-qemu.ini` file, so that you will not have test
   conflicts. Then you can develop your new test code, run it
   using virt-test, and commit your changes.

4. Make sure you have `inspektor <https://github.com/autotest/inspektor#inspektor>`_ installed.
5. Run::

    inspekt checkall --disable-style E501,E265,W601,E402,E722,E741 --no-license-check <test_script_name>.py

6. Ensure <https://github.com/autotest/tp-libvirt/blob/master/tp-libvirt_review_comment_summary.rst> are met.
7. Fix any problems.
8. Push your changes and submit a pull request.
9. That's it.

.. [1] You can always create your own test provider, if you have special purposes, or just want to develop your work independently.