As a qa-automation tester in Product QA for SLES and SUSE-Manager, the SUTs I test (system under test) (like SLE-12-SP2-beta-etc) are changing every day (new packages, patches are merged to SP2, files changes and so on).
Problem: we don't have a tool that give us metadata about the system, like machinery well do.
machinery inspect SUT
machinery show SUT
Problem : what changed from system SLE12-SP-BUILD 8000 from to 8400 ? ( oh, i lost the mail from release manager ! )
Problem : i found a regression with systemd-tests-suite on SLEnkins:
the testsuite fail on BUILD 7400 , but build 7399 is still OK.
what exactly has changed for the package, but also for the system? -> Machinery
Problem: As QA i found a BUG on NFS. I have to report a bug.
Machinery can help me to fill the bug, giving me exact information about really different systems (SLES-12-SP1, openSUSE), etc, what has changed with NFS ? Or Fedora side?
First i want to thank the machinery team, especially Mauro and Manuel that supported me. On this hackweek, have integrated machinery for qa-automation on the library https://github.com/okirch/susetest, and in the SLEnkins automation Framwork.
This work really nice, for scanning systems under test. (SLES, openSUSE)
For qa-automation, machinery works nice and i achieved what i was expecting ! :)
I can scan, compare systems. This could be a FEDORA, DEBIAN, ArchLinux whatever against a openSUSE or a SLES.
In QA and Development, and even Relase Management Perspective this is awesome.
NEW HACK ! :
Revolutionar Perspective for QAAUTOTESTING with Machinery
I'm really glad, i can show you this :
In this example, i compare a SLES-12-SP2-LATEST, with 3-4 builds before.
RESULTS is amazing
With machinery i achieved to compare differents builds from SLES-12-SP2, thanks to the scope, i can see exactly was has changed and was not. I can compare a SLE_12-SP2-GNOME with a SLE-12-SP2-Default, and tracks perfectly changes.
Concrete examples are here :
Scan of a system With console log for machinery ( after the tests are executed) https://slenkins.suse.de/jenkins/view/Test%20suites/job/suite-machinery/13/console
Or with the inspect command redirect to a file.txt to workspace jenkins:
``` setup() machinery_sut = machinery(sut)
try: sometest(sut) machinerysut.inspect() machinerysut.show("tests-machinery") machinerysut.compare("SLE-12-SP2-BUILDXXX-GNOME") ```
Looking for mad skills in:
qa-automation susetest python slenkins machinery
This project is part of:
Hack Week 14
At SUSE we've implemented a module on Salt call...
As there is no progress around [MIrrorPinky](ht...
During the last year Askbot, a question and ans...
Let's make reposync faster
Following a FOSDEM presentation on [Angr](http:...