From flub at devork.be Tue May 1 16:17:44 2018 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 01 May 2018 22:17:44 +0200 Subject: [pytest-dev] request to add pytest-echo to pytest-dev plugins In-Reply-To: References: Message-ID: <871sevyvtj.fsf@powell.devork.be> +1 from me too :) On Sun 29 Apr 2018 at 16:39 +0000, Bruno Oliveira wrote: > Hi Stefano, > > Yep according to our rules we still need one more +1. > > Cheers, > > On Sun, Apr 29, 2018 at 1:37 PM Stefano wrote: > >> Dear Bruno, >> >> thanks for your reply. >> >> I have to wait one more positive feedback before starting to transfer the >> ownership, is this correct ? >> >> >> Cheers, >> Stefano >> >> >> 2018-04-29 2:07 GMT+02:00 Bruno Oliveira : >> >>> Hi Stefano, >>> >>> The plugin meets all requirements so +1 from me. :) >>> >>> Cheers >>> >>> On Sat, Apr 28, 2018 at 2:18 PM Stefano wrote: >>> >>>> Hi, >>>> >>>> I did a very small plugin (pytest-echo), let me know if it can be added >>>> to the pytest-dev organization. >>>> >>>> Code can be found at https://github.com/saxix/pytest-echo >>>> >>>> >>>> Best, >>>> Stefano >>>> _______________________________________________ >>>> pytest-dev mailing list >>>> pytest-dev at python.org >>>> https://mail.python.org/mailman/listinfo/pytest-dev >>>> >>> >> > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From nicoddemus at gmail.com Tue May 1 16:37:02 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Tue, 01 May 2018 20:37:02 +0000 Subject: [pytest-dev] request to add pytest-echo to pytest-dev plugins In-Reply-To: <871sevyvtj.fsf@powell.devork.be> References: <871sevyvtj.fsf@powell.devork.be> Message-ID: Thanks Floris! Stefano feel free to transfer the repository to me (@nicoddemus) or Floris (@flub) and we can complete the transfer! Cheers, On Tue, May 1, 2018 at 5:17 PM Floris Bruynooghe wrote: > +1 from me too :) > > On Sun 29 Apr 2018 at 16:39 +0000, Bruno Oliveira wrote: > > > Hi Stefano, > > > > Yep according to our rules we still need one more +1. > > > > Cheers, > > > > On Sun, Apr 29, 2018 at 1:37 PM Stefano wrote: > > > >> Dear Bruno, > >> > >> thanks for your reply. > >> > >> I have to wait one more positive feedback before starting to transfer > the > >> ownership, is this correct ? > >> > >> > >> Cheers, > >> Stefano > >> > >> > >> 2018-04-29 2:07 GMT+02:00 Bruno Oliveira : > >> > >>> Hi Stefano, > >>> > >>> The plugin meets all requirements so +1 from me. :) > >>> > >>> Cheers > >>> > >>> On Sat, Apr 28, 2018 at 2:18 PM Stefano > wrote: > >>> > >>>> Hi, > >>>> > >>>> I did a very small plugin (pytest-echo), let me know if it can be > added > >>>> to the pytest-dev organization. > >>>> > >>>> Code can be found at https://github.com/saxix/pytest-echo > >>>> > >>>> > >>>> Best, > >>>> Stefano > >>>> _______________________________________________ > >>>> pytest-dev mailing list > >>>> pytest-dev at python.org > >>>> https://mail.python.org/mailman/listinfo/pytest-dev > >>>> > >>> > >> > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Wed May 2 07:15:03 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 02 May 2018 11:15:03 +0000 Subject: [pytest-dev] request to add pytest-echo to pytest-dev plugins In-Reply-To: References: <871sevyvtj.fsf@powell.devork.be> Message-ID: Stefano, Welcome to the pytest-dev organization! I've completed the transfer of pytest-echo, let me know if you encounter any problems! :) Cheers, On Tue, May 1, 2018 at 5:36 PM Bruno Oliveira wrote: > Thanks Floris! > > Stefano feel free to transfer the repository to me (@nicoddemus) or Floris > (@flub) and we can complete the transfer! > > Cheers, > > On Tue, May 1, 2018 at 5:17 PM Floris Bruynooghe wrote: > >> +1 from me too :) >> >> On Sun 29 Apr 2018 at 16:39 +0000, Bruno Oliveira wrote: >> >> > Hi Stefano, >> > >> > Yep according to our rules we still need one more +1. >> > >> > Cheers, >> > >> > On Sun, Apr 29, 2018 at 1:37 PM Stefano wrote: >> > >> >> Dear Bruno, >> >> >> >> thanks for your reply. >> >> >> >> I have to wait one more positive feedback before starting to transfer >> the >> >> ownership, is this correct ? >> >> >> >> >> >> Cheers, >> >> Stefano >> >> >> >> >> >> 2018-04-29 2:07 GMT+02:00 Bruno Oliveira : >> >> >> >>> Hi Stefano, >> >>> >> >>> The plugin meets all requirements so +1 from me. :) >> >>> >> >>> Cheers >> >>> >> >>> On Sat, Apr 28, 2018 at 2:18 PM Stefano >> wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I did a very small plugin (pytest-echo), let me know if it can be >> added >> >>>> to the pytest-dev organization. >> >>>> >> >>>> Code can be found at https://github.com/saxix/pytest-echo >> >>>> >> >>>> >> >>>> Best, >> >>>> Stefano >> >>>> _______________________________________________ >> >>>> pytest-dev mailing list >> >>>> pytest-dev at python.org >> >>>> https://mail.python.org/mailman/listinfo/pytest-dev >> >>>> >> >>> >> >> >> > _______________________________________________ >> > pytest-dev mailing list >> > pytest-dev at python.org >> > https://mail.python.org/mailman/listinfo/pytest-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.apostolico at gmail.com Wed May 2 07:35:49 2018 From: s.apostolico at gmail.com (Stefano) Date: Wed, 2 May 2018 13:35:49 +0200 Subject: [pytest-dev] request to add pytest-echo to pytest-dev plugins In-Reply-To: References: <871sevyvtj.fsf@powell.devork.be> Message-ID: Thanks a lot Bruno for help and support. Cheers, Stefano 2018-05-02 13:15 GMT+02:00 Bruno Oliveira : > Stefano, > > Welcome to the pytest-dev organization! I've completed the transfer of > pytest-echo, let me know if you encounter any problems! :) > > Cheers, > > On Tue, May 1, 2018 at 5:36 PM Bruno Oliveira > wrote: > >> Thanks Floris! >> >> Stefano feel free to transfer the repository to me (@nicoddemus) or >> Floris (@flub) and we can complete the transfer! >> >> Cheers, >> >> On Tue, May 1, 2018 at 5:17 PM Floris Bruynooghe wrote: >> >>> +1 from me too :) >>> >>> On Sun 29 Apr 2018 at 16:39 +0000, Bruno Oliveira wrote: >>> >>> > Hi Stefano, >>> > >>> > Yep according to our rules we still need one more +1. >>> > >>> > Cheers, >>> > >>> > On Sun, Apr 29, 2018 at 1:37 PM Stefano >>> wrote: >>> > >>> >> Dear Bruno, >>> >> >>> >> thanks for your reply. >>> >> >>> >> I have to wait one more positive feedback before starting to >>> transfer the >>> >> ownership, is this correct ? >>> >> >>> >> >>> >> Cheers, >>> >> Stefano >>> >> >>> >> >>> >> 2018-04-29 2:07 GMT+02:00 Bruno Oliveira : >>> >> >>> >>> Hi Stefano, >>> >>> >>> >>> The plugin meets all requirements so +1 from me. :) >>> >>> >>> >>> Cheers >>> >>> >>> >>> On Sat, Apr 28, 2018 at 2:18 PM Stefano >>> wrote: >>> >>> >>> >>>> Hi, >>> >>>> >>> >>>> I did a very small plugin (pytest-echo), let me know if it can be >>> added >>> >>>> to the pytest-dev organization. >>> >>>> >>> >>>> Code can be found at https://github.com/saxix/pytest-echo >>> >>>> >>> >>>> >>> >>>> Best, >>> >>>> Stefano >>> >>>> _______________________________________________ >>> >>>> pytest-dev mailing list >>> >>>> pytest-dev at python.org >>> >>>> https://mail.python.org/mailman/listinfo/pytest-dev >>> >>>> >>> >>> >>> >> >>> > _______________________________________________ >>> > pytest-dev mailing list >>> > pytest-dev at python.org >>> > https://mail.python.org/mailman/listinfo/pytest-dev >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From huaqin2005 at gmail.com Thu May 10 23:37:28 2018 From: huaqin2005 at gmail.com (Reed Xia) Date: Fri, 11 May 2018 11:37:28 +0800 Subject: [pytest-dev] Refactor the old tests with pytest Message-ID: Hi, In my project there are some API tests(with pytest) like following: /api_test test_device_api01_via_lan.py test_device_api02_via_lan.py test_device_api03_via_lan.py test_device_api01_via_wan.py test_device_api02_via_wan.py test_device_api03_via_wan.py As you see and you may guess, yes...the two set of test_*.py have the almost the same code, except they use the different global variable, one is LAN_URL the other is WAN_URL, looks stupid, right? :( So I want to refactor it, I think the two set of tests should not be seperated just because of an variable. but there's another problem, this test project run with Jenkins, launched by "python3 -m py.test --junitxml=./result/api_test_result.xml",so that Jenkins can collect the JUnit formate xml file. I think I easily to launch the tests in loop by giving LAN_URL and WAN_URL, but I didn't figure out how to generate a JUnit XML file in this way, can someone please share some ideas? Thanks, Reed -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri May 11 06:19:05 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 11 May 2018 07:19:05 -0300 Subject: [pytest-dev] Refactor the old tests with pytest In-Reply-To: References: Message-ID: Hi Reed, You should take a look at parametrizing[1] so you end up with only: /api_test test_device_api01.py test_device_api02.py test_device_api03.py And inside it all tests are parametrized based on LAN_URL and WAN_URL (possibly using a parametrized fixture if it is more convenient). Report generation will remain unaffected. Hope this helps, Bruno. [1] https://docs.pytest.org/en/latest/parametrize.html On Fri, May 11, 2018 at 12:38 AM Reed Xia wrote: > Hi, > > In my project there are some API tests(with pytest) like following: > > /api_test > test_device_api01_via_lan.py > test_device_api02_via_lan.py > test_device_api03_via_lan.py > > test_device_api01_via_wan.py > test_device_api02_via_wan.py > test_device_api03_via_wan.py > > As you see and you may guess, yes...the two set of test_*.py have the > almost the same code, except they use the different global variable, one is > LAN_URL the other is WAN_URL, looks stupid, right? :( > > So I want to refactor it, I think the two set of tests should not be > seperated just because of an variable. > > but there's another problem, this test project run with Jenkins, launched > by "python3 -m py.test --junitxml=./result/api_test_result.xml",so that > Jenkins can collect the JUnit formate xml file. > > I think I easily to launch the tests in loop by giving LAN_URL and > WAN_URL, but I didn't figure out how to generate a JUnit XML file in this > way, can someone please share some ideas? > > Thanks, > Reed > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From huaqin2005 at gmail.com Fri May 11 08:56:16 2018 From: huaqin2005 at gmail.com (Reed Xia) Date: Fri, 11 May 2018 20:56:16 +0800 Subject: [pytest-dev] Refactor the old tests with pytest In-Reply-To: References: Message-ID: Wow.. sound great! Thanks Bruno, I'll check! On Fri, May 11, 2018 at 6:19 PM, Bruno Oliveira wrote: > Hi Reed, > > You should take a look at parametrizing[1] so you end up with only: > > /api_test > test_device_api01.py > test_device_api02.py > test_device_api03.py > > And inside it all tests are parametrized based on LAN_URL and WAN_URL > (possibly using a parametrized fixture if it is more convenient). > > Report generation will remain unaffected. > > Hope this helps, > Bruno. > > [1] https://docs.pytest.org/en/latest/parametrize.html > > On Fri, May 11, 2018 at 12:38 AM Reed Xia wrote: > >> Hi, >> >> In my project there are some API tests(with pytest) like following: >> >> /api_test >> test_device_api01_via_lan.py >> test_device_api02_via_lan.py >> test_device_api03_via_lan.py >> >> test_device_api01_via_wan.py >> test_device_api02_via_wan.py >> test_device_api03_via_wan.py >> >> As you see and you may guess, yes...the two set of test_*.py have the >> almost the same code, except they use the different global variable, one is >> LAN_URL the other is WAN_URL, looks stupid, right? :( >> >> So I want to refactor it, I think the two set of tests should not be >> seperated just because of an variable. >> >> but there's another problem, this test project run with Jenkins, launched >> by "python3 -m py.test --junitxml=./result/api_test_result.xml",so that >> Jenkins can collect the JUnit formate xml file. >> >> I think I easily to launch the tests in loop by giving LAN_URL and >> WAN_URL, but I didn't figure out how to generate a JUnit XML file in this >> way, can someone please share some ideas? >> >> Thanks, >> Reed >> >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From huaqin2005 at gmail.com Fri May 11 11:07:32 2018 From: huaqin2005 at gmail.com (Reed Xia) Date: Fri, 11 May 2018 23:07:32 +0800 Subject: [pytest-dev] Refactor the old tests with pytest In-Reply-To: References: Message-ID: It works ? # content of conftest.py def pytest_generate_tests(metafunc): idlist = [] argvalues = [] for scenario in metafunc.cls.scenarios: idlist.append(scenario[0]) items = scenario[1].items() argnames = [x[0] for x in items] argvalues.append(([x[1] for x in items])) metafunc.parametrize(argnames, argvalues, ids=idlist, scope="class") scenario1 = ('LAN', {'URL': 'www.baidu.com'}) scenario2 = ('WAN', {'URL': 'www.sohu.com'}) # content of a test_ import pytest from conftest import scenario1, scenario2 class TestLogin(object): scenarios = [scenario1, scenario2] def test_login_01(self, URL): assert "www" in URL def test_login_02(self, URL): assert "ok" == "ok" def test_login_03(self, URL): assert "sohu" in URL ---- Now I'm having the tests... rx:pytest_proj reed$ pytest --collect-only tests/test_api01.py ============================================================= test session starts ============================================================= platform darwin -- Python 3.6.5, pytest-3.5.1, py-1.5.3, pluggy-0.6.0 rootdir: /Users/reed/Documents/dev/pytest_proj, inifile: collected 6 items Thanks Bruno and PYTEST!! On Fri, May 11, 2018 at 8:56 PM, Reed Xia wrote: > Wow.. sound great! Thanks Bruno, I'll check! > > On Fri, May 11, 2018 at 6:19 PM, Bruno Oliveira > wrote: > >> Hi Reed, >> >> You should take a look at parametrizing[1] so you end up with only: >> >> /api_test >> test_device_api01.py >> test_device_api02.py >> test_device_api03.py >> >> And inside it all tests are parametrized based on LAN_URL and WAN_URL >> (possibly using a parametrized fixture if it is more convenient). >> >> Report generation will remain unaffected. >> >> Hope this helps, >> Bruno. >> >> [1] https://docs.pytest.org/en/latest/parametrize.html >> >> On Fri, May 11, 2018 at 12:38 AM Reed Xia wrote: >> >>> Hi, >>> >>> In my project there are some API tests(with pytest) like following: >>> >>> /api_test >>> test_device_api01_via_lan.py >>> test_device_api02_via_lan.py >>> test_device_api03_via_lan.py >>> >>> test_device_api01_via_wan.py >>> test_device_api02_via_wan.py >>> test_device_api03_via_wan.py >>> >>> As you see and you may guess, yes...the two set of test_*.py have the >>> almost the same code, except they use the different global variable, one is >>> LAN_URL the other is WAN_URL, looks stupid, right? :( >>> >>> So I want to refactor it, I think the two set of tests should not be >>> seperated just because of an variable. >>> >>> but there's another problem, this test project run with Jenkins, >>> launched by "python3 -m py.test --junitxml=./result/api_test_result.xml",so >>> that Jenkins can collect the JUnit formate xml file. >>> >>> I think I easily to launch the tests in loop by giving LAN_URL and >>> WAN_URL, but I didn't figure out how to generate a JUnit XML file in this >>> way, can someone please share some ideas? >>> >>> Thanks, >>> Reed >>> >>> >>> _______________________________________________ >>> pytest-dev mailing list >>> pytest-dev at python.org >>> https://mail.python.org/mailman/listinfo/pytest-dev >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri May 11 11:10:48 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 11 May 2018 12:10:48 -0300 Subject: [pytest-dev] Refactor the old tests with pytest In-Reply-To: References: Message-ID: Cool, thanks for sharing the final solution Reed! On Fri, May 11, 2018 at 12:07 PM Reed Xia wrote: > It works ? > > # content of conftest.py > > def pytest_generate_tests(metafunc): > idlist = [] > argvalues = [] > for scenario in metafunc.cls.scenarios: > idlist.append(scenario[0]) > items = scenario[1].items() > argnames = [x[0] for x in items] > argvalues.append(([x[1] for x in items])) > metafunc.parametrize(argnames, argvalues, ids=idlist, scope="class") > > scenario1 = ('LAN', {'URL': 'www.baidu.com'}) > scenario2 = ('WAN', {'URL': 'www.sohu.com'}) > > # content of a test_ > > import pytest > from conftest import scenario1, scenario2 > > class TestLogin(object): > scenarios = [scenario1, scenario2] > > def test_login_01(self, URL): > assert "www" in URL > > def test_login_02(self, URL): > assert "ok" == "ok" > > def test_login_03(self, URL): > assert "sohu" in URL > > > ---- > Now I'm having the tests... > > rx:pytest_proj reed$ pytest --collect-only tests/test_api01.py > ============================================================= test session > starts ============================================================= > platform darwin -- Python 3.6.5, pytest-3.5.1, py-1.5.3, pluggy-0.6.0 > rootdir: /Users/reed/Documents/dev/pytest_proj, inifile: > collected 6 items > > > > > > > > > > > Thanks Bruno and PYTEST!! > > On Fri, May 11, 2018 at 8:56 PM, Reed Xia wrote: > >> Wow.. sound great! Thanks Bruno, I'll check! >> >> On Fri, May 11, 2018 at 6:19 PM, Bruno Oliveira >> wrote: >> >>> Hi Reed, >>> >>> You should take a look at parametrizing[1] so you end up with only: >>> >>> /api_test >>> test_device_api01.py >>> test_device_api02.py >>> test_device_api03.py >>> >>> And inside it all tests are parametrized based on LAN_URL and WAN_URL >>> (possibly using a parametrized fixture if it is more convenient). >>> >>> Report generation will remain unaffected. >>> >>> Hope this helps, >>> Bruno. >>> >>> [1] https://docs.pytest.org/en/latest/parametrize.html >>> >>> On Fri, May 11, 2018 at 12:38 AM Reed Xia wrote: >>> >>>> Hi, >>>> >>>> In my project there are some API tests(with pytest) like following: >>>> >>>> /api_test >>>> test_device_api01_via_lan.py >>>> test_device_api02_via_lan.py >>>> test_device_api03_via_lan.py >>>> >>>> test_device_api01_via_wan.py >>>> test_device_api02_via_wan.py >>>> test_device_api03_via_wan.py >>>> >>>> As you see and you may guess, yes...the two set of test_*.py have the >>>> almost the same code, except they use the different global variable, one is >>>> LAN_URL the other is WAN_URL, looks stupid, right? :( >>>> >>>> So I want to refactor it, I think the two set of tests should not be >>>> seperated just because of an variable. >>>> >>>> but there's another problem, this test project run with Jenkins, >>>> launched by "python3 -m py.test >>>> --junitxml=./result/api_test_result.xml",so that Jenkins can collect the >>>> JUnit formate xml file. >>>> >>>> I think I easily to launch the tests in loop by giving LAN_URL and >>>> WAN_URL, but I didn't figure out how to generate a JUnit XML file in this >>>> way, can someone please share some ideas? >>>> >>>> Thanks, >>>> Reed >>>> >>>> >>>> _______________________________________________ >>>> pytest-dev mailing list >>>> pytest-dev at python.org >>>> https://mail.python.org/mailman/listinfo/pytest-dev >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ilya.kazakevich at jetbrains.com Tue May 15 18:15:52 2018 From: ilya.kazakevich at jetbrains.com (Ilya Kazakevich) Date: Wed, 16 May 2018 01:15:52 +0300 Subject: [pytest-dev] hook to obtain parameters for parametrized test Message-ID: Hello. I write plugin for pytest, and I need to obtain parameters for test decorated with @parametrize before this test is actually called. There is a ``pytest_runtest_logstart``, but it does not provide information about parameters. There is ``pytest_runtest_setup`` but it is called too late. I belive ``runner.py`` (line 58) may provide this info to ``pytest_runtest_logstart``, but it does not. Is there any way to get information about test parameters before pytest launches it? Ilya. -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver at bestwalter.de Sun May 20 10:47:21 2018 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Sun, 20 May 2018 16:47:21 +0200 Subject: [pytest-dev] EuroPython 2018: help desk Message-ID: Hi, I will be attending the EuroPython and just submitted the same proposal like last year to run a pytest/tox/devpi helpdesk. Last year was fun and most people who came had not much experience with the tools yet and were looking for some help introducing automated testing in their projects. If any of you are also there and would like to hang out with me and help some folks to get their questions answered, I would be happy. I will let you know if the proposal was accepted. Cheers, Oliver -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Mon May 21 07:16:45 2018 From: flub at devork.be (Floris Bruynooghe) Date: Mon, 21 May 2018 13:16:45 +0200 Subject: [pytest-dev] hook to obtain parameters for parametrized test In-Reply-To: References: Message-ID: <87zi0tz2aq.fsf@powell.devork.be> Hi Ilya, On Wed 16 May 2018 at 01:15 +0300, Ilya Kazakevich wrote: > I write plugin for pytest, and I need to obtain parameters > for test decorated with @parametrize before this test is actually called. Could you describe a bit more what your use-case is? Why do you need to obtain these parameters and what do you intent to do with them. If you can provide a minimal example, even if still made-up, rather then something abstract that would also be of great help. This will help us understand your question better and figure out the correct way to answer it. Cheers, Floris From dhunt at mozilla.com Mon May 21 09:31:36 2018 From: dhunt at mozilla.com (Dave Hunt) Date: Mon, 21 May 2018 14:31:36 +0100 Subject: [pytest-dev] [tox-dev] EuroPython 2018: help desk In-Reply-To: References: Message-ID: Hey Oliver, I?m there Monday-Saturday and would be happy to help out where I can! Cheers, Dave > On 20 May 2018, at 15:47, Oliver Bestwalter wrote: > > Hi, > > I will be attending the EuroPython and just submitted the same proposal like last year to run a pytest/tox/devpi helpdesk. Last year was fun and most people who came had not much experience with the tools yet and were looking for some help introducing automated testing in their projects. > > If any of you are also there and would like to hang out with me and help some folks to get their questions answered, I would be happy. > > I will let you know if the proposal was accepted. > > Cheers, > Oliver > _______________________________________________ > tox-dev mailing list > tox-dev at python.org > https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From oliver at bestwalter.de Mon May 21 09:52:41 2018 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Mon, 21 May 2018 15:52:41 +0200 Subject: [pytest-dev] [tox-dev] EuroPython 2018: help desk In-Reply-To: References: Message-ID: Hi Dave, great! Looking forward to hang out with you :) Cheers, Oliver On Mon, 21 May 2018 at 15:31 Dave Hunt wrote: > Hey Oliver, > > I?m there Monday-Saturday and would be happy to help out where I can! > > Cheers, > Dave > > > On 20 May 2018, at 15:47, Oliver Bestwalter > wrote: > > > > Hi, > > > > I will be attending the EuroPython and just submitted the same proposal > like last year to run a pytest/tox/devpi helpdesk. Last year was fun and > most people who came had not much experience with the tools yet and were > looking for some help introducing automated testing in their projects. > > > > If any of you are also there and would like to hang out with me and help > some folks to get their questions answered, I would be happy. > > > > I will let you know if the proposal was accepted. > > > > Cheers, > > Oliver > > _______________________________________________ > > tox-dev mailing list > > tox-dev at python.org > > https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Wed May 23 07:05:34 2018 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 23 May 2018 08:05:34 -0300 Subject: [pytest-dev] pytest 3.6.0 released! Message-ID: The pytest team is proud to announce the 3.6.0 release! pytest is a mature Python testing tool with more than 2000 tests against itself, passing on many different interpreters and platforms. This release contains a major internal refactoring of how marks are handled, fixing a long number of long standing bugs. Users are strongly encouraged to read the related documentation: https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration As usual, the complete CHANGELOG can be found at: http://doc.pytest.org/en/latest/changelog.html For complete documentation, please visit: http://docs.pytest.org As usual, you can upgrade from pypi via: pip install -U pytest Thanks to all who contributed to this release, among them: * Anthony Shaw * ApaDoctor * Brian Maissy * Bruno Oliveira * Jon Dufresne * Katerina Koukiou * Miro Hron?ok * Rachel Kogan * Ronny Pfannschmidt * Tim Hughes * Tyler Goodlet * Ville Skytt? * aviral1701 * feuillemorte Happy testing, The Pytest Development Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver at bestwalter.de Thu May 31 08:51:29 2018 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Thu, 31 May 2018 14:51:29 +0200 Subject: [pytest-dev] [tox-dev] EuroPython 2018: help desk In-Reply-To: References: Message-ID: Hello all, I just got confirmation that the help desk proposal was accepted. See you in Scotland then :) Cheers, Oliver On Mon, 21 May 2018 at 15:52 Oliver Bestwalter wrote: > Hi Dave, > > great! Looking forward to hang out with you :) > > Cheers, > Oliver > > On Mon, 21 May 2018 at 15:31 Dave Hunt wrote: > >> Hey Oliver, >> >> I?m there Monday-Saturday and would be happy to help out where I can! >> >> Cheers, >> Dave >> >> > On 20 May 2018, at 15:47, Oliver Bestwalter >> wrote: >> > >> > Hi, >> > >> > I will be attending the EuroPython and just submitted the same proposal >> like last year to run a pytest/tox/devpi helpdesk. Last year was fun and >> most people who came had not much experience with the tools yet and were >> looking for some help introducing automated testing in their projects. >> > >> > If any of you are also there and would like to hang out with me and >> help some folks to get their questions answered, I would be happy. >> > >> > I will let you know if the proposal was accepted. >> > >> > Cheers, >> > Oliver >> > _______________________________________________ >> > tox-dev mailing list >> > tox-dev at python.org >> > https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: