search

allankp / pytest-testrail

pytest plugin for integration with TestRail, for creating testruns and updating results
MIT License
96 stars 124 forks source link

Additional logic to call add_plan_entry #92

Closed conversica-aaronpa closed 5 years ago

conversica-aaronpa commented 5 years ago

Additional logic to call add_plan_entry in place of add_run when a test run id is supplied but no run id

conversica-aaronpa commented 5 years ago

Calling pytest with following appended:

--testrail --tr-config=testrail.cfg --tr-password=MyRealPassword --tr-plan-id=70

Example output:

python3 -m pytest -m dashboard_leadmanager_listview_status --junitxml logs/out_report.xml --html /logs/out_report.html --variables /config/config.json --testrail --tr-config=testrail.cfg --tr-password=MyRealPassword --tr-plan-id=70
============================= test session starts ==============================
platform linux -- Python 3.6.8, pytest-4.3.1, py-1.8.0, pluggy-0.9.0
pytest-testrail: existing testplan #70 selected
rootdir: /, inifile:
plugins: variables-1.7.1, testrail-2.3.3, metadata-1.8.0, html-1.20.0, cov-2.6.1
collecting 46 items                                                            [testrail] New testrun created in  test_plan_id=70 with name "Automated Run 12-03-2019 21:26:26" and ID=150
collected 60 items / 59 deselected / 1 selected                                

tests/menu_walk/test_leadmanager_listview.py .                           [100%][testrail] Start publishing
[testrail] Testcases to publish: 647
[testrail] End publishing
conversica-aaronpa commented 5 years ago

Working on adding unit tests; is there example output of the current expected results? I've gotten the tests to run and am seeing a depreciation warning that I assume is currently in there, but I'm also going to include some version bumps on the pytest dependencies.

conversica-aaronpa commented 5 years ago

This Travis build failure is confusing to me, would love to have a brief explanation why the failure occured.

apallier commented 5 years ago

@conversica-aaronpa I think Travis CI failed since you update versions of pytest and pytest-cov

conversica-aaronpa commented 5 years ago

@conversica-aaronpa I think Travis CI failed since you update versions of pytest and pytest-cov

Is there a reason to keep the older versions? External dependencies? Should I revert the change?

allankp commented 5 years ago

@conversica-aaronpa I think Travis CI failed since you update versions of pytest and pytest-cov

Is there a reason to keep the older versions? External dependencies? Should I revert the change?

I now think its time to drop support for py27, py3 is now mainstream. So can you update the tox to

[tox] distribute = false envlist = {py3}-test skip_missing_interpreters = true

[testenv]
basepython =
    py3: python3
commands = py.test [] tests/test_plugin.py --junitxml=pytests_{envname}.xml --cov-report=xml --cov=pytest_testrail
deps =
    -rrequirements/testing.txt

Which means you will be left with a failing test, which I am going to have a look at now. (I'll update this comment)

conversica-aaronpa commented 5 years ago

@conversica-aaronpa I think Travis CI failed since you update versions of pytest and pytest-cov

Is there a reason to keep the older versions? External dependencies? Should I revert the change?

I now think its time to drop support for py27, py3 is now mainstream. So can you update the tox to

Done: https://github.com/allankp/pytest-testrail/pull/92/commits/c81205c09ab9c903cc5ef8548329d08db936a238

conversica-aaronpa commented 5 years ago

Anyone interested in helping with this PR (still)? I'd like to get it merged, but am in the weeds on getting proper unit tests set up.

conversica-aaronpa commented 5 years ago

Anyone interested in helping on this PR? I'm using the code on a private branch, but don't have time to figure out how to satisfy the build requirements for this very simple but useful addition.

allankp commented 5 years ago

Closing this for now, don't have time at the moment to look at this. Its also become completely inactivate.

apailthorp commented 5 years ago

Yes, I couldn't figure out how to resolve the issues around running the tests, hence the inactivity. I'm hopeful that the recent activity that has gone on will be helpful for my scenario, wanting to create test sets on the fly.