Re: [pytest-dev] Configurable collection roots and reusable testsuites - Brainstorming

I think I'm the evil mastermind behind that idea. It's about collecting from places that cannot be represented as path arguments to `py.test`, like a runtime-defined place (a basic example would be if you want to collect something from site-p

Re: [pytest-dev] a potential alternative to the py.code merge

Hi Ronny, On Mon, Jan 25, 2016 at 00:38 +0100, Ronny Pfannschmidt wrote: > Hi everyone, > > this is probably a bit late, in particular since Bruno did already spend > a considerable amount of time, > > but instead of merging py.code for the exception repressentation, > i would like to propose in

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 07:03 +0100, Florian Bruhin wrote: > * Bruno Oliveira [2016-01-25 00:13:43 +]: > > If we abolish the features branch and still honor semantic versioning, it > > is very likely that every other release will increase the minor version... > > so we would have pytest 2.20.0

Re: [pytest-dev] Configurable collection roots and reusable testsuites - Brainstorming

Hi Ronny, Ionel, all, On Mon, Jan 25, 2016 at 00:46 +0100, Ronny Pfannschmidt wrote: > Hi everyone, > > a topic thats gripping since quite a while, is wanting to have reusable > testsuites, > so plugins/extensions that implement a behaviout, > can import and use integration tests from a installed

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 4:03 AM Florian Bruhin wrote: > I think the right route to go is to make releases easier (I think > Bruno is doing a great job on that!), and then maybe switch to > time-based releases rather than milestone-based releases like gitlab > does? > Thanks! :) I read that link

Re: [pytest-dev] pytest docs on readthedocs?

Hi Bruno, all, could you give me your handles on readthedocs so i can add you as maintainers to pytest.readthedocs.org? If we can maintain the current URL layout of pytest.org and have it served from rtfd i'd be fine with going for it. There are many references across the web into pytest.org UR

Re: [pytest-dev] pytest docs on readthedocs?

On Mon, Jan 25, 2016 at 8:38 AM holger krekel wrote: > Hi Bruno, all, > > could you give me your handles on readthedocs so i can add you as > maintainers > to pytest.readthedocs.org? > Mine is nicoddemus. > > If we can maintain the current URL layout of pytest.org and have it served > from rtf

Re: [pytest-dev] on abolishing the feature branch concept

I agree on the link article as well and like the model, i propose a time-frame of either 3 or 4 months for the feature releases. My personal preference is 3 months. I already started with trying to automate regendoc, my first attempt can be classified as failure. I'd like to discuss a new approa

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 9:06 AM Ronny Pfannschmidt < [email protected]> wrote: > I agree on the link article as well and like the model, > i propose a time-frame of either 3 or 4 months for the feature releases. > > My personal preference is 3 months. > I think that sounds good for

Re: [pytest-dev] on abolishing the feature branch concept

* Bruno Oliveira [2016-01-25 11:43:27 +]: > On Mon, Jan 25, 2016 at 9:06 AM Ronny Pfannschmidt < > [email protected]> wrote: > > > I agree on the link article as well and like the model, > > i propose a time-frame of either 3 or 4 months for the feature releases. > > > > My pers

Re: [pytest-dev] on abolishing the feature branch concept

For bugfix releases i would like to do them as soon as possible (i.e. try to stay within one day of the merge) that would also create more incentives for an better automation -- Ronny Am 25.01.2016 um 12:49 schrieb Florian Bruhin: > * Bruno Oliveira [2016-01-25 11:43:27 +]: >> On Mon, Jan 2

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 10:00 AM Ronny Pfannschmidt < [email protected]> wrote: > For bugfix releases i would like to do them as soon as possible > (i.e. try to stay within one day of the merge) > Hmmm what do you mean Ronny? A release after each bug fix is merged in? that would al

Re: [pytest-dev] TLS certificate expired

Hi all, i just setup letsencrypt for pytest.org and also auto-renewal per cron. Seems to work fine. Thanks everyone. best, holger On Sat, Jan 23, 2016 at 08:02 +1100, Brianna Laugher wrote: > Hi, > > It was pointed out on Twitter that our tls certificate has expired. > > Cheers > Brianna > _

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 9:49 AM Florian Bruhin wrote: > * Bruno Oliveira [2016-01-25 11:43:27 +]: > > I think that sounds good for the feature releases. For bug fix releases I > > think a shorter time frame makes more sense, how about every 2 weeks? We > > could prepare the release PR Thursd

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 12:03 +, Bruno Oliveira wrote: > On Mon, Jan 25, 2016 at 10:00 AM Ronny Pfannschmidt < > [email protected]> wrote: > > > For bugfix releases i would like to do them as soon as possible > > (i.e. try to stay within one day of the merge) > > > > Hmmm what d

Re: [pytest-dev] Configurable collection roots and reusable testsuites - Brainstorming

Im aware of that rudimentary mechanism, i would like to elevate a "testsuite" to a set of collected tests in filled with "dependencies" via fixtures that approach would also provide a more clean mechanism that are currently handled with session scoped fixtures that are parametrized one of such ex

Re: [pytest-dev] on abolishing the feature branch concept

i think we need to be much more strict on what a bugfix is for example the regression in 2.8.6 was caused by the "feature" of more detailed exceptions from monkeypatch if we go to a __strict__ handling of bugfixes, then much more of what had gone to the 2.8.6 release would have landed in the featu

Re: [pytest-dev] on abolishing the feature branch concept

* Ronny Pfannschmidt [2016-01-25 14:36:12 +0100]: > i think we need to be much more strict on what a bugfix is > for example the regression in 2.8.6 was caused by the "feature" > of more detailed exceptions from monkeypatch I agree this particular PR should've gone to 'features'. IMHO it'd have

Re: [pytest-dev] pytest docs on readthedocs?

On 25 January 2016 at 10:47, Bruno Oliveira wrote: > > > On Mon, Jan 25, 2016 at 8:38 AM holger krekel wrote: >> >> Hi Bruno, all, >> >> could you give me your handles on readthedocs so i can add you as >> maintainers >> to pytest.readthedocs.org? > > > Mine is nicoddemus. Mine is flub > >> >>

Re: [pytest-dev] pytest docs on readthedocs?

On Mon, Jan 25, 2016 at 12:18 PM Floris Bruynooghe wrote: > > I think the latter is certainly possible, since that's what fabric does: > > > > http://www.fabfile.org/ > > http://docs.fabfile.org/en/1.10/ > > +1 to this layout > I will study how to use this later Today. On a related note: I cha

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 12:04 PM Florian Bruhin wrote: > * Ronny Pfannschmidt [2016-01-25 > 14:36:12 +0100]: > > i think we need to be much more strict on what a bugfix is > > for example the regression in 2.8.6 was caused by the "feature" > > of more detailed exceptions from monkeypatch > > I a

Re: [pytest-dev] on abolishing the feature branch concept

Am 25.01.2016 um 15:04 schrieb Florian Bruhin: > * Ronny Pfannschmidt [2016-01-25 14:36:12 > +0100]: >> i think we need to be much more strict on what a bugfix is >> for example the regression in 2.8.6 was caused by the "feature" >> of more detailed exceptions from monkeypatch > I agree this pa

Re: [pytest-dev] on abolishing the feature branch concept

On Mon, Jan 25, 2016 at 12:42 PM Ronny Pfannschmidt < [email protected]> wrote: > Am 25.01.2016 um 15:04 schrieb Florian Bruhin: > > * Ronny Pfannschmidt [2016-01-25 > 14:36:12 +0100]: > >> to that effect it might even be sensible to change from master + > >> features to bugfix + ma

Re: [pytest-dev] a potential alternative to the py.code merge

i have ideas for replacing/changing it in the back of my head since a while now, so i'd like to have a reasonable/easy testbed also we could avoid the need for api compatibility even if we copy in py.code given that the old api would be available also exception representation is a very low-gangin

Re: [pytest-dev] pytest docs on readthedocs?

On Mon, Jan 25, 2016 at 14:18 +, Floris Bruynooghe wrote: > On 25 January 2016 at 10:47, Bruno Oliveira wrote: > > > > > > On Mon, Jan 25, 2016 at 8:38 AM holger krekel wrote: > >> > >> Hi Bruno, all, > >> > >> could you give me your handles on readthedocs so i can add you as > >> maintainers

Re: [pytest-dev] a potential alternative to the py.code merge

On Mon, Jan 25, 2016 at 12:59 PM Ronny Pfannschmidt < [email protected]> wrote: > i have ideas for replacing/changing it in the back of my head since a > while now, > so i'd like to have a reasonable/easy testbed > > also we could avoid the need for api compatibility even if we copy

Re: [pytest-dev] a potential alternative to the py.code merge

given the circumstances it might be best to go with 2 after all Am 25.01.2016 um 16:41 schrieb Bruno Oliveira: > > > On Mon, Jan 25, 2016 at 12:59 PM Ronny Pfannschmidt > > wrote: > > i have ideas for replacing/changing it in the back of my head since a

[pytest-dev] Introduction

Hi everyone! My name is Isaul Vargas and I work as a software tester. I have been using py.test since 2013 and I really like the fixture interface of Py.test it's a powerful abstraction! One of the libraries I use to test software is Selenium (and Appium for mobile devices), and one indispensable

Re: [pytest-dev] Introduction

Hi Isaul! On Mon, Jan 25, 2016 at 5:42 PM Isaul Vargas wrote: > Hi everyone! My name is Isaul Vargas and I work as a software tester. > I have been using py.test since 2013 and I really like the fixture > interface of > Py.test it's a powerful abstraction! > ... > So, I've decided to volunteer m

Re: [pytest-dev] pytest docs on readthedocs?

Hi On Mon, Jan 25, 2016 at 12:39 PM Bruno Oliveira wrote: > I will study how to use this later Today. > Well, registering a CNAME from http://docs.pytest.org to http://pytest.readthedocs.org is beyond my almost non-existent server-configuration-fu skills. :) Could somebody with more experience