openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/scenario
History
ghanshyam bd8cc59dc2 Mark network slow test as slow 
We have observed that tempest-full jobs was time out
many times.

  http://status.openstack.org/elastic-recheck/#1783405

Based on below ethercalc, we are trying to check the slow
tests and mark them slow so that those tests will not run
as part of tempest-full job. There is other job tempest-slow
which will run these tests.

  https://ethercalc.openstack.org/dorupfz6s9qt

Compute slow tests have been marked slow in
- I2a0e154ba38c7407b41b7e986a0bf9b451c65cae

This commit mark network slow tests based on above ethercalc.

Change-Id: Ic2b3f5ea5b6885fe727a21810ddd9e17b779a1a0
Partial-Bug: #1783405
 		2018-11-02 08:00:21 +00:00
..
README.rst Fix docs markup consistency 2017-11-21 19:02:54 +09:00
__init__.py add scenario directory 2013-05-17 08:52:22 -04:00
manager.py Merge "Set max_microversion 2.35 for nova image tests" 2018-09-18 16:06:40 +00:00
test_aggregates_basic_ops.py Replace list_hypervisors with list_services 2018-04-04 10:28:40 +03:00
test_encrypted_cinder_volumes.py Use new encryption provider constants 2018-04-06 06:20:59 +00:00
test_minimum_basic.py Refresh server data after fip is assigned 2018-02-06 11:17:06 +00:00
test_network_advanced_server_ops.py Skip test_server_connectivity_cold_migration_revert until fixed 2018-09-15 11:37:42 -04:00
test_network_basic_ops.py Merge "Add extra_msg and server parameter to check_vm_connectivity" 2018-07-24 11:16:40 +00:00
test_network_v6.py Mark network slow test as slow 2018-11-02 08:00:21 +00:00
test_object_storage_basic_ops.py Fix senario test: test_swift_acl_anonymous_download 2017-10-09 16:58:10 +08:00
test_security_groups_basic_ops.py Use base.get_host_for_server to get server host 2018-08-23 09:55:17 +08:00
test_server_advanced_ops.py Trivial docstring cleanup in TestServerAdvancedOps 2018-04-25 16:17:03 -04:00
test_server_basic_ops.py Refactor config drive mounting 2018-02-19 10:16:13 -05:00
test_server_multinode.py Move test decorators to common 2017-08-23 17:09:33 +00:00
test_shelve_instance.py Log server console output during create/get timestamp 2018-07-30 22:46:56 +02:00
test_snapshot_pattern.py Log server console output during create/get timestamp 2018-07-30 22:46:56 +02:00
test_stamp_pattern.py Log server console output during create/get timestamp 2018-07-30 22:46:56 +02:00
test_volume_backup_restore.py Add status check for creating volume backup 2018-06-19 01:08:28 +00:00
test_volume_boot_pattern.py Delete snapshot in test_image_defined_boot_from_volume 2018-08-09 03:50:41 +00:00
test_volume_migrate_attached.py Make volume client alias with _latest suffix 2018-08-07 05:33:48 +00:00

README.rst

Tempest Field Guide to Scenario tests

What are these tests?

Scenario tests are "through path" tests of OpenStack function. Complicated setups where one part might depend on completion of a previous part. They ideally involve the integration between multiple OpenStack services to exercise the touch points between them.

Any scenario test should have a real-life use case. An example would be:

  • "As operator I want to start with a blank environment":
    1. upload a glance image
    2. deploy a vm from it
    3. ssh to the guest
    4. create a snapshot of the vm

Why are these tests in Tempest?

This is one of Tempest's core purposes, testing the integration between projects.

Scope of these tests

Scenario tests should always use the Tempest implementation of the OpenStack API, as we want to ensure that bugs aren't hidden by the official clients.

Tests should be tagged with which services they exercise, as determined by which client libraries are used directly by the test.

Example of a good test

While we are looking for interaction of 2 or more services, be specific in your interactions. A giant "this is my data center" smoke test is hard to debug when it goes wrong.

A flow of interactions between Glance and Nova, like in the introduction, is a good example. Especially if it involves a repeated interaction when a resource is setup, modified, detached, and then reused later again.