Gordon
Gordon
A collection of autotests for Crowbar
At SUSE, we're using Crowbar in such products as Cloud and Storage, so it will be really helpful for us to have a collection of tests for the web interface and run them after each update to make sure that everything works as expected.
There's a short video about gordon in action here
This project is written in Python3 and uses Splinter library
You can check out source code on the github page
Results by this hackweeck:
- POC was created;
- Gordon can simulate typical user behavior (drag & drop, form filling etc...) on Crowbar page;
- ~ 60 tests were written.
- Here is my short presentation from Prague lightning talks session.
Still need to be done:
- cover whole Crowbar page with tests;
- fetch more hackers to this project;
- cleanup and refactoring (the project is still in alpha phase)
New ideas:
- we can use Gordon POC as the base for another web page testing (for example Portus)
Blog posts:
p.s. the name of the project was inspired by Gordon Freeman, because who better knows how to use crowbar :) ?
This project is part of:
Hack Week 14
Activity
Comments
-
-
over 9 years ago by evshmarnev | Reply
Hi :) I don't think that it's important to choose ruby if you want to interact with web-interface and check results. Regarding cct: Vladimir is more comfortable with ruby, and I'm - with python. We will see what I can do during this hackweek and if it will be valuable for whole QAM team which I am a part of.
Hope I answered your question.
Similar Projects
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/