os-autoinst | OS-level test automation
kandi X-RAY | os-autoinst Summary
kandi X-RAY | os-autoinst Summary
os-autoinst is a Perl library typically used in Chef applications. os-autoinst has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.
The OS-autoinst project aims at providing a means to run fully automated tests. Especially to run tests of basic and low-level operating system components such as bootloader, kernel, installer and upgrade, which can not easily and safely be tested with other automated testing frameworks. However, it can just as well be used to test firefox and openoffice operation on top of a newly installed OS. os-autoinst can be executed alone, but is currently designed to be executed together with openQA, the web user interface that allows to run more than one os-autoinst instance at the same time. More information on os-autoinst and openQA can be found on
The OS-autoinst project aims at providing a means to run fully automated tests. Especially to run tests of basic and low-level operating system components such as bootloader, kernel, installer and upgrade, which can not easily and safely be tested with other automated testing frameworks. However, it can just as well be used to test firefox and openoffice operation on top of a newly installed OS. os-autoinst can be executed alone, but is currently designed to be executed together with openQA, the web user interface that allows to run more than one os-autoinst instance at the same time. More information on os-autoinst and openQA can be found on
Support
Quality
Security
License
Reuse
Support
os-autoinst has a low active ecosystem.
It has 136 star(s) with 189 fork(s). There are 22 watchers for this library.
It had no major release in the last 12 months.
There are 2 open issues and 56 have been closed. On average issues are closed in 168 days. There are 12 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of os-autoinst is rolling_relase
Quality
os-autoinst has no bugs reported.
Security
os-autoinst has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
os-autoinst is licensed under the GPL-2.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
os-autoinst releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of os-autoinst
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of os-autoinst
os-autoinst Key Features
No Key Features are available at this moment for os-autoinst.
os-autoinst Examples and Code Snippets
No Code Snippets are available at this moment for os-autoinst.
Community Discussions
No Community Discussions are available at this moment for os-autoinst.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install os-autoinst
Under openSUSE the os-autoinst package can be installed from the official repository or from our devel repository. For further details, have a look at the openQA documentation.
in the top folder which automatically creates a build directory and builds the complete project. to list all available targets. The above commands use a convenience Makefile calling cmake. For packaging, when using an IDE or to conduct the steps manually it is suggested to use CMake directly and do the following: Create a build directory outside of the source directory. The following commands need to be invoked within that directory. You can specify any of the standard CMake variables, e.g. -DCMAKE_BUILD_TYPE=Debug and -DCMAKE_INSTALL_PREFIX=/custom/install/prefix. The following examples assume that GNU Make is used. It is possible to generate for a different build tool by adding e.g. -G Ninja to the CMake arguments.
When using the test-perl-testsuite target, ctest is not used (and therefore ctest specific tweaks have no effect).
One can always run Perl tests manually via prove after the build has been conducted with make symlinks. Note that some tests need to be invoked within the t directory. An invocation like prove -vI.. -I../external/os-autoinst-common/lib 28-signalblocker.t is supposed to work.
It is also possible to run ctest within the build directory directly instead of using the mentioned targets.
All mentioned variables to influence the test execution (TESTS, WITH_COVER_OPTIONS, …) can be combined and can also be used with the coverage target.
in the top folder which automatically creates a build directory and builds the complete project. to list all available targets. The above commands use a convenience Makefile calling cmake. For packaging, when using an IDE or to conduct the steps manually it is suggested to use CMake directly and do the following: Create a build directory outside of the source directory. The following commands need to be invoked within that directory. You can specify any of the standard CMake variables, e.g. -DCMAKE_BUILD_TYPE=Debug and -DCMAKE_INSTALL_PREFIX=/custom/install/prefix. The following examples assume that GNU Make is used. It is possible to generate for a different build tool by adding e.g. -G Ninja to the CMake arguments.
When using the test-perl-testsuite target, ctest is not used (and therefore ctest specific tweaks have no effect).
One can always run Perl tests manually via prove after the build has been conducted with make symlinks. Note that some tests need to be invoked within the t directory. An invocation like prove -vI.. -I../external/os-autoinst-common/lib 28-signalblocker.t is supposed to work.
It is also possible to run ctest within the build directory directly instead of using the mentioned targets.
All mentioned variables to influence the test execution (TESTS, WITH_COVER_OPTIONS, …) can be combined and can also be used with the coverage target.
Support
If you want to contribute to this project, please clone and send pull requests via https://github.com/os-autoinst/os-autoinst. More information on the contribution can be found on http://os-autoinst.github.io/openQA/contact/, too. Issues are tracked on https://progress.opensuse.org/projects/openqav3/. For an overview of the architecture, see doc/architecture.md.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page