devolo/pytest-adaptavist

pytest plugin generating test execution results within Jira Test Management (tm4j)

pytest-adaptavist's Issues

Disable if jira_server is not set

I see errors lie request failed. Invalid URL '/rest/api/2/user/search?username=.&startAt=0&maxResults=200': No schema supplied. in the pytest startup, due to jira_server not being set.

The plugin should be inactive unless it has been given the required config values

if jira unauthorised jira_username then test_run_key is inored and all tests collected to execute

pytest-adaptavist/pytest_adaptavist/_pytest_adaptavist.py

Line 863 in e833a30

test_run = self.adaptavist.get_test_run(self.test_run_key)

Use library with Zephyr Scale 8.0.2-jira7

Hello ! Will this library work with Zephyr Scale 8.0.2-jira7?
Now i used :
`@pytest.mark.project(project_key="PPP", test_run_suffix="11111")
class TestSCM(object):
arm = None
scm_dsr = None

def test_T9299(self, meta_data):`

And I expect that a test run will be created and a test case with the key T9299 is attached to it. What am I doing wrong?

Test cases are not attached to test run

Hello. We're having a trouble with test cases.
I've created Test object and added methods with test_[test-case-key] syntax, and after running, it only creates new test cycle, with no test cases attached to it. All keys are correct. Project key is also added to global_config file.

@pytest.mark.project(project_key="TEST")
class TestIACM(object):
    def test_T8254(self, meta_data):

Is there any parameter in config that I might have missed? Or there is other way to add test cases to the cycle?

Support for a blockif decorator

We could implement a blockif decorator. Behaves just like the skipif decorator but with a blocked testcase in adaptavist afterwards

Adaptavists API 2.0 call to get users not working for jira cloud

adaptavists.py -> get_users()

possibly just some limitations due to the version of adaptavists used.
I believe the API endpoint used will need to be updated to API 3.0 where users will need to specify atlassian ID and just verify it exists.

{"errorMessages":["The query parameter 'username' is not supported in GDPR strict mode."],"errors":{}}

found this on atlassian forumns:

https://community.atlassian.com/t5/Advanced-Roadmaps-questions/error-quot-The-query-parameter-username-is-not-supported-in-GDPR/qaq-p/1365942

and some official documentation here
https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/

Use decorators on test cases to specify test_key and step vs renaming test function with test_key and step

feature request

Use decorators on test cases to specify test_key and step vs renaming test function with test_key and step

Instead of this

@pytest.mark.project(project_key="myproject")
class TestAPI(unittest.TestCase):
    def test_T1_1(self):
        ...

this

@pytest.mark.project(project_key="myproject")
class TestAPI(unittest.TestCase):
    @pytest.mark.test(test_key="T1", test_step=1)
    def test_api_get_obj(self):
        ...