Re: [pytest-dev] pytest documentation

[Brianna Laugher]

I'm still in favour, and it sounds like a smart way to avoid the problems
of a long-lived branch.

On Wed, 3 Mar 2021 at 07:57, Daniele Procida  wrote:

> Bruno Oliveira wrote:
>
> >I definitely think it would be a good idea, but I'm interested to hear
> >what the other maintainers think as well.
>
> I haven't heard any other replies - I would be glad to know what others
> think, to be sure that this will be a good way forward and of benefit to
> pytest (or not!).
>
> Thanks,
>
> Daniele
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Manually running test steps/getting user input

[Brianna Laugher]

I work in an environment where there is a lot of manual text execution
(blame hardware).

Moving people to ATDD/BDD style tests (such as Gherkin) is a first step.
The good thing about tests written in this style is it works for both
automated and manual execution.

We are looking at adopting such a framework to start with some system level
testing for embedded software. Robot Framework is well known and solid in
this space. One of my colleagues pointed out that RF even has a capability
to prompt the user for input or to record a step as pass/fail.
https://robotframework.org/robotframework/latest/libraries/Dialogs.html
(I've just tried it out and it is an extremely basic Tk dialog that pops up
from the command line on Windows, but it is kinda nifty.) I am loath to
discover that RF has a feature pytest does not...

This is kind of a neat tool to have on a path towards automation. Of course
the steps run all the time need to be automated, but there are plenty of
others that could stay manual, being able to do this is an interesting
hybrid. (Obviously these are not the kind of tests you run in CI!)

So has anyone heard of a plugin like that for pytest?

The RF code looks like it might not take that much porting, tbh...
https://github.com/robotframework/robotframework/blob/master/src/robot/libraries/Dialogs.py

Any thoughts about this as an idea, somewhere between awesome and cursed? :)

cheers
Brianna

-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Resolution of recent conflict

[Brianna Laugher]

Many of you know that there has recently been some conflict within the
pytest core maintainer group. Thanks all for your patience while
discussions took place in the background. In the end, we as active
maintainers agreed to exclude Daniel from pytest project membership for at
least six months, because of interactions which we deemed innappropriate
and harmful to the project. After six months we will be ready to talk again.

Daniel has been a prolific and significant contributor to pytest, and we
recognise and deeply appreciate the time he has devoted to the project, and
thank him for his efforts.

We thank everyone for allowing some time and space to the resolve the
situation, in particular to Holger who discussed with Daniel and everybody
else in the background. We ask that you resist the temptation to create a
hero/villain narrative, because it is both not correct and not helpful.
This is also the reason we don't cite his full name as we don't want to put
public blame or burn bridges that we'd like to remain walkable in the
future.

Thanks,
Anthony, Brianna, Bruno, Florian, Floris, Ran, Ronny.
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Code of conduct issues

[Brianna Laugher]

Hi all,

As one of the Code of Conduct (CoC) committee members (
https://github.com/pytest-dev/pytest/blob/master/CODE_OF_CONDUCT.md ) I
want to apologise for the poor handling of issues that have led Bruno,
Anthony and Ronny to step back from the project. As a group we failed to
act decisively and now people who have contributed so much to pytest are
suffering, and for that I am sorry.

I intend to reach out to the PSF Conduct Working Group and ask them to
advise us on a way forward.

thanks,
Brianna
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Strike for the climate on 20th (Friday)

[Brianna Laugher]

I reckon go for it! Can we put a banner on the Github repo somehow?

See you in the streets 

Brianna

On Wed, 18 Sep 2019 at 19:57, Bruno Oliveira  wrote:

> Hi everyone,
>
> pytest, devpi and tox want to join the Digital Climate Strike which will
> happen next Friday:
>
> https://digital.globalclimatestrike.net/
>
> The idea is to 1) not have the support team available on that day, as well
> as perhaps 2) including a widget to the docs advertising the event, such as
> this one:
>
> https://assets.digitalclimatestrike.net/demo.html?fullPage
>
>
> (Note that it can be closed and still provide access to the docs).
>
> I think there will be almost no disruption, as sometimes issues sit around
> for a day before getting an answer and the widget over the docs can be
> dismissed with a single click.
>
> Opinions?
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] [core] Tidelift Funding

[Brianna Laugher]

Hi,

It looks like there are a few more repos that could be claimed as well:

https://tidelift.com/lifter/search/pypi/pytest-xdist
https://tidelift.com/lifter/search/pypi/pytest-cov
https://tidelift.com/lifter/search/pypi/pluggy
https://tidelift.com/lifter/search/pypi/py

etc.

cheers
Brianna


On Fri, 10 May 2019 at 08:20, Bruno Oliveira  wrote:

> Hi everyone,
>
> I've registered pytest with Tidelift, so it is now officially part of the
> platform:  https://tidelift.com/subscription/pkg/pypi-pytest
>
> I've opened a PR documenting what we've discussed here:
>
> https://github.com/pytest-dev/pytest/pull/5240
>
> Any suggestions are very welcome!
>
> Cheers,
>
> On Wed, May 8, 2019 at 8:05 AM Bruno Oliveira 
> wrote:
>
>> Hey Daniel,
>>
>> On Wed, May 8, 2019 at 5:57 AM Daniel Hahler 
>> wrote:
>>
>>>
>>> I think a new repository like pytest-meta, or pytest-org makes sense -
>>> it is
>>> easy to setup in general, and keeps away noise from the main repo.
>>>
>>> We could create some issue in the main repo to link to it for
>>> transparency.
>>>
>>> But maybe just having an issue for it in the (main) repo is enough
>>> already:
>>>  you get notifications, it can be edited etc.
>>>
>>
>> I think the plan for now is to just have a TIDELIFT.rst (wink Floris) on
>> the main repository with instructions, and the maintainers interested in
>> receiving funds. To update the document we use standard PRs. I believe this
>> will fit for now, but if we find it lacking we can easily move to a
>> separate repository for sure.
>>
>> About automation, they have a simple API for posting new CHANGELOGs:
>> https://tidelift.com/docs/api, so that can be definitely automated.
>>
>> Cheers,
>> Bruno.
>>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Hacktober coming up

[Brianna Laugher]

Hi,

I was reminded today that github's month long event encouraging people to
submit PRs to open source projects will begin once again in a week or so. I
am not sure how much increased activity was notice last year, but perhaps
it would be prudent to do a bit of extra issue grooming if we can.
Especially labeling beginner friendly/easy issues.

Cheers
Brianna
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Fwd: [CodeTriage] Help triage pytest-dev/pytest

[Brianna Laugher]

On the topic of issue triage, this is a service we could promote people to
use. But I guess it's a question if the problem is more rate of new issues
or old issues never getting closed.

Brianna


-- Forwarded message -
From: CodeTriage 
Date: Sun, 9 Sep 2018 at 16:38
Subject: [CodeTriage] Help triage pytest-dev/pytest
To: 


Hello pfctdayelise,
Repo added to CodeTriage!

Thank you for adding pytest-dev/pytest to CodeTriage. If you want to get
more people helping out with this repo, we suggest adding a badge to the
repo’s readme. Here is the markdown:

[![Open Source Helpers
badge](https://codetriage.com/pytest-dev/pytest/badges/users.svg)](https://codetriage.com/pytest-dev/pytest)

You can view an the badge on the CodeTriage page for pytest

.

If pytest has a “contributing section” or docs on helping such as
contributing.md, it helps to put a sentence or two encouraging people to
subscribe to your repo:

You can triage issues which may include reproducing bug reports
or asking for vital information, such as version numbers or
reproduction instructions. If you would like to start triaging
issues, one easy way to get started is to [subscribe to pytest on
CodeTriage](https://codetriage.com/pytest-dev/pytest).

The more people you have subscribed to this repo on CodeTriage, the more
help it will get on this project. The more ’s the better.
--
You subscribed to pytest on CodeTriage!

You signed up to help triage GitHub issues on pytest-dev/pytest
.
That’s pretty awesome.

What’s next? You’ll get issues sent to your inbox periodically like this
one:

*pytest-dev/pytest#2449* warnings: support for logging.captureWarnings


The rate at which we send emails backs off automatically when you get busy.
You can also set you prefered email rate in your user settings.

What do you do with an issue when it gets in your inbox? Try to triage it.
How To Triage?

First, carefully read over the issue, title, and description, if there are
any comments read over all the comments, carefully. If a member of this
repo is engaging actively there is no need to do anything, leaving a
comment in the issue would just add to the clutter.

If the issue hasn’t been updated in awhile, or if no one has commented
consider the issue, if it is a bug try to reproduce it. If it is a pull
request consider what an alternate implementation might look like. If there
is something you don’t understand about the issue and feel others will have
that same question please leave your question in the comments. Be as
descriptive as possible. Comments like “I don’t understand this” are not
helpful and counter productive. A better comment might be “Can you help me
understand a use case for this?”.

If you can reproduce the issue or you believe it is a good pull request,
add a comment and say why you think that is. Try to stay positive while
triaging issues, ask questions before you downvote something. If you do
decide to  or  on an issue, leave a comment as to why you feel that
way. Issues are for social coding, if you help someone make better issues,
you’re helping the community.

If the issue goes stale, leave a comment asking if it is still a problem.
If you get no response for a number of days, you can leave another comment
suggesting to the repo owner that they should close the issue.

Read more about Fixing Open Source Issues via Triage

.
Goals of Triage

   - Help share the 

Re: [pytest-dev] Hacktoberfest - Beginner Issues

[Brianna Laugher]

Some projects have a bug triaging guide, eg
http://docs.hood.ie/en/latest/developers/TRIAGING.html . Writing up the
existing process (eg intention of existing labels) may help more people
carry out bug triage.

On Sun, 9 Sep 2018 at 16:43, Brianna Laugher 
wrote:

> I have seen a lot of projects use something like
> https://github.com/apps/stale to auto-close issues after a certain amount
> of time has passed without activity.
>
> On Fri, 7 Sep 2018 at 04:21, Bruno Oliveira  wrote:
>
>>
>> On Thu, Sep 6, 2018 at 2:26 PM Maik Figura  wrote:
>>
>>> Hey everyone,
>>>
>>> I noticed that the issue tracker almost hit 500 issues. Would it be good
>>> to discuss how to handle issues in general (follow ups, etc) and on how
>>> to maybe reduce the amount of outdated issues (I am not even sure there
>>> are outdated ones...). Do we maybe have examples how other projects do
>>> this? Or maybe this was already discussed and I just missed it?
>>>
>>>
>> Hi Maik,
>>
>> (I'm adressing the contents of the email, not the title :))
>>
>> The number of open issues is something that bugs me. One of the reasons
>> that labels like "question" and "needs information" were created was that
>> we could periodically go over issues marked with them and close if they
>> have been inactive after some time, but this is something that has to be
>> done regularly.
>>
>> I would love to know how other projects which also face a large number of
>> issues deal with this.
>>
>> Cheers,
>> Bruno.
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Hacktoberfest - Beginner Issues

[Brianna Laugher]

I have seen a lot of projects use something like
https://github.com/apps/stale to auto-close issues after a certain amount
of time has passed without activity.

On Fri, 7 Sep 2018 at 04:21, Bruno Oliveira  wrote:

>
> On Thu, Sep 6, 2018 at 2:26 PM Maik Figura  wrote:
>
>> Hey everyone,
>>
>> I noticed that the issue tracker almost hit 500 issues. Would it be good
>> to discuss how to handle issues in general (follow ups, etc) and on how
>> to maybe reduce the amount of outdated issues (I am not even sure there
>> are outdated ones...). Do we maybe have examples how other projects do
>> this? Or maybe this was already discussed and I just missed it?
>>
>>
> Hi Maik,
>
> (I'm adressing the contents of the email, not the title :))
>
> The number of open issues is something that bugs me. One of the reasons
> that labels like "question" and "needs information" were created was that
> we could periodically go over issues marked with them and close if they
> have been inactive after some time, but this is something that has to be
> done regularly.
>
> I would love to know how other projects which also face a large number of
> issues deal with this.
>
> Cheers,
> Bruno.
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Documentation proposal

[Brianna Laugher]

Yes thanks Daniele!

Daniele gave a great talk at PyCon Australia this past weekend about these
four different types of documentation and how they are different/similar:
https://www.youtube.com/watch?v=t4vKPhjcMZg=PLs4CJRBY5F1KsK4AbFaPsUT8X8iXc7X84=65

Daniele referred to "Brianna's tutorial", which is the materials for a 3
hour tutorial that I gave at the conference. It doesn't have video, but the
materials are here:

https://www.dropbox.com/sh/jx44jys7g6v5gy8/AAB49nqGd4_FXUqq6SjN4V6wa?dl=0

The concept of the tutorial was to use a "starter" application and test
suite and build on/modify that. The application is
https://github.com/pfctdayelise/allseasons

I have a lot of notes and feedback from giving the tutorial itself to feed
back to the pytest community (mainly around using pytest-bdd/splinter/Xvfb
on Windows and OSX), but I am still in recovery mode from the conference
itself so it will take me a little longer to write that up.

cheers
Brianna


On 8 August 2017 at 02:07, Bruno Oliveira  wrote:

> Hi Daniele,
>
> Thanks a lot for following up on this!
>
> I've pushed your branch up to pytest's repository and enabled building it
> on RTD so people can more easily take a look at it:
>
> https://docs.pytest.org/en/documentation-restructure/
>
> I did a quick glance and I like what I see so far. Having separate
> tutorial/how-to guides/reference documents seems like a great improvement
> because a common complain regarding pytest's docs was the fact that there
> was no clear distinction between those different types of documentation.
>
> From my part I'm +1 on continue to work on this. :)
>
> Cheers,
> Bruno.
>
>
> On Mon, Aug 7, 2017 at 2:50 AM Daniele Procida  wrote:
>
>> On Sat, Jul 15, 2017, Daniele Procida  wrote:
>>
>> >I propose to restructure the pytest docmentation, according to this
>> >scheme  (the rationale for the
>> >scheme is described at length in that article).
>>
>> Hi.
>>
>> I have made a start on this since I first mentioned it at EuroPython.
>>
>> You can see the work so far at > dev/pytest/compare/master...evildmp:documentation-restructure?expand=1>
>>
>> To try it out locally:
>>
>> Clone my branch and get into the right directory:
>>
>> git clone -b documentation-restructure g...@github.com:evildmp/pytest.
>> git
>> cd pytest/doc/en
>>
>> Set up the virtualenv for the docs:
>>
>> make install
>>
>> Start the documentation server:
>>
>> make run
>>
>> Checkout the new documentation at .
>>
>> Please note that there remains a lot more to do, but there is enough so
>> far to get an idea of:
>>
>> * how it will be structured
>> * what it will like
>>
>> I have many questions, which are in issues on my fork: <
>> https://github.com/evildmp/pytest/issues/>.
>>
>> Because commits land so fast in master (over 200 since I started working
>> on this less than a month ago) it would be good to get some feedback on
>> this and know whether this approach is going to be accepted into pytest. If
>> so, I will be able to continue, with two main tasks:
>>
>> * build Brianna's tutorial into the documentation
>> * work through every single page and ensure that all content is correctly
>> placed in the appropriate section.
>>
>> Thanks,
>>
>> Daniele
>>
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Dependency CI

[Brianna Laugher]

Hi,

This is a new service thing that is free for open source projects.
https://dependencyci.com/

Is it worth investigating for pytest and plugins?

cheers,
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Postpone 3.0?

[Brianna Laugher]

It's mainly Floris, Oliver and me that are the hold up right? Removing
reinterpret assert and 2x docs.
I hope to work on the docs restructure this weekend and at a minimum make
it clear what tasks are left so it's easier for other people to help.

Brianna

On 15/07/2016 6:21 AM, "Bruno Oliveira"  wrote:

> Hi pytesters,
>
> Our original target date for pytest 3.0 was around this week (just before
> EuroPython), but it seems we are not going to make it as there are some
> issues still in the 3.0 check list which have not been merged:
>
> https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist
>
> My question is if we should delay the release a little bit and give more
> time to people to work on them for 3.0, or bite the bullet and make the
> release anyway this weekend/early next week? And if we decide to delay,
> what people think would be a good time for a new target date?
>
> Personally I would rather wait a little more because I consider the
> remaining issues important to go in 3.0.
>
> Btw, I was taking a look at the Pulse page on GitHub (
> https://github.com/pytest-dev/pytest/pulse
> ) and in the last 7
> days we have merged 16 PRs. That's awesome. :)
>
> Cheers,
> Bruno.
>
>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] sprint logistics / food

[Brianna Laugher]

Yes I am leaving Australia Saturday and would like to know soon that I have
a bed somewhere. :) I'm not travelling directly to the sprints so I have
some flexibility on when I arrive, but basically plan to arrive on the 19th.

thanks! exciting!! :D
Brianna

On 7 June 2016 at 20:57, holger krekel  wrote:

> Hey pytest/tox sprinters,
>
> wrt to our current wiki planning here:
>
> https://github.com/pytest-dev/pytest/wiki/sprint2016
>
> i'd like all attendees to check once again preferably until thursday:
>
> - i added a food column, could you all until thursday this week fill in
>   the column e.g. with "ALL", "no-meat", "vegetarian", "vegan"?
>   If your column is not changed till thursday i am going to assume
> "vegetarian".
>   This is important because i am going to tell the Haus-am-Schoenberg,
> where
>   the sprint is, for their lunch cooking (we get lunch every day, maybe not
>   on wednesday).
>
> - Then, as to accomodation i'd like to get a clear picture what exactly
>   is still needed.  Please check your accomodation column.  I assume
>   that where people have "private" that it's settled.  And where it's
>   shared/wanted that it's still open -- that would be 7-8 people
>   (depending on Andreas).  At least Ana/Brianna and Florian can stay
>   around my place as things stand.  So we'd need a second flat for 4-5
>   persons IISIC.
>
> - three people (ronny, Danielle, NN/Splunk) have not updated their
>   travel details yet -- could you do so?
>
> If anyone has any other questions, please post them here.
>
> cheers,
> holger
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] planet pytest

[Brianna Laugher]

Nice! Could someone add a link to the github repo/instructions about how to
add a new feed, and maybe also an explicit link to the planet rss feed?

Cheers
Brianna
On 12/04/2016 7:00 AM, "Bruno Oliveira"  wrote:

> Nice, subscribed! :)
>
> On Mon, Apr 11, 2016 at 5:51 PM Raphael Pierzina 
> wrote:
>
>> Now pytest-tricks does have a feed
>> https://github.com/fschulze/planet.pytest.org/pull/4 :D
>>
>> On 11 Apr 2016, at 17:25, Florian Schulze 
>> wrote:
>>
>>
>>
>> On 11 Apr 2016, at 13:37, Florian Bruhin wrote:
>>
>> I'll check if I find some other interesting blogs with pytest content
>> :)
>>
>> Some which come to mind:
>>
>> http://hackebrot.github.io/pytest-tricks/
>>
>>
>> This doesn't seem to have a feed.
>>
>> http://pythontesting.net/category/framework/pytest/
>>
>>
>> Add it like this:
>>
>> [http://pythontesting.net/category/framework/pytest/feed/]
>> title = Python Testing
>> link = http://pythontesting.net/category/framework/pytest/
>>
>> http://blog.devork.be/ if it had a pytest tag (hint, hint)
>>
>>
>> It has labels, but there doesn't seem to be a feed for labels.
>>
>> https://blog.dbrgn.ch/tags/pytest/
>>
>>
>> PR for that merged.
>>
>>
>> I switched from genshi to the default planet template thingy and that
>> seems to got rid of the rendering issues.
>>
>> Regards,
>> Florian Schulze
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Sprint participants writing a blog post?

[Brianna Laugher]

Just sent out an update with a link to your post Andreas, thanks!

Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
posts? :P

cheers
Brianna


On 16 February 2016 at 22:24, Brianna Laugher <brianna.laug...@gmail.com>
wrote:

> That's a great post, I look forward to that pytest blog too ;)
>
> I suggest we wait a few days to post another IGG update, they recommend to
> do updates at least every 5 days, but it's nice if the total donated gets a
> bit bigger between each update :)
>
> Brianna
>
> On 16 February 2016 at 08:43, Andreas Pelme <andr...@pelme.se> wrote:
>
>>
>> > On 13 feb. 2016, at 05:06, Brianna Laugher <brianna.laug...@gmail.com>
>> wrote:
>> >
>> > Andreas, how about you? You could speak about your company's support
>> too :)
>>
>> I’ve put together a post at
>>
>> http://andreas.pelme.se/pytest-sprint.html
>>
>> I don’t really have a draft mode on my blog, but I’m quite sure it does
>> not receive any traffic anyways. Feedback on the post is very welcome :)
>>
>> Cheers,
>> Andreas
>>
>>
>
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
>



-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Sprint participants writing a blog post?

[Brianna Laugher]

Your writing is great Bruno! If you wanted I would be happy to edit a draft
though.

Andreas, how about you? You could speak about your company's support too :)

Brianna

On 12 February 2016 at 09:02, Holger Krekel <hol...@merlinux.eu> wrote:

> Your written English is pretty good so you feel youbare rather missing
> practice in pronunciation? But when we did the hangout I wasn't aware of it
> :)
>
>
>
> On February 11, 2016 10:01:52 PM GMT+01:00, Bruno Oliveira <
> nicodde...@gmail.com> wrote:
>>
>> Hi Holger,
>>
>> TBH I'm a little shy of my english speaking skills, so I rather don't do
>> the interview. :S
>>
>> Someone else might be more suited!
>>
>>
>> On Thu, Feb 11, 2016 at 7:10 AM holger krekel <hol...@merlinux.eu> wrote:
>>
>>>
>>> Hey Bruno,
>>>
>>> what about you?  You have been incredibly active and it'd be cool to see
>>> you interviewed :)  I think apart from the campaign it'd be interesting
>>> to talk about pytest-3.0 and xdist improvements that we are looking into
>>> ...
>>>
>>> best,
>>> holger
>>>
>>>
>>> On Wed, Feb 10, 2016 at 20:14 +, Dave Hunt wrote:
>>> > We have an invitation to be discuss/promote the sprint on the Python
>>> Test Podcast if anyone wants to volunteer!
>>> > https://twitter.com/brianokken/status/697419561797160960 <
>>> https://twitter.com/brianokken/status/697419561797160960>
>>> >
>>> > Cheers,
>>> > Dave
>>> >
>>> > > On 9 Feb 2016, at 17:16, Dave Hunt <dh...@mozilla.com> wrote:
>>> > >
>>> > > Published:
>>> > > http://blargon7.com/2016/02/python-testing-sprint-2016/ <
>>> http://blargon7.com/2016/02/python-testing-sprint-2016/>
>>> > >
>>> > > Dave
>>> > >
>>> > >> On 9 Feb 2016, at 14:09, holger krekel <hol...@merlinux.eu >> hol...@merlinux.eu>> wrote:
>>> > >>
>>> > >> On Tue, Feb 09, 2016 at 14:07 +, Dave Hunt wrote:
>>> > >>> I have a public preview of my blog post. Feedback welcome:
>>> > >>> http://blargon7.com/?p=204=1&_ppp=65d7c71c07 <
>>> http://blargon7.com/?p=204=1&_ppp=65d7c71c07> <
>>> http://blargon7.com/?p=204=1&_ppp=65d7c71c07 <
>>> http://blargon7.com/?p=204=1&_ppp=65d7c71c07>>
>>> > >>
>>> > >> reads good!
>>> > >>
>>> > >> holger
>>> > >>
>>> > >>> Dave
>>> > >>>
>>> > >>>> On 9 Feb 2016, at 10:40, Dave Hunt <dh...@mozilla.com >> dh...@mozilla.com>> wrote:
>>> > >>>>
>>> > >>>> I think this is a great idea! I have had approval to join you all
>>> during the sprint, so I’d be happy to write a blog post about how I came to
>>> pytest and what I’d like to work on during the week.
>>> > >>>>
>>> > >>>> Cheers,
>>> > >>>> Dave
>>> > >>>>
>>> > >>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <
>>> brianna.laug...@gmail.com <mailto:brianna.laug...@gmail.com> >> brianna.laug...@gmail.com <mailto:brianna.laug...@gmail.com>>> wrote:
>>> > >>>>>
>>> > >>>>> Heh, I had the exact same idea last night :)
>>> > >>>>>
>>> > >>>>> I was thinking
>>> > >>>>> 1) how did you get involved with pytest?
>>> > >>>>> 2) What is your favourite feature/plugin of pytest that is
>>> relatively unknown?
>>> > >>>>> 3) What are you planning to work on during the sprint?
>>> > >>>>>
>>> > >>>>> Cheers
>>> > >>>>> Brianna
>>> > >>>>>
>>> > >>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <hol...@merlinux.eu
>>> <mailto:hol...@merlinux.eu> <mailto:hol...@merlinux.eu >> hol...@merlinux.eu>>> wrote:
>>> > >>>>> What about if each of us who wants to participate writes a small
>>> blog (lacking a blog a pytest-dev) post of where he/she comes from, past
>>> core or plugin work for example, and main areas of interest for the sprint?
>>> > >>

[pytest-dev] Twitter update

[Brianna Laugher]

Hi,

I added Holger @hpk42 and Raphael @hackebrot to the pytestdotorg twitter
account so they can tweet from it (via tweetdeck.twitter.com). If anyone
else feels like they might be inspired to tweet on behalf of pytest, let me
know offlist.

cheers
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] RFC: pytest sprint indiegogo page (draft)

[Brianna Laugher]

I think a dedicated page on the pytest site is a good idea (as well as a
banner), then when it is over we can put the supporters names there (if
they wish).

55 days is a long time, maybe a 30 day campaign is better?

I would suggest to include even more context about what pytest is, maybe
some numbers like pypi downloads, founded in 200x.

Cheers
Brianna
On 04/02/2016 3:23 AM, "holger krekel"  wrote:

> Hey all,
>
> i adapted the indiegogo draft page below according to suggestions here.
> I didn't include yet Brianna's idea on allowing "voting", see my comment
> to her mail.
>
> Feel free to edit or comment here further.  I'd like to publish tomorrow
> european evening and i think pytestorg/Brianna should tweet then and we
> retweet or so.
>
> Also i think we should put a banner on all pytest.org pages, what do you
> think?  Anything else?
>
> best,
> holger
>
>
> On Wed, Feb 03, 2016 at 10:00 +, holger krekel wrote:
> > Hey all,
> >
> > i've done a indiegogo sprint page which is still in draft mode, see here:
> >
> > https://www.indiegogo.com/project/preview/ee72990c#/
> >
> > I also invited Bruno, Brianna, Floris and Florian as editors.
> > If other wants to help edit, or comment on the setup, please send
> > a mail here.  I am particular unsure about the "perks" ...
> >
> > I'd like to get it online tomorrow or latest friday if possible.
> >
> > cheers,
> > holger
> >
> > --
> > about me:http://holgerkrekel.net/about-me/
> > contracting: http://merlinux.eu
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>
> --
> about me:http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] TLS certificate expired

[Brianna Laugher]

Hi,

It was pointed out on Twitter that our tls certificate has expired.

Cheers
Brianna
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest sprint 2016 / getting started

[Brianna Laugher]

That's fine with me Raphael. BTW if anyone else would like to tweet for
pytest, just contact me offlist to arrange :)

I summarised the discussion etc so far here:
https://github.com/pytest-dev/pytest/wiki/2016-dev-sprint

and put some ideas I had about crowdfunding 'rewards'. I think more or less
any github user can edit the wiki, so please do if you want to add
something.

cheers
Brianna


On 19 January 2016 at 09:12, Raphael Pierzina  wrote:

> Hi friends,
>
> there’s been a blog post on FOSS funding recently, which received quite a
> bit of attention on HackerNews/Twitter and alike:
>
> https://medium.com/@nayafia/how-i-stumbled-upon-the-internet-s-biggest-blind-spot-b9aa23618c58#.kf5a41ubn
>
> The author Nadia Eghbal (@nayafia) now started a doc on projects that
> require support.
> https://twitter.com/nayafia/status/689174577302253568
>
> I added pytest to the list and who knows, maybe it will help us fund the
> dev sprint.
>
> @Brianna: I put in the orgs twitter handle to get in touch. Please feel
> free to update this to what you feel suits best.
>
> Cheers
> Raphael
>
> On 07 Jan 2016, at 10:40, holger krekel  wrote:
>
> Hey all,
>
> let's try to find out if we can make a pytest sprint happen in 2016.
> Here are some suggestions/thoughts on key points.
>
> Participants: anyway who has contributed to pytest in recent years but also
> interested newcomers/wanna-be-contributors.  Contributors are eligible
> for getting their travel costs reimbursed (see funding below).
>
> Location: somewhere around Freiburg, black forest, Germany.
>
> Date ranges:
>
>20-26th June or
>
>30th June - 6th July.
>
> Travel: arrive on the first day, leave the last.
>
> Funding: we'll do a Indiegogo or betterplace.org campaign and ask
> companies and individuals to help come up with funding for travel
> costs, lodging and food for participants.  If participants can come
> on their company's time and money even better.  In fact, the gathering
> will be a great opportunity to dive deeper into pytest and make the best
> use of it for your company.
>
> sprint contents: pytest-3.0 and a major new revision of the xdist plugin?
> Cleaning up wards, introducing new features (to be continued ...).
>
> deadline for funding compaign: maybe February/March
> so everybody can start booking.
>
> Who'd be up for it?  how much do you estimate you need for travel?
> Would the date range fit?
>
> best,
> holger
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] tentative pytest sprint june 2016 / funding

[Brianna Laugher]

I guess more people might be able to commit to participating when event
details are locked down. Bit of a catch 22 for organising.

I don't have a preference on platform (I think kickstarter is best if
making a lot of money/getting a lot of backers is the most important thing,
which it's probably not here), but I strongly recommend not doing it
yourself. :)

http://funding.openinitiative.com/ is specifically for open source projects
though.

PSF will probably contribute a bit too https://www.python.org/psf/grants/

cheers
Brianna


On 13 January 2016 at 08:54, holger krekel  wrote:

> Hey Florian, Bruno, Brianna, Floris, Omar, all,
>
> great to hear that 20-26th June could work for you all!
> Ronny is missing though and i haven't heart from Anatoly
> for a longer time.
>
> I slightly prefer the june date to attaching the sprint to
> EuroPython2016 which i am not sure i'll make.  As i am bound to be on
> travels (currently in San Francisco) quite a bit this year i'd prefer
> hosting the sprint in Freiburg to not add yet another longer duration
> where i am completely away from family.
>
> So now that we have a tentative plan i think it's time to go for the
> funding campaign!  If no one beats me to it i can see to draft a text
> end january.  I guess we can ask for EUR 4000 to be on the safe side as
> it stands.  my company could handle the accounting or we appoint someone
> else who does it (i am  not eager so please step foward if you like --
> the overhead with my accountant is probably 10% :)
>
> Anyone prefering a particular platform like indiegogo or betterplace or
> so?  I don't have much experience with those platforms myself.  If we
> aim at getting primarily companies to fund it we could even go without
> those platforms and just setup a campain page on pytest.org and provide
> a contact mail.  A company funding it is also invited to send their
> developer(s) to participate, learn and contribute for mutual benefit?!
> :)
>
> best,
> holger
>
>
> On Thu, Jan 07, 2016 at 10:40 +, holger krekel wrote:
> > Hey all,
> >
> > let's try to find out if we can make a pytest sprint happen in 2016.
> > Here are some suggestions/thoughts on key points.
> >
> > Participants: anyway who has contributed to pytest in recent years but
> also
> > interested newcomers/wanna-be-contributors.  Contributors are eligible
> > for getting their travel costs reimbursed (see funding below).
> >
> > Location: somewhere around Freiburg, black forest, Germany.
> >
> > Date ranges:
> >
> > 20-26th June or
> >
> > 30th June - 6th July.
> >
> > Travel: arrive on the first day, leave the last.
> >
> > Funding: we'll do a Indiegogo or betterplace.org campaign and ask
> > companies and individuals to help come up with funding for travel
> > costs, lodging and food for participants.  If participants can come
> > on their company's time and money even better.  In fact, the gathering
> > will be a great opportunity to dive deeper into pytest and make the best
> > use of it for your company.
> >
> > sprint contents: pytest-3.0 and a major new revision of the xdist plugin?
> > Cleaning up wards, introducing new features (to be continued ...).
> >
> > deadline for funding compaign: maybe February/March
> > so everybody can start booking.
> >
> > Who'd be up for it?  how much do you estimate you need for travel?
> > Would the date range fit?
> >
> > best,
> > holger
> > ___
> > pytest-dev mailing list
> > pytest-dev@python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>
> --
> about me:http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>



-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest sprint 2016 / getting started

[Brianna Laugher]

I spoke to them and they seem positive about working something out, so I'm
tentatively in :DDD

On 8 January 2016 at 23:52, Brianna Laugher <brianna.laug...@gmail.com>
wrote:

> The dates are fine for me and I would love to come, but a bigger question
> is if I can justify flying to Europe from Australia for such a short trip.
> I am starting a new job in February and should have enough leave for that,
> but not much more. I guess I will raise it with my future bosses and see
> what they say.
>

-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest sprint 2016 / getting started

[Brianna Laugher]

Bruno I see your 700€ and raise you 1000€... ;)

The dates are fine for me and I would love to come, but a bigger question
is if I can justify flying to Europe from Australia for such a short trip.
I am starting a new job in February and should have enough leave for that,
but not much more. I guess I will raise it with my future bosses and see
what they say.

It's very tempting though, as I really enjoyed time with pytesters at PyCon
US and Europython :)

A couple of considerations -

- is it worth aligning with a conference such as Europython (immediately
before/after)? Maybe Europython sprints + 2 extra days is easier than 5
days just for pytest. Or maybe not, I'm not sure.

- what's the optimal number of participants? I imagine something like 5-15.

Cheers
Brianna
On 07/01/2016 9:40 PM, "holger krekel"  wrote:

> Hey all,
>
> let's try to find out if we can make a pytest sprint happen in 2016.
> Here are some suggestions/thoughts on key points.
>
> Participants: anyway who has contributed to pytest in recent years but also
> interested newcomers/wanna-be-contributors.  Contributors are eligible
> for getting their travel costs reimbursed (see funding below).
>
> Location: somewhere around Freiburg, black forest, Germany.
>
> Date ranges:
>
> 20-26th June or
>
> 30th June - 6th July.
>
> Travel: arrive on the first day, leave the last.
>
> Funding: we'll do a Indiegogo or betterplace.org campaign and ask
> companies and individuals to help come up with funding for travel
> costs, lodging and food for participants.  If participants can come
> on their company's time and money even better.  In fact, the gathering
> will be a great opportunity to dive deeper into pytest and make the best
> use of it for your company.
>
> sprint contents: pytest-3.0 and a major new revision of the xdist plugin?
> Cleaning up wards, introducing new features (to be continued ...).
>
> deadline for funding compaign: maybe February/March
> so everybody can start booking.
>
> Who'd be up for it?  how much do you estimate you need for travel?
> Would the date range fit?
>
> best,
> holger
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Paid contract desired/bountysource label on gh ?

[Brianna Laugher]

I have never seen bounty stuff work well in open source TBH.

Perhaps the website needs to be a bit more pointed in showing that there
are consultants (such as Holger, but surely others too) available to work
on pytest for a fee.

IMO pytest is well into the size and popularity that it would benefit from
a fulltime paid staff or 1 or more. We have quite an active volunteer
community which is great! but it's difficult for volunteers to resolve
problems that require major refactors.

cheers
Brianna

On 2 January 2016 at 04:28, Bruno Oliveira  wrote:

> I think it is a good idea to have bounty labels... having an official
> channel for people to explicitly offer bounties would be nice.
>
> On Fri, Jan 1, 2016 at 3:20 PM Ronny Pfannschmidt <
> opensou...@ronnypfannschmidt.de> wrote:
>
>> Hi all,
>>
>> While grooming I stumbled upon issues where Holger rightfully noted that
>> he wouldn't tackle them in free time
>>
>> I wonder if it would be a good idea to create contract work and/or bounty
>> labels
>> And experiment with the effect.
>>
>> -- Ronny
>> --
>> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
>> gesendet.___
>> pytest-dev mailing list
>> pytest-dev@python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Europython sprints

[Brianna Laugher]

Hi!

I thought we could try and be a bit organised for the sprints, in terms of
planning things to work on and who will be there and so on. So I made a
wiki page:

https://github.com/pytest-dev/pytest/wiki/Europython-2015-sprints

Please add yourself if you'll be there, or add a task (or reply here) if
you think of something sprint-sized. Could be docs etc.

For example, I would quite like to use labels in github issues to group
related bugs, eg those related to parametrize.

cheers
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] adopt pytest month is over!

[Brianna Laugher]

Hi all,

So adopt pytest month is officially over! I am working on surveys for
the helpers and projects and will send them out this week. I hope
everyone enjoyed it and maybe even learned something.

One thing, the helpers for Nefertari (REST API framework built on
Pyramid and ElasticSearch) are a bit stuck and could do with some more
experienced eyes, specifically about how to approach testing a
framework. Although the month is over Nefertari don't have much to
show for it yet and it would be nice to see if we can help them get
going with the basics. Would anyone be willing to help there?

cheers,
Brianna

-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Let's have an Adopt pytest month

[Brianna Laugher]

Hello all!

We finally have a web page for adopt pytest month:
http://pytest.org/latest/adopt.html

If you would like to be a helper, please fill out this short form,
preferably in the next week or so: http://goo.gl/forms/nxqAhqWt1P

I will use the information to try and pair helpers with appropriate
projects according to their needs.

And if you have some projects in mind that you'd like to gently nudge
towards pytest, I think now is the time to spread the word :)

cheers
Brianna


On 12 February 2015 at 22:06, Raphael Pierzina raph...@hackebrot.de wrote:

 I'm in :) This is a great idea.

 Back in November I converted a bunch of tests for Cookiecutter. Most PR's
 are still pending though.
 https://github.com/audreyr/cookiecutter/pulls/hackebrot

 I did not contribute to PyTest thus far.

 Raphael

 ___
 pytest-dev mailing list
 pytest-dev@python.org
 https://mail.python.org/mailman/listinfo/pytest-dev




-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Setting up tox

[Brianna Laugher]

Hello,

The contributing guide ( http://pytest.org/latest/contributing.html ) is
still missing a couple of steps I'm afraid...

I installed tox in my virtualenv and then ran python runtox.py -e
py27,py33,flakes as advised. At the end of the run tox tells me:

ERROR:   py27: could not install deps [nose, mock]
ERROR:   py33: InterpreterNotFound: python3.3
ERROR:   flakes: could not install deps [pytest-flakes=0.2]

I can manually pip install nose, mock and pytest-flakes, but I don't know
how to make python3.3 (which I have installed from my OS repo) visible or
available to this virtualenv. Any ideas?

Thanks,
Brianna

-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
Pytest-dev mailing list
Pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Setting up tox

[Brianna Laugher]

On 16 April 2014 16:44, holger krekel hol...@merlinux.eu wrote:


  I can manually pip install nose, mock and pytest-flakes, but I don't know
  how to make python3.3 (which I have installed from my OS repo) visible
 or
  available to this virtualenv. Any ideas?

 It should be on the PATH, so invoking python3.3 should basically work.


Do you mean calling runtox.py with the right python version? No luck there
either:

(pytest)brianna@montreal:~/workspace/pytest$ which python3.4
/usr/bin/python3.4
(pytest)brianna@montreal:~/workspace/pytest$ python3.4 runtox.py -v -e
py27,py34,flakes
/usr/bin/python3.4: No module named tox
(pytest)brianna@montreal:~/workspace/pytest$ which python3
/usr/bin/python3
(pytest)brianna@montreal:~/workspace/pytest$ python3 runtox.py -v -e
py27,py34,flakes
/usr/bin/python3: No module named tox

 Brianna

-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
Pytest-dev mailing list
Pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] fixtures and pylint W0621

[Brianna Laugher]

On 3 December 2013 18:39, holger krekel hol...@merlinux.eu wrote:
 Right, it seems that when we introduced @pytest.fixture we decided you can
 either use the prefix or the marker.  That could be lifted but i wonder
 if we should rather go for a different convention because pytest_funcarg__
 is not a beautiful prefix.  What do you think of pytest stripping the __ 
 prefix?

 @pytest.fixture
 def __foo2(monkeypatch):
return monkeypatch

 This fixture would become accessible via the foo2 name.  Using __foo2
 would yield a lookup error and the error would indicate there is a foo2
 available.  If you don't like it, any other suggestions?

Hmm. My main concern here would be that fixture definitions are easily
'findable' in a global search. The fixture decorator is easy to search
for, as is 'pytest_funcarg__'. Such an ugly prefix is also far easier
to google. Double underscore, not so much. The ugly prefix is also
good for backwards compat.

So, I don't really mind what happens as long as each fixture has at
least one of fixture decorator/ugly prefix.

cheers
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
Pytest-dev mailing list
Pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] parametrize and ids

[Brianna Laugher]

On 29 May 2013 17:48, holger krekel hol...@merlinux.eu wrote:

 agreed.   One a sidenote, yesterday i introduced a briefer way to
 specify argument names.  Your example would start like this:

 @pytest.mark.parametrize(wx,expectedCoverage,expectedTrend, ...)

 and you can also have spaces after the commas if you prefer.


I noticed that :) looks good. I think of parametrize like specifying
namedtuples so it is a good improvement.


 I'd recommend to write a wrapper @myparametrize which generates a
 pytest.mark.parametrize() instance in the end.  This way you could use
 and consolidate your API ideas in real life with today's pytest in real
 life before aiming for pytest inclusion.


Great idea. I discussed my idea with my workmate and he immediately
suggested I use a dictionary, with the key being the test name and the
value being the argvalue (test data). In doing that the test order is not
guaranteed, but one could use an OrderedDict I suppose if that was
important.

I have put up a working example here for anyone who is interested:
https://gist.github.com/pfctdayelise/5719730

cheers
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
Pytest-dev mailing list
Pytest-dev@python.org
http://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] parametrize and ids

[Brianna Laugher]

Another alternative - I would often prefer just doing what metafunc.addcall
does if you don't specify an id, which is just make an integer, like so:

  Function 'test_filterPrecipOrTS[0]'
  Function 'test_filterPrecipOrTS[1]'
  Function 'test_filterPrecipOrTS[2]'
  Function 'test_filterPrecipOrTS[3]'
  Function 'test_filterPrecipOrTS[4]'
  Function 'test_filterPrecipOrTS[5]'

Maybe it is wrong and should be updated to use idmaker :P
But basically, if the id can't be simple and meaningful to me (and with
parametrize it is often not), an integer would be less visual noise and
in the case of the mark parametrize, easy to map back to the specific test
data in the case of a failure.

Brianna

-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
Pytest-dev mailing list
Pytest-dev@python.org
http://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Using a context manager in a funcarg/fixture

[Brianna Laugher]

On 23 April 2013 17:33, Ronny Pfannschmidt ronny.pfannschm...@gmx.dewrote:

 Hi Holger, Brianna,

 there is 
 https://github.com/pelme/**pytest-contextfixturehttps://github.com/pelme/pytest-contextfixture
 which seems to handle it for the time being


Hi Ronny,

I didn't know about that, but I think this TODO is telling:

https://github.com/pelme/pytest-contextfixture/blob/master/pytest_contextfixture.py#L17

(ie, it's not really solved)

thanks
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
Pytest-dev mailing list
Pytest-dev@python.org
http://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] parametrize + xfail

[Brianna Laugher]

Hi again :)

A common problem I have is that I have a test that is parametrized with
py.test.mark.parametrize, I discover a bug, I want to add another test case
for that bug and mark it as xfail.

I have done something based on
http://stackoverflow.com/questions/12364801/how-to-mark-some-generated-tests-as-xfail-skip
for pytest_generate type functions, but it is awkward to do without
disrupting the existing cases, and somewhat overkill in cases where the
xfail is likely to be resolved (the bug is fixed) soon.

With py.test.mark.parametrize, I notice
https://bitbucket.org/hpk42/pytest/issue/124/allow-individual-parametrized-values-to-be

I was just thinking about this now and I wonder if it is possible to build
a decorator like this?

@py.test.mark.parametrizexfail('duration', 'expectedBrackets'), [
(7, [None, None, None, 7]),
(19, [None, 7, 6, 6]),
])
@py.test.mark.parametrize(('duration', 'expectedBrackets'), [
(24, [6, 6, 6, 6]),
(23, [6, 6, 6, 6]),
(25, [6, 6, 6, 6]),
])

So 5 cases would be fed into the test, with only the first two marked as
xfail.


Also while I'm at it, it could be good for pytest to issue a warning if
someone uses a mark called parameterize, parametrise or parameterise,
because I've been caught pondering why a mark wasn't working properly at
least once :)

cheers
Brianna



-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
___
Pytest-dev mailing list
Pytest-dev@python.org
http://mail.python.org/mailman/listinfo/pytest-dev