satelliteqe / robottelo Goto Github PK

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

upload
create
update
delete
refresh

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

Implement python decorators to classify tests for specific products - not all tests are applicable to all products.

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

We should be able to run the UI automation using different locales.

NOTE: Firefox allows you to create a profile dynamically which would allow us to create a localized profile. Need to test other browsers.

from selenium import webdriver

profile = webdriver.firefox.firefox_profile.FirefoxProfile()
profile.set_preference("intl.accept_languages", "fr")

browser = webdriver.Firefox(profile)

browser.get("http://google.com")

The idea is to rename robotello.properties to robotello.properties.sample and then instruct the user to copy and rename the samples file. This way changes to the file won't trigger github warnings. Obviously we'd also add robotello.properties to .gitignore.

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

We should be able to run the CLI tests using different locales other than English:

python robottelo_runner.py --host www.example.com --project katello --locale pt_BR --tests tests.cli.test_Login
python robottelo_runner.py --host www.example.com --project katello --locale fr --tests tests.cli.test_Login

I'm thinking something unique and that can be used by other modules to add multibyte/UTF-8 testing capability across all tests that require it. Please see http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt for some examples.

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

The more menu has non-unique id's for some elements, so navigating this menu requires a workaround until unique ids are added.

We need to be able to wait for ajax calls to complete before selenium commands. This is implemented in katello.auto as a function that polls a javascript var. Since it uses a webdriver method to execute javascript it should be straightforward to port from clojure to python.

Support for sending / reviewing user emails
Example: Forgot Password scenario, Forgot Username scenario

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

• create
• update
• delete
• search
• publish
• refresh

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

upload
create
update
delete
refresh

Thanks to https://github.com/RedHatQE/python-stageportal we should be able to create, edit and delete real RHEL manifests for our content tests! Though we could create a new user for every test, perhaps we should re-use the same user but generate unique distributors for our tests. The teardown method should make sure to delete the distributor to make sure we don't overuse our pools.

All configuration parameters necessary for this feature (i.e. URL for stage CDN) should be kept and read from a properties file (wait until https://github.com/omaciel/robottelo/issues/59 is completed).

Decorators for tests to flag it as being blocked by an existing Bugzilla issue. The framework should:

• Check the Bugzilla issue's current status
  • If CLOSED, VERIFIED, POST or MODIFIED then run the test
    • [BONUS] If test passes, add comment to Bugzilla issue or even mark it as VERIFIED
  • If NEW or ASSIGNED, then skip the test
• Report status of test (runnable?) and any BZ blocking it

@bugzilla(1001234)
def test_delete_org(self)

At the end of the run:

2013-10-31 15:37:16 - robottelo - DEBUG - Test blocked by Bugzilla #1001234

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

• create
• update
• delete
• search

This is going to check for the functionality in UI. Currently there is no facility to check the actual email. This will be done in future.

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

upload
create
update
delete
refresh

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

Providing support of framework arguments (host, sshkey, etc) through properties file.
Sequence of loading should be following:

if os.environ['CONFIG'] != nil; then
  load filename os.environ['CONFIG']
else
  load filename: robotello.properties
fi
overwrite any os.environ[<PROPERTY>] passed to the runner

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

Check whether the client registered successfully.

The UI automation should accept SauceLabs as an option (instead of running on local or internal Selenium grid)

There are scroll bars in a few locations (org switcher, left pane in some views) that have to be scrolled via javascript. These are implemented in katello.auto and since they are primarily javascript, should be easy to port.

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

upload
create
update
delete
refresh

support loading properties from file.

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the CLI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

create
update
delete

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

• upload
• create
• update
• delete
• refresh

This is going to check for the functionality in UI. Currently there is no facility to check the actual email. This will be done in future.

These are not tests but functions to perform the actions via the UI. Let's make sure to add CRUD methods and stick to a standard nomenclature to the method names themselves:

• create sync plan
• update sync plan
• delete sync plan
• sync