{"action":"created","issue":{"url":"https://api.github.com/repos/SatelliteQE/robottelo/issues/3083","labels_url":"https://api.github.com/repos/SatelliteQE/robottelo/issues/3083/labels{/name}","comments_url":"https://api.github.com/repos/SatelliteQE/robottelo/issues/3083/comments","events_url":"https://api.github.com/repos/SatelliteQE/robottelo/issues/3083/events","html_url":"https://github.com/SatelliteQE/robottelo/issues/3083","id":119004536,"number":3083,"title":"Tests naming conventions","user":{"login":"oshtaier","id":10895065,"avatar_url":"https://avatars.githubusercontent.com/u/10895065?v=3","gravatar_id":"","url":"https://api.github.com/users/oshtaier","html_url":"https://github.com/oshtaier","followers_url":"https://api.github.com/users/oshtaier/followers","following_url":"https://api.github.com/users/oshtaier/following{/other_user}","gists_url":"https://api.github.com/users/oshtaier/gists{/gist_id}","starred_url":"https://api.github.com/users/oshtaier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oshtaier/subscriptions","organizations_url":"https://api.github.com/users/oshtaier/orgs","repos_url":"https://api.github.com/users/oshtaier/repos","events_url":"https://api.github.com/users/oshtaier/events{/privacy}","received_events_url":"https://api.github.com/users/oshtaier/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/SatelliteQE/robottelo/labels/Infrastructure","name":"Infrastructure","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":23,"created_at":"2015-11-26T09:31:01Z","updated_at":"2015-12-07T16:52:25Z","closed_at":null,"body":"Here we like to describe some rules that should be used when we name our tests in our development. All of them, of course, cannot be applied for each and every situation, but, anyway, should be treated as generic template.\r\n\r\n**All tests**\r\n- Should be started from word `test` (`test_xxxxxxxx`)\r\n- `positive` or `negative` term should be used as second word (`test_positive_xxxxxxxx` or `test_negative_xxxxxxxx`)\r\n\r\n**First Tier**\r\n- Test name should always contain one from `create`, `update` or `delete` terms as third word (`test_postive_create_xxxxxxxx` or `test_negative_update_xxxxxxxx`)\r\n\r\n**Second Tier**\r\n- Test name should contain action that is planned to be performed as third word (`test_positive_publish_xxxxxxxx` or `test_negative_add_xxxxxxxx``)\r\n\r\n**Third Tier**\r\n- Same as for tier two, but also can contain words like `long`, `end-to-end` or `infrastructure`.\r\n\r\n**General requirements**\r\n- After these three words we should briefly describe goal of particular test (`test_positive_publish_composite_cv` or `test_positive_associate_custom_content`). That can help in further test failures analyze procedure as it is easier to remember precise names\r\n- We do not need to specify feature under test in a test name (for example, state `test_positive_cv_promote` explicitly for `test_content_view.py` module as it is already obvious that we are testing content view functionality and use `test_positive_promote` instead)\r\n- Do not use numbers to specify amount of tests in corresponding direction (e.g. `test_positive_create_1` or `test_negative_add_15`)\r\n- There is an exception for cases that are testing specific Bugzilla issue as we can use `test_bugzilla_xxxxxxxx` as a test name"},"comment":{"url":"https://api.github.com/repos/SatelliteQE/robottelo/issues/comments/162590224","html_url":"https://github.com/SatelliteQE/robottelo/issues/3083#issuecomment-162590224","issue_url":"https://api.github.com/repos/SatelliteQE/robottelo/issues/3083","id":162590224,"user":{"login":"omaciel","id":53362,"avatar_url":"https://avatars.githubusercontent.com/u/53362?v=3","gravatar_id":"","url":"https://api.github.com/users/omaciel","html_url":"https://github.com/omaciel","followers_url":"https://api.github.com/users/omaciel/followers","following_url":"https://api.github.com/users/omaciel/following{/other_user}","gists_url":"https://api.github.com/users/omaciel/gists{/gist_id}","starred_url":"https://api.github.com/users/omaciel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/omaciel/subscriptions","organizations_url":"https://api.github.com/users/omaciel/orgs","repos_url":"https://api.github.com/users/omaciel/repos","events_url":"https://api.github.com/users/omaciel/events{/privacy}","received_events_url":"https://api.github.com/users/omaciel/received_events","type":"User","site_admin":false},"created_at":"2015-12-07T16:52:25Z","updated_at":"2015-12-07T16:52:25Z","body":"@oshtaier definitely need a separate issue for this."}}