JJan RichterCompatibility with config files in early stages
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Plugins: port bootstrap, list and run plugins This makes the changes necessary for Avocado-VT plugins to work properly with the new style plugins code on Avocado. About namespace and module installation, the Avocado-VT plugins now live on their own namespace, avocado_vt, which will usually find it itself installed on /usr/lib/pythonX.Y/site-packages/avocado_vt. Avocado can find the plugins because Avocado-VT has plugins registered in the correct entry points (avocado.plugins.cli and avocado.plugins.cli.cmd). Signed-off-by: Cleber Rosa <crosa@redhat.com> | 10 年前 | |
Merge pull request #2851 from PaulYuuu/loader_shortname Introduce "--vt-short-names-when-config" to switch test names display | 5 年前 | |
Avocado compatibility: implement a consistent mapping of option names By using the name of the section and key in the configuration file as as the option name, we both: * Improve consistency Adhere to the standard used by the new Avocado * settings module The other positive aspect of this change is that if users should not be impacted if using configuration files, given that the section names and keys did not change, and the option names are pretty much internal. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Compatibility with config files in early stages In early stage of avocado run, there is a time when the vt options are created, but they are not synchronized with values from config files. This can affect some of the global variables which are set during this time. This commit ensures the synchronization right after the options are registered. Reference: #2912 Signed-off-by: Jan Richter <jarichte@redhat.com> | 5 年前 | |
VT Joblock plugin: be lenient with test suites containing Tasks With the resolver/nrunner implementation, there won't be the traditional "test factories" in the test suites, but Tasks. This attempts to fetch the class from the test factory, and ignores if it fails, which would happen if a Task is there instead. This leniency isn't a problem because the joblock plugin should only enforce a lock if a VT (VirtTest) test in within the test suite, which won't happen at this point as there's no resolver for VT tests. Fixes: https://github.com/avocado-framework/avocado/issues/4102 Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Initialization with Job API Right now when we want to run tests through avocado Job API the avocado-vt is not loaded, because a lot of avocado-vt settings is initialized through CLI plugin. This commit moves the initialization to the Init plugin and leaves CLI plugin just for necessary command line setup Signed-off-by: Jan Richter <jarichte@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 年前 | |
Introduce vt-list-guests command This command is meant as a substitute for the option given to "avocado list". The rationale is that when users want to list guests, they don't want to list *tests*. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 5 年前 | |
Use SettingPlugin to register config files The SettingPlugin allows to extend setting paths. let's use this plugin to include our config files instead of injecting them to a magic location. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 6 年前 |