rally/tests/functional
Boris Pavlovic bd067082c5 Rename certification/ to tasks/
Every day Rally step by step closer to the point where Rally is going to be
generic framework and it would be possible to split Rally & Rally OpenStack Plugins

One of the blockers for doing this is certification & samples directories and
their contents. Current apporach creates a lot of confusion:

- Rally Users are running samples against production
- Rally samples are actually not that usefull, because creating from them
  tasks takes a lot of time
- Rally Users don't know what certification task is and how to use it
- Samples are hard to ship/find in packaged way (when rally is installed)
- Samples are going to be impossible to ship after the split
- We have to keep hunderds of yaml/json files in actual state
  in our repo (extra work for developers)

Proposed approach is to:

- Create mechansim CLI command that generates samples using plugin names
- Rename certification -> tasks
- Put in tasks directory pre created and tested tasks for different use cases:
  key performance metrics, functional testing, load testing of key functionality,
  ha Testing
- Remove samples as they are not needed anymore

Change-Id: I4c45224c3af637d17dab0edea038c69a2bae8b1a
2017-09-19 18:01:25 -07:00
..
extra Remove old way to describe scenario plugin via method 2017-07-07 08:30:30 -07:00
__init__.py Display proper missing argument name 2014-10-13 20:48:13 +03:00
test_certification_task.py Rename certification/ to tasks/ 2017-09-19 18:01:25 -07:00
test_cli_deployment.py [CLI] Add support for emtpy deployment 2017-09-09 09:15:43 +00:00
test_cli_plugin.py Fix assertRaise cli output to only generate one file per test 2017-07-20 15:08:27 -07:00
test_cli_task.py Reword "benchmark" word in code base 2017-09-05 23:57:14 +00:00
test_cli_verify.py Configure gate-rally-dsvm-verify 2014-12-12 01:28:01 +02:00
test_lib_api.py [Test] Add test for simple app based on rally api 2017-01-19 13:23:01 +03:00
utils.py Switch everything to rally db 2017-08-29 13:25:41 -07:00