From ssbarnea at redhat.com  Tue Sep  8 09:06:28 2020
From: ssbarnea at redhat.com (Sorin Sbarnea)
Date: Tue, 8 Sep 2020 14:06:28 +0100
Subject: [pytest-dev] Using meta project for organization wide issues
Message-ID: <4A439224-F443-47E6-B377-6C3BA687D3E6@redhat.com>

About two weeks ago I created the https://github.com/pytest-dev/meta project with the hope of being used for tracking organization wide issues (and avoid having to pollute our main pytest project).

I seen use of "meta" on many github organizations for the same purpose, "stuff" that is unrelated to the code of a specific repository. I hope it will become popular. I do also see other benefits as used of a mailing list sets a higher barrier for people that are not yet fully dedicated (we do all know experienced the "Ahh not another ML!" sensation).

Early today I also added the first ticket, the proposal for adoption of the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1 and comment there.

Cheers,
Sorin


From arseny.antonov at gmail.com  Tue Sep  8 09:54:42 2020
From: arseny.antonov at gmail.com (Arseniy Antonov)
Date: Tue, 8 Sep 2020 16:54:42 +0300
Subject: [pytest-dev] Using meta project for organization wide issues
In-Reply-To: <4A439224-F443-47E6-B377-6C3BA687D3E6@redhat.com>
References: <4A439224-F443-47E6-B377-6C3BA687D3E6@redhat.com>
Message-ID: <CALPRNShtpQBL0TdYg9Ojc=v8mNX5-Pji9+_u0R1oGs-Z=p85WQ@mail.gmail.com>

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 other messenger) group for pytest community?

??, 8 ????. 2020 ?. ? 16:07, Sorin Sbarnea <ssbarnea at redhat.com>:

> About two weeks ago I created the https://github.com/pytest-dev/meta
> project with the hope of being used for tracking organization wide issues
> (and avoid having to pollute our main pytest project).
>
> I seen use of "meta" on many github organizations for the same purpose,
> "stuff" that is unrelated to the code of a specific repository. I hope it
> will become popular. I do also see other benefits as used of a mailing list
> sets a higher barrier for people that are not yet fully dedicated (we do
> all know experienced the "Ahh not another ML!" sensation).
>
> Early today I also added the first ticket, the proposal for adoption of
> the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1 and
> comment there.
>
> Cheers,
> Sorin
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>


-- 
--------------------------
Regards.
Arseny Antonov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200908/f97720bf/attachment.html>

From ssbarnea at redhat.com  Tue Sep  8 10:07:54 2020
From: ssbarnea at redhat.com (Sorin Sbarnea)
Date: Tue, 8 Sep 2020 15:07:54 +0100
Subject: [pytest-dev] Using meta project for organization wide issues
In-Reply-To: <CALPRNShtpQBL0TdYg9Ojc=v8mNX5-Pji9+_u0R1oGs-Z=p85WQ@mail.gmail.com>
References: <4A439224-F443-47E6-B377-6C3BA687D3E6@redhat.com>
 <CALPRNShtpQBL0TdYg9Ojc=v8mNX5-Pji9+_u0R1oGs-Z=p85WQ@mail.gmail.com>
Message-ID: <EB559712-7C5D-45F5-A063-C735E2130998@redhat.com>

My intent was to separate organization threads from the development ones, not to deprecate the mailing list.

I do not think that an issue tracker is good for **discussions** as in open-ended subjects, or even for support. In fact using the issue tracker for user support is really bad as it make maintenance much harder.

Still, there is something new from github called discussions which is a very basic forum directly integrated into github. 

You can see it as https://github.com/ansible-community/molecule/discussions -- not very active but functional.

Discussions are in private beta, and we need to ask github to enable them. 

If anyone wants to enable it for "pytest", I could try to pull some strings. If desired, an org/repo admin should ask for it at https://github.community/t/can-one-apply-for-github-discussions-beta/121120 


> On 8 Sep 2020, at 14:54, Arseniy Antonov <arseny.antonov at gmail.com> wrote:
> 
> 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 other messenger) group for pytest community? 
> 
> ??, 8 ????. 2020 ?. ? 16:07, Sorin Sbarnea <ssbarnea at redhat.com>:
> About two weeks ago I created the https://github.com/pytest-dev/meta project with the hope of being used for tracking organization wide issues (and avoid having to pollute our main pytest project).
> 
> I seen use of "meta" on many github organizations for the same purpose, "stuff" that is unrelated to the code of a specific repository. I hope it will become popular. I do also see other benefits as used of a mailing list sets a higher barrier for people that are not yet fully dedicated (we do all know experienced the "Ahh not another ML!" sensation).
> 
> Early today I also added the first ticket, the proposal for adoption of the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1 and comment there.
> 
> Cheers,
> Sorin
> 
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
> 
> 
> -- 
> --------------------------
> Regards.
> Arseny Antonov


From nicoddemus at gmail.com  Wed Sep  9 07:32:11 2020
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 9 Sep 2020 08:32:11 -0300
Subject: [pytest-dev] Using meta project for organization wide issues
In-Reply-To: <EB559712-7C5D-45F5-A063-C735E2130998@redhat.com>
References: <4A439224-F443-47E6-B377-6C3BA687D3E6@redhat.com>
 <CALPRNShtpQBL0TdYg9Ojc=v8mNX5-Pji9+_u0R1oGs-Z=p85WQ@mail.gmail.com>
 <EB559712-7C5D-45F5-A063-C735E2130998@redhat.com>
Message-ID: <CA+RQFfdhmE2oxXxfaCXt_cY7yh1XkQhJkHfQ6H3prdGZxmxwmQ@mail.gmail.com>

Thanks Sorin for bringing this up.

I've posted a request to enable the Discussions feature for
pytest-dev/pytest:
https://github.community/t/can-one-apply-for-github-discussions-beta/121120/162?u=nicoddemus

Cheers,
Bruno.

On Tue, Sep 8, 2020 at 11:08 AM Sorin Sbarnea <ssbarnea at redhat.com> wrote:

> My intent was to separate organization threads from the development ones,
> not to deprecate the mailing list.
>
> I do not think that an issue tracker is good for **discussions** as in
> open-ended subjects, or even for support. In fact using the issue tracker
> for user support is really bad as it make maintenance much harder.
>
> Still, there is something new from github called discussions which is a
> very basic forum directly integrated into github.
>
> You can see it as
> https://github.com/ansible-community/molecule/discussions -- not very
> active but functional.
>
> Discussions are in private beta, and we need to ask github to enable them.
>
> If anyone wants to enable it for "pytest", I could try to pull some
> strings. If desired, an org/repo admin should ask for it at
> https://github.community/t/can-one-apply-for-github-discussions-beta/121120
>
>
> > On 8 Sep 2020, at 14:54, Arseniy Antonov <arseny.antonov at gmail.com>
> wrote:
> >
> > 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 other messenger) group for pytest community?
> >
> > ??, 8 ????. 2020 ?. ? 16:07, Sorin Sbarnea <ssbarnea at redhat.com>:
> > About two weeks ago I created the https://github.com/pytest-dev/meta
> project with the hope of being used for tracking organization wide issues
> (and avoid having to pollute our main pytest project).
> >
> > I seen use of "meta" on many github organizations for the same purpose,
> "stuff" that is unrelated to the code of a specific repository. I hope it
> will become popular. I do also see other benefits as used of a mailing list
> sets a higher barrier for people that are not yet fully dedicated (we do
> all know experienced the "Ahh not another ML!" sensation).
> >
> > Early today I also added the first ticket, the proposal for adoption of
> the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1 and
> comment there.
> >
> > Cheers,
> > Sorin
> >
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
> >
> > --
> > --------------------------
> > Regards.
> > Arseny Antonov
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20200909/a1a9f54d/attachment.html>

From nicoddemus at gmail.com  Thu Sep 10 12:30:03 2020
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 10 Sep 2020 13:30:03 -0300
Subject: [pytest-dev] Using meta project for organization wide issues
In-Reply-To: <CA+RQFfdhmE2oxXxfaCXt_cY7yh1XkQhJkHfQ6H3prdGZxmxwmQ@mail.gmail.com>
References: <4A439224-F443-47E6-B377-6C3BA687D3E6@redhat.com>
 <CALPRNShtpQBL0TdYg9Ojc=v8mNX5-Pji9+_u0R1oGs-Z=p85WQ@mail.gmail.com>
 <EB559712-7C5D-45F5-A063-C735E2130998@redhat.com>
 <CA+RQFfdhmE2oxXxfaCXt_cY7yh1XkQhJkHfQ6H3prdGZxmxwmQ@mail.gmail.com>
Message-ID: <CA+RQFfeyFSOYzRCEr8Mx-fW=dRCNanUjb4q6bu-zG3VC3_cLPQ@mail.gmail.com>

Hi everyone,

The Discussions feature is now enabled.

Let's see how best we can use this feature to declutter the issue tracker
if possible, and create a good knowledge base of problems/solutions.

Cheers,

On Wed, Sep 9, 2020 at 8:32 AM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Thanks Sorin for bringing this up.
>
> I've posted a request to enable the Discussions feature for
> pytest-dev/pytest:
> https://github.community/t/can-one-apply-for-github-discussions-beta/121120/162?u=nicoddemus
>
> Cheers,
> Bruno.
>
> On Tue, Sep 8, 2020 at 11:08 AM Sorin Sbarnea <ssbarnea at redhat.com> wrote:
>
>> My intent was to separate organization threads from the development ones,
>> not to deprecate the mailing list.
>>
>> I do not think that an issue tracker is good for **discussions** as in
>> open-ended subjects, or even for support. In fact using the issue tracker
>> for user support is really bad as it make maintenance much harder.
>>
>> Still, there is something new from github called discussions which is a
>> very basic forum directly integrated into github.
>>
>> You can see it as
>> https://github.com/ansible-community/molecule/discussions -- not very
>> active but functional.
>>
>> Discussions are in private beta, and we need to ask github to enable
>> them.
>>
>> If anyone wants to enable it for "pytest", I could try to pull some
>> strings. If desired, an org/repo admin should ask for it at
>> https://github.community/t/can-one-apply-for-github-discussions-beta/121120
>>
>>
>> > On 8 Sep 2020, at 14:54, Arseniy Antonov <arseny.antonov at gmail.com>
>> wrote:
>> >
>> > 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 other messenger) group for pytest community?
>> >
>> > ??, 8 ????. 2020 ?. ? 16:07, Sorin Sbarnea <ssbarnea at redhat.com>:
>> > About two weeks ago I created the https://github.com/pytest-dev/meta
>> project with the hope of being used for tracking organization wide issues
>> (and avoid having to pollute our main pytest project).
>> >
>> > I seen use of "meta" on many github organizations for the same purpose,
>> "stuff" that is unrelated to the code of a specific repository. I hope it
>> will become popular. I do also see other benefits as used of a mailing list
>> sets a higher barrier for people that are not yet fully dedicated (we do
>> all know experienced the "Ahh not another ML!" sensation).
>> >
>> > Early today I also added the first ticket, the proposal for adoption of
>> the testinfra plugin, see https://github.com/pytest-dev/meta/issues/1
>> and comment there.
>> >
>> > Cheers,
>> > Sorin
>> >
>> > _______________________________________________
>> > pytest-dev mailing list
>> > pytest-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>> >
>> >
>> > --
>> > --------------------------
>> > Regards.
>> > Arseny Antonov
>>
>> _______________________________________________
>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20200910/7fbf4a09/attachment.html>

From ran at unusedvar.com  Fri Sep 11 19:21:57 2020
From: ran at unusedvar.com (Ran Benita)
Date: Sat, 12 Sep 2020 02:21:57 +0300
Subject: [pytest-dev] pytest-6.0.2
Message-ID: <22930ef4-6409-443a-89a9-d177efad77ae@www.fastmail.com>

pytest 6.0.2 has just been released to PyPI.

This is a bug-fix release, being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.

Thanks to all of the contributors to this release:

* Bruno Oliveira
* Ran Benita

Happy testing,
The pytest Development Team

From sivaramshibu at live.com  Sat Sep 12 07:08:06 2020
From: sivaramshibu at live.com (sivaram shibu)
Date: Sat, 12 Sep 2020 11:08:06 +0000
Subject: [pytest-dev] Plugin for test suite execution
Message-ID: <MN2PR02MB6925DC72DEA780FEE397CEE4B5250@MN2PR02MB6925.namprd02.prod.outlook.com>


Dear Admin,

                I was working in a project which uses Pytest framework for testing purpose and we were blocked when we encountered a situation were the test cases has to be executed in a user defined manner , so after doing proper research I have developed a plugin which have satisfied our need , so I thought of making this plugin a global one so other developers might use this feature in their work based on the requirement. Please find the code in the following repository and help me making this plugin a common one among the Pytest community , I was all open for any suggestions.

https://github.com/SivaRamSV/Pytest_Test_suite_sequence

Thanks and Regards,
Sivaram SV.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200912/8983d290/attachment.html>

From flub at devork.be  Sun Sep 13 15:05:26 2020
From: flub at devork.be (Floris Bruynooghe)
Date: Sun, 13 Sep 2020 21:05:26 +0200
Subject: [pytest-dev] Plugin for test suite execution
In-Reply-To: <MN2PR02MB6925DC72DEA780FEE397CEE4B5250@MN2PR02MB6925.namprd02.prod.outlook.com>
References: <MN2PR02MB6925DC72DEA780FEE397CEE4B5250@MN2PR02MB6925.namprd02.prod.outlook.com>
Message-ID: <87r1r5lcp5.fsf@powell.devork.be>

Hi Sivaram,

Hope you are well and nice that you wrote a pytest plugin!  As far as I
recall pytest by default already executes tests in the order they are
defined in the source code though.  I guess this was not expressive
enough for your needs?

As for advertising, it's best to follow the advice on
https://docs.pytest.org/en/stable/writing_plugins.html which mentions
how to use PyPI classifiers.  Also read about the plugin compat project
linked from there, making sure that finds your plugin is a good
indication of how discoverable your plugin is.

Finally, just be aware this is a mailing list of anyone interested in
pytest development and not specifically an admin person.  I'm just one
random person answering.

Cheers,
Floris

On Sat 12 Sep 2020 at 11:08 +0000, sivaram shibu wrote:

> Dear Admin,
>
>                 I was working in a project which uses Pytest framework for testing purpose and we were blocked when we encountered a situation were the test cases has to be executed in a user defined manner , so after doing proper research I have developed a plugin which have satisfied our need , so I thought of making this plugin a global one so other developers might use this feature in their work based on the requirement. Please find the code in the following repository and help me making this plugin a common one among the Pytest community , I was all open for any suggestions.
>
> https://github.com/SivaRamSV/Pytest_Test_suite_sequence
>
> Thanks and Regards,
> Sivaram SV.
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From sivaramshibu at live.com  Mon Sep 14 04:05:11 2020
From: sivaramshibu at live.com (sivaram shibu)
Date: Mon, 14 Sep 2020 08:05:11 +0000
Subject: [pytest-dev] Plugin for test suite execution
In-Reply-To: <87r1r5lcp5.fsf@powell.devork.be>
References: <MN2PR02MB6925DC72DEA780FEE397CEE4B5250@MN2PR02MB6925.namprd02.prod.outlook.com>,
 <87r1r5lcp5.fsf@powell.devork.be>
Message-ID: <MN2PR02MB69250FF9BE91A61B6C8EEB9FB5230@MN2PR02MB6925.namprd02.prod.outlook.com>

Hi Floris,
Thanks for the reply, hope you are doing good.

So basically in our setup we had a requirement in which we have to use unique python scripts for each and every test cases ,insted of having them in a single script.
And we had another requirement to change the executing order for different scenarios.
For example lets say I have a folder names "TESTS" and
 I have placed 3 test cases named

"test_109.py",
"test_298.py",
"test_301.py",

Now in one suite I want the execution order to be     test301 - test298 ? test109
And for another it has to be test298 - test301 - test109

Now instead of editing these test cases each and every time for changing the order sequence ,

I came up with an approach of storing these cases in a JSON called let say ?test_suite.JSON?  which contains the following data

{
            Scenario1 : {
?test_301? : 1,
                                    ?test_298? : 2,
                                    ?test_109? : 3,
                        },

Scenario2 : {
?test_298? : 1,
                                    ?test_301? : 2,
                                    ?test_109? : 3,
                        }
}


So the command would be ? pytest  ./TESTS --suite_cfg ./test_suite.json --suite_name Scenario1 ?

Where ,
suite_cfg and suite_name are the parser key word?s which I used in this plugin.

This plugin will be useful in scenario?s were the testcase name can?t be created in an order.

Note: we are using board farm so there will be some additional parameters to the above mentioned execution command which will contain the required config files.

So I hope now I have explained the need of this plugin and it would be really helpful if you could guide me in making this plugin available to the community. And thanks for letting me know about this mail thread.

Thanks and Regards,

Siva ram SV.



From: Floris Bruynooghe <floris.bruynooghe at gmail.com> on behalf of Floris Bruynooghe <flub at devork.be>
Sent: Monday, September 14, 2020 12:35:26 AM
To: sivaram shibu <sivaramshibu at live.com>; pytest-dev at python.org <pytest-dev at python.org>
Subject: Re: [pytest-dev] Plugin for test suite execution

Hi Sivaram,

Hope you are well and nice that you wrote a pytest plugin!  As far as I
recall pytest by default already executes tests in the order they are
defined in the source code though.  I guess this was not expressive
enough for your needs?

As for advertising, it's best to follow the advice on
https://docs.pytest.org/en/stable/writing_plugins.html which mentions
how to use PyPI classifiers.  Also read about the plugin compat project
linked from there, making sure that finds your plugin is a good
indication of how discoverable your plugin is.

Finally, just be aware this is a mailing list of anyone interested in
pytest development and not specifically an admin person.  I'm just one
random person answering.

Cheers,
Floris

On Sat 12 Sep 2020 at 11:08 +0000, sivaram shibu wrote:

> Dear Admin,
>
>                 I was working in a project which uses Pytest framework for testing purpose and we were blocked when we encountered a situation were the test cases has to be executed in a user defined manner , so after doing proper research I have developed a plugin which have satisfied our need , so I thought of making this plugin a global one so other developers might use this feature in their work based on the requirement. Please find the code in the following repository and help me making this plugin a common one among the Pytest community , I was all open for any suggestions.
>
> https://github.com/SivaRamSV/Pytest_Test_suite_sequence
>
> Thanks and Regards,
> Sivaram SV.
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20200914/dcdc35e5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: B98828A9F24B48F0A056A77076C2D166.png
Type: image/png
Size: 144 bytes
Desc: B98828A9F24B48F0A056A77076C2D166.png
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200914/dcdc35e5/attachment-0001.png>

From ran at unusedvar.com  Sat Sep 26 14:27:09 2020
From: ran at unusedvar.com (Ran Benita)
Date: Sat, 26 Sep 2020 21:27:09 +0300
Subject: [pytest-dev] pytest-6.1.0
Message-ID: <a8892ebf-d03a-468a-b61e-c2ada0092c90@www.fastmail.com>

The pytest team is proud to announce the 6.1.0 release!

This release contains new features, improvements, bug fixes, and breaking changes, so users
are encouraged to take a look at the CHANGELOG carefully:

    https://docs.pytest.org/en/stable/changelog.html

For complete documentation, please visit:

    https://docs.pytest.org/en/stable/

As usual, you can upgrade from PyPI via:

    pip install -U pytest

Thanks to all of the contributors to this release:

* Anthony Sottile
* Bruno Oliveira
* C. Titus Brown
* Drew Devereux
* Faris A Chugthai
* Florian Bruhin
* Hugo van Kemenade
* Hynek Schlawack
* Joseph Lucas
* Kamran Ahmad
* Mattreex
* Maximilian Cosmo Sitter
* Ran Benita
* R?diger Busche
* Sam Estep
* Sorin Sbarnea
* Thomas Grainger
* Vipul Kumar
* Yutaro Ikeda
* hp310780


Happy testing,
The pytest Development Team