Hi Lucas, I hope this doesn’t mean the development for autotest is going to stop in any way? BTW, what happened to the beaker project, was it not something similar framework as autotest and being used by redhat primarily.
I would certainly work on testing the below framework. Regards, Om Prakash Singh From: [email protected] [mailto:[email protected]] On Behalf Of Lucas Meneghel Rodrigues Sent: Wednesday, May 27, 2015 2:41 AM To: Virt Test Development Mailing List; Autotest Mailing list Cc: Markus Armbruster; Eduardo Otubo; Paolo Bonzini; Ademar Reis Subject: [Autotest] Avocado + virt-test: Compatibility layer plugin - request for testing TL;DR: We are inviting you guys for early testing of a feature still under development, so please keep your expectations low :). Jump to the numbered list on instructions on how to test it. Hi guys, As you know, we've been developing a replacement framework for autotest, named avocado (the name is going to change soon, but bear with me :)) virt-test is our test suite developed on top of autotest, that grew a lot in the past 6 years it's being developed. It's useful for a number of users, and it's a very active project. We have big plans for the future. And we want to invite you to help build this future. Specifically, we have developed a new plugin for avocado that allows you to run virt-test tests in avocado, allowing you to start to get to know the new runner tool, one of the front pieces of the new framework, and also giving some extra features specific to avocado that weren't available before. * Nice HTML reporting, a hot requested feature that we never had the intention to deliver in virt test itself. The URL below has a screenshot: https://cloud.githubusercontent.com/assets/296807/7406339/7699689e-eed7-11e4-9214-38a678c105ec.png * You can run virt-tests on arbitrary order, and multiple instances of a given test, something that is also currently not possible with the virt test runner. * System info collection. It's a flexible feature, you get to configure easily what gets logged/recorded between tests. Keep in mind that this is the first integration step. In the future, more of the avocado features might be exposed or integrated into the existing virt-tests. Setup ===== 0) Install the autotest rpm from Fedora repos: $ sudo yum install autotest-framework 1) Have virt-test's repo cloned somewhere you deem appropriate: $ git clone https://github.com/autotest/virt-test.git 2) Check out the latest avocado integration branch (the branch is being reviewed before it gets to master) git fetch origin git checkout -b avocado-integration-v3 origin/avocado-integration-v3 git merge master 3) Run the virt test bootstrap script as appropriate in virt-test's dir and make sure you download the latest JeOS: $ ./run -t qemu --bootstrap Please pay attention to the output of the bootstrap script and see if you need to install additional packages to get virt-test properly working. 4) Add my bleeding edge stuff repo to yum/dnf, see its COPR page: https://copr.fedoraproject.org/coprs/lmr/BleedingEdgeStuff/ 5) Install avocado from that repository. Make sure you're not using other avocado rpms in your system $ sudo yum install avocado avocado-examples avocado-plugins-output-html 6) edit your avocado local config file to contain the location of your virt test checkout: $ vim ~/.config/avocado/avocado.conf [virt-test] virt_test_dir=/valid/path/to/virt_test 7) Phew, done! Of course the final process is going to be more streamlined than this. Test ==== A good test for the compat plugin would be to run a mixture of avocado and virt-test tests: avocado run --vt-setup passtest type_specific.io-github-autotest-qemu.migrate.default.tcp type_specific.io-github-autotest-qemu.migrate.default.tcp --open-browser The command line above runs the avocado passtest, then virt-test's migrate.default.tcp test twice and then opens the HTML report in your default browser. Remember that you can check which tests are available in virt-test in the virt-test runner: $ ./run -t qemu --list-tests And in avocado by doing: $ avocado list You can check the virt test compat layer options through: $ avocado run -h You can also check the config values that you can override in your local config file through $ avocado config Please keep in mind that this is at the very best an alpha plugin - we'll be happy to get your error reports! Thanks for helping, Lucas This e-mail (including any attachments) is private and confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are strictly prohibited from taking action on the basis of information in this e-mail and must contact the sender immediately, delete this e-mail (and all attachments) and destroy any hard copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to retain, monitor and intercept e-mail communications through its networks (subject to and in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm
_______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
