mastermanager31manager30
This is the automated testsuite for SUSE Manager.
Before you start, make sure you know about the basic concepts of Cucumber that we are using in this testsuite: features, scenarios and steps.
Apart from Cucumber, the testsuite relies on a number of software components.
You can run the SUSE Manager testsuite with sumaform.
The tests (features) included in the [testsuite.yml](https://github.com/SUSE/spacewalk-testsuite-base/blob/master/run_sets/testsuite.yml) file will be executed sequentially from the top to the bottom.
Idempotency is the faculty to run same the feature any number of times. The basic idea of such a feature is that it does not change its environment.
The features are grouped by core and secondary features.
For the group of the core features, the order is relevant. The core features are by design not idempotent, and serve to create a basic testing environment.
The secondary features can be run any number of times, and the order is not important.
- Always create a PR (even for backporting)
- Your PR always needs at least one reviewer to approve
To get started, see the documentation about Using and writing Cucumber steps. It covers most common steps in an ordered manner, as well as the way to write new steps.
Please read with attention the guidelines. They cover style issues, idempotency concerns, file naming conventions, and features, scenarios and test naming conventions.
Check the code coverage results after you have run the test suite with your code.
There are also hints about how to debug the testsuite and about Pitfalls in writing the testsuite.
-
Development (to be run against a HEAD version of SUSE Manager):
-
Release (to be run against a nightly or released tagged version of SUSE Manager):
All other branches are considered legacy (not under development anymore): Manager 2.1, manager21-longterm, Manager 17, Manager 12.