Re: [pytest-dev] Do we have a place to introduce new plugins.

e: > > Hey, > > On Wed, Nov 18, 2020 at 11:15:02AM +0300, Arseniy Antonov wrote: > > Hi all, > > I think it would be great to have a single place like for example reddit > or > > something like that where anyone could be able to introduce and discuss > new > &

[pytest-dev] Do we have a place to introduce new plugins.

Hi all, I think it would be great to have a single place like for example reddit or something like that where anyone could be able to introduce and discuss new plugins or ask the community for support. Mailing lists quite outdated nowadays. I'm personally love them, mostly because you have to

Re: [pytest-dev] Using meta project for organization wide issues

Hi Sorin, So basically you want to move all projects related discussions from maillists to the github issues - did I get you correct? If the answer is yes then from my perspective it's a really nice idea. Also a lot of communities have #slack accounts - have you ever thought about the slack/(any

Re: [pytest-dev] Fwd: pytest-mimesis transfer to pytest-dev

I like this plugin too. Thank you for contributing. +1 . сб, 10 авг. 2019 г. в 14:41, Bruno Oliveira : > Great, thanks! > > Next step is to get approval from other core devs: > > > If no contributor strongly objects and two agree, the repository can > then be transferred to the pytest-dev

Re: [pytest-dev] Feedback requested on new plugin

Hello, Why don't you want to add markers to pytest.ini config? For now, you can add custom run options to the pytest.ini file. [pytest]addopts = -m my_marker But I agree that separate option for run marked tests would be better. [pytest]addopts = -s -v markers_to_run = my_marker1, my_marker2

Re: [pytest-dev] pytest slack reporting plugin proposal

Thanks! Will do it in 1 day. Also, GitHub is pretty friendly and routes all requests after transferring to the new URL. чт, 2 мая 2019 г. в 21:49, Bruno Oliveira : > > On Thu, May 2, 2019 at 3:45 PM Arseniy Antonov > wrote: > >> I've initialized transfer process to you (B

Re: [pytest-dev] pytest slack reporting plugin proposal

think. > > Cheers, > Floris > > [0] > https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev > > On Fri 26 Apr 2019 at 11:05 +0300, Arseniy Antonov wrote: > > > I would say that I'm going to support it, but I think that t

Re: [pytest-dev] pytest slack reporting plugin proposal

Hi, > What will you submit to the channel? Only the summary will be reported (number of tests, failed tests, skipped tests, errored tests) > I did not check the code but I suppose we can configure it. I've added 2 issues for this: 1st one for adding verbosity report level. 2nd one for the

Re: [pytest-dev] pytest slack reporting plugin proposal

t; the bus-effects we need to consider. > I believe this is a nice and useful addition, but we need to ensure that > long term maintenance under the pytest-dev umbrella is a reality. > > -- Ronny > > Am Mi., 24. Apr. 2019 um 12:00 Uhr schrieb Arseniy Antonov < > arseny.ant

[pytest-dev] pytest slack reporting plugin proposal

Hello, I've developed a plugin for sending pytest results to the slack. I suppose it may be a useful tool for the pytest community, so I want to contribute it to the pytest-dev. Please review: https://github.com/ArseniyAntonov/pytest-slack -- -- Regards. Arseny Antonov