Avocado-VT is a compatibility plugin that lets you execute virtualization related tests, with all conveniences provided by Avocado
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
COPR SCM/"make srpm" support This adds a Makefile that adds support for the Fedora COPR service to build packages for Avocado-VT, right out of a Git repo. To do so, create your project, and in "Builds" tab, select "New Build". On "1. Select source type" section, select "SCM". On section "2. Provide the source", under "Clone url" add the URL of your repo. For instance, this has been tested with: https://github.com/clebergnu/avocado-vt Under "Committish", enter a reference to a given commit. For instance, this has been tested with the name of this branch: "copr_makefile". Under "3. How to build SRPM from the source", select "make srpm". Finally, select the appropriate Chroots. It's better not to have "Enable internet access during this build" option checked. Finally, it's advisable to not attempt to run this Makefile locally, as it's designed to be run on the environment that CORP provides, that is, a mock based chroot with super user privileges. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 7 年前 | |
Merge pull request #2938 from pevogam/fix-undefined-variable Fix an instance of (conditionally) undefined variable | 5 年前 | |
Cirrus CI Deployment checks: build and install from wheels And also from tarballs. This make sure that the packages we upload to PyPI are tested, given that we've found differences when installing from wheels. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Update Getting Started 1. Avocado doc has been restructured: fix broken links 2. Give more priority to pip installation: a. It's the primary installation method for Avocado (s. doc https://avocado-framework.readthedocs.io/en/latest/guides/user/chapters/installing.html "Avocado is primarily written in Python, so a standard Python installation is possible and often preferable. You can also install from your distro repository, if available." etc.) b. Pip installation is available on more environments. c. Whoever wants to develop/debug test cases is better off with pip installation. 3. Recommend to use the same installation method for both plugin and main program: a. Mixing both methods can lead to issues due to version incompatibility and command availability. 4. Add python-devel as dependency: I got installation error from dependency netifaces (Python.h: No such file or directory) 5. Add a note that test backend related progrmas should be available on target system in order to list test cases. 6. As consequence of GetStartedGuide: Add virsh to recommended programs for qemu test backend because Networking is usually done using libvirtd's virbr0 - s. https://avocado-vt.readthedocs.io/en/latest/Networking.html A user following the GetStartedGuide and gets to the point where they randomly chose any test, e.g. lvm.lvm_create for execution from avocado list --vt-type qemu will just see "ERROR: Can't add interface ... to bridge virbr0: there is no bridge in the system." It's not enough for them to just add a bridge of that name, so it can become quite tedious. By having the virsh already as a recommended program the user can at least try install it which would then automatically set up the default network with correct bridge. | 6 年前 | |
Remove usage of 52lts compatibility layer by Avocado-VT itself Because Avocado 52lts has not been supported for a while, we should drop the compatibility layer. This is a first stage, which removes the *usage* of that layer by Avocado itself. The test providers also need to drop the usage of the 52lts compatibility functions, and then we can remove it from Avocado-VT itself. Even the staging libraries were addressed, because it makes it allows the compatibility module to be removed, and thus, prove that there are no leftovers, and that there won't be any regressions. The staging libraries situation still need to be addressed in the sense that they need to be synced or ideally moved to avocado.utils. This still deserves some more testing, and that is really appreciated, but I'm much more confident with it. I've checked for obvious errors, common on this type of mass change, with: inspekt lint --disable W,R,C,E1002,E1101,E1103,E1120,F0401,I0011,E1003 And there are no new issues introduced with this change. I've also checked and tp-qemu and tp-libvirt are already free of compat_52lts. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 6 年前 | |
Merge pull request #1452 from hereischen/python3-3-23-division Python 3: division fixer | 8 年前 | |
Merge pull request #2413 from pevogam/joint-value-substitution Allow value replacement in joint variants | 5 年前 | |
Merge pull request #2959 from nanliu-r/add_new_cpu_models cpu.py:add new model EPYC-Milan and delete old model | 5 年前 | |
Introduce vt-list-archs command This command is meant as a substitute for the option given to "avocado list". The rationale is that when users want to list archs, they don't want to list *tests*. Differently than the vt-list-guests command, this defaults to current guest configured, to match the behavior of --vt-list-archs. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Virt Test Compatibility layer: Initial import This is the base code for the virt test compatibility layer. We arrived at this initial version of the code after significant work and previous reviews. Basically the compatibility layer aims to let people run virt-test tests inside avocado, giving them avocado specific features, and letting them to get used to the new avocado world. Changes from v3 (v13): * Fixed Ruda's comment about imp import; * Made the entire test source/runner plugin code to fit into 80 columns. Changes from v1 (v11): * The LICENSE file was fixed to state that the files inside the plugin are GPLv2+ licensed (GPLv2 or later), per adereis's comments. Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com> | 10 年前 | |
virt: Adds file which contain patterns which should be excluded. Adds file which contain patterns which should be excluded from tar package distributed to clients from the server. Signed-off-by: Jiří Župka <jzupka@redhat.com> | 13 年前 | |
Remove python 2.7 support in travis ci python 2.7 is deprecated already, so just remove it Moreover, this also align with avocado project Signed-off-by: chunfuwen <chwen@redhat.com> | 5 年前 | |
avocado-vt: add coding style file Signed-off-by: Xu Tian <xutian@redhat.com> | 9 年前 | |
Virt Test Compatibility layer: Initial import This is the base code for the virt test compatibility layer. We arrived at this initial version of the code after significant work and previous reviews. Basically the compatibility layer aims to let people run virt-test tests inside avocado, giving them avocado specific features, and letting them to get used to the new avocado world. Changes from v3 (v13): * Fixed Ruda's comment about imp import; * Made the entire test source/runner plugin code to fit into 80 columns. Changes from v1 (v11): * The LICENSE file was fixed to state that the files inside the plugin are GPLv2+ licensed (GPLv2 or later), per adereis's comments. Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com> | 10 年前 | |
Changing email address Changing email address for Satheesh Rajendran Signed-off-by: Satheesh Rajendran <sathnaga86@gmail.com> | 5 年前 | |
Exclude pmsocat to install avocado-vt in python 2.7 env It reports a SyntaxError when installing avocado-vt in python 2.7 env. And it's a script that can only be used in python 3 env, so exlude it in MANIFEST.in. Signed-off-by: Yingshun Cui <yicui@redhat.com> | 5 年前 | |
Spell check: introduce the concept and command Fixing all spelling issues within Avocado-VT is a huge task, and I don't think we can solve it at once. The goal of this patch is to enable the command and an initial set of changes. Anyone is then welcome to work on this once it's merged, fixing issues and/or adding words to the ignore list. At release time, I can take an extra amount of effort to reduce the issues until we declare it as a requirement like Avocado itself does. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Makefile: Add --upgrade to default pip install Without the "--upgrade" pip detects previous installation and simply returns "already satisfied", without even checking whether it is the same version (nor whether some files changed). Using the "--upgrade" ensures it's always re-installed, which is closer to the previous "setup.py install" behavior. There is a caveat and all deps are actually upgraded as well as the Avocado-vt. Note I tried using "--force-reinstall" and "--ignore-installed", but it resulted in all dependencies being reinstalled even if using the same version, therefor "--upgrade" performs better. I haven't found anything that would only force-reinstall the Avocado-vt. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 6 年前 | |
Add upstream PR Review/Contribute Practices This is follow-up for issue:https://github.com/avocado-framework/avocado-vt/issues/2748 Libvirt Team members summarize some rules or guidelines related to Upstream PR Review/Contribute as per past practices. After reviewing, it is good to be merged and become common best practices in avocado-vt upstream. If further feedbacks are available, related guidelines and rules can be constantsly evolved accordingly. Signed-off-by: chunfuwen <chwen@redhat.com> | 5 年前 | |
Update Getting Started 1. Avocado doc has been restructured: fix broken links 2. Give more priority to pip installation: a. It's the primary installation method for Avocado (s. doc https://avocado-framework.readthedocs.io/en/latest/guides/user/chapters/installing.html "Avocado is primarily written in Python, so a standard Python installation is possible and often preferable. You can also install from your distro repository, if available." etc.) b. Pip installation is available on more environments. c. Whoever wants to develop/debug test cases is better off with pip installation. 3. Recommend to use the same installation method for both plugin and main program: a. Mixing both methods can lead to issues due to version incompatibility and command availability. 4. Add python-devel as dependency: I got installation error from dependency netifaces (Python.h: No such file or directory) 5. Add a note that test backend related progrmas should be available on target system in order to list test cases. 6. As consequence of GetStartedGuide: Add virsh to recommended programs for qemu test backend because Networking is usually done using libvirtd's virbr0 - s. https://avocado-vt.readthedocs.io/en/latest/Networking.html A user following the GetStartedGuide and gets to the point where they randomly chose any test, e.g. lvm.lvm_create for execution from avocado list --vt-type qemu will just see "ERROR: Can't add interface ... to bridge virbr0: there is no bridge in the system." It's not enough for them to just add a bridge of that name, so it can become quite tedious. By having the virsh already as a recommended program the user can at least try install it which would then automatically set up the default network with correct bridge. | 6 年前 | |
Release 86.0 Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Move virt to top level virt directory Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com> | 13 年前 | |
Release 86.0 Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Migrate the core functionality from the remote utility to aexpect This code makes more sense in the aexpect repo as indicated by the higher coupling of imports and use cases. This commit goes hand in hand with the relevant commits on the aexpect side importing the raw code and extending on exceptions, log functions and so on. Signed-off-by: Plamen Dimitrov <pdimitrov@pevogam.com> | 5 年前 | |
Fix centos 7.1 cirrus failure issue due to aexpect On centos 7.1, it use python 2.7 and need relatively lower aexpect version Signed-off-by: chunfuwen <chwen@redhat.com> | 5 年前 | |
Introduce vt-list-archs command This command is meant as a substitute for the option given to "avocado list". The rationale is that when users want to list archs, they don't want to list *tests*. Differently than the vt-list-guests command, this defaults to current guest configured, to match the behavior of --vt-list-archs. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Spell check: introduce the concept and command Fixing all spelling issues within Avocado-VT is a huge task, and I don't think we can solve it at once. The goal of this patch is to enable the command and an initial set of changes. Anyone is then welcome to work on this once it's merged, fixing issues and/or adding words to the ignore list. At release time, I can take an extra amount of effort to reduce the issues until we declare it as a requirement like Avocado itself does. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Allow for absolute paths to additional virtual tests Some test suites would prefer to place their tests outside of and not relative to the default folder with virtual tests. Signed-off-by: Plamen Dimitrov <pdimitrov@pevogam.com> | 6 年前 |
Avocado VT Plugin
Avocado-VT is a compatibility plugin that lets you execute virtualization related tests (then known as virt-test), with all conveniences provided by Avocado.
Gettings started with Avocado
First of all, make sure you have Avocado itself installed. You can check the Avocado online documentation at:
https://avocado-framework.readthedocs.io/en/latest/guides/user/chapters/installing.html
Getting started with Avocado-VT
The recommended way of installing Avocado-VT is through RPM packages. Documentation on how to install it can be found at:
http://avocado-vt.readthedocs.org/en/latest/GetStartedGuide.html