[pytest-dev] Appeal for co-maintainer for pytest-html

[Dave Hunt]

Hey folks,

When I took a step back from maintaining pytest-html and other plugins, Jim 
Brännlund and Ana Ribeiro offered to help take on some of this work. Between 
them they have performed an excellent job of triaging issues, reviewing pull 
requests, providing fixes, and pushing out new releases. Recently, Ana has had 
less time to contribute, which means Jim has taken on a lot of this work 
himself.

I’d like to see if there’s anyone in the community that might have some time to 
help Jim with maintaining the popular pytest-html 
 plugin? This plugin generates a 
HTML report for pytest results, and therefore it would be valuable if someone 
with some front-end experience could help. Although there are plenty of 
opportunities for new features, it would be most valuable to have someone 
helping with the maintenance tasks mentioned above.

There isn't a high volume of issues or pull requests for the project, so any 
level of contribution would likely have a significant positive impact.

I'd like to take this opportunity to once again thank both Jim and Ana for 
their contributions to the project, and to everyone who has used the plugin - 
especially those who have opened issues or submitted patches!

Thanks in advance,
Dave Hunt___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Looking for additional maintainers for pytest plugins

[Dave Hunt]

Thanks Ana! I’m not going away entirely, so I’d be happy to help anyone taking 
on a maintainer role. I may just turn off the Github notifications at some 
point, so that I only get email when I’m mentioned. :)

> On 30 Nov 2018, at 19:51, Ana Ribeiro  wrote:
> 
> Hi Dave,
> 
> I probably have technical knowledge for Pytest-HTML, but I never mantained a 
> popular technical project before. I would be willing to help mantain 
> Pytest-HTML if you could help me for the first weeks.
> 
> Cheers,
> Ana
> 
>> Em 30 de nov de 2018, à(s) 16:41, Brian Okken > <mailto:variedthoug...@gmail.com>> escreveu:
>> 
>> Dave, Jim,
>> 
>> Would you want this need mentioned on either Test & Code or Python Bytes 
>> podcast?
>> 
>> I don’t have bandwidth to help out, but perhaps some listeners do. But I 
>> don’t want to mention if you’d rather I didn’t. 
>> 
>> - Brian
>> 
>> On Nov 30, 2018, at 11:15 AM, Dave Hunt > <mailto:dh...@mozilla.com>> wrote:
>> 
>>> Due to a change in my role, I’m no longer going to be able to spend as much 
>>> time as I have with maintaining the plugins listed below. The maintenance 
>>> burden is very light, and releases are handled through Travis CI. I’ve 
>>> already had some excellent help from Jim Brännlund (BeyondEvil), and have 
>>> added him as a developer to a few of these. I’d appreciate any additional 
>>> help from the community to support these plugins, and if you’re aware of 
>>> somebody who would like to contribute please point them in my direction.
>>> 
>>> https://github.com/pytest-dev/pytest-base-url 
>>> <https://github.com/pytest-dev/pytest-base-url> - A very small plugin, no 
>>> commits in over a year
>>> https://github.com/pytest-dev/pytest-selenium 
>>> <https://github.com/pytest-dev/pytest-selenium> - Jim is a developer, and 
>>> helps out a lot with this one, he's taken care of much of the recent 
>>> development and responding to issues
>>> https://github.com/pytest-dev/pytest-html 
>>> <https://github.com/pytest-dev/pytest-html> - This is probably the most 
>>> popular plugin I’ve been maintaining, and I think there’s a lot of 
>>> potential for enhancements (great ideas already in the tracker)
>>> https://github.com/pytest-dev/pytest-metadata 
>>> <https://github.com/pytest-dev/pytest-metadata> - Split off as a dependency 
>>> for pytest-html, relatively small plugin and minimal maintenance needs. Jim 
>>> is a developer for this plugin too
>>> https://github.com/pytest-dev/pytest-variables 
>>> <https://github.com/pytest-dev/pytest-variables> - Another small plugin 
>>> with very few maintenance needs
>>> https://github.com/pytest-dev/pytest-repeat 
>>> <https://github.com/pytest-dev/pytest-repeat> - I don’t really maintain 
>>> this one currently, but feel that it’s worth mentioning because I was one 
>>> of the early contributors
>>> 
>>> I’m happy to answer any questions, and keen to hear any suggestions for 
>>> handling any handover
>>> 
>>> I’m sure these are in safe hands, and I will continue to use them myself, 
>>> and promote the use of them to others!
>>> 
>>> Cheers,
>>> Dave
>>> ___
>>> pytest-dev mailing list
>>> pytest-dev@python.org <mailto:pytest-dev@python.org>
>>> https://mail.python.org/mailman/listinfo/pytest-dev 
>>> <https://mail.python.org/mailman/listinfo/pytest-dev>
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org <mailto: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] Looking for additional maintainers for pytest plugins

[Dave Hunt]

That’s very kind of you Brian, maybe a mention on Twitter would be good, but I 
don’t think it merits the attention of your podcast listeners (I really enjoyed 
the latest episode, by the way!)

I tried writing a tweet myself, but couldn’t find a satisfying way to word it. 
:D

Cheers,
Dave

> On 30 Nov 2018, at 19:41, Brian Okken  wrote:
> 
> Dave, Jim,
> 
> Would you want this need mentioned on either Test & Code or Python Bytes 
> podcast?
> 
> I don’t have bandwidth to help out, but perhaps some listeners do. But I 
> don’t want to mention if you’d rather I didn’t. 
> 
> - Brian
> 
> On Nov 30, 2018, at 11:15 AM, Dave Hunt  <mailto:dh...@mozilla.com>> wrote:
> 
>> Due to a change in my role, I’m no longer going to be able to spend as much 
>> time as I have with maintaining the plugins listed below. The maintenance 
>> burden is very light, and releases are handled through Travis CI. I’ve 
>> already had some excellent help from Jim Brännlund (BeyondEvil), and have 
>> added him as a developer to a few of these. I’d appreciate any additional 
>> help from the community to support these plugins, and if you’re aware of 
>> somebody who would like to contribute please point them in my direction.
>> 
>> https://github.com/pytest-dev/pytest-base-url 
>> <https://github.com/pytest-dev/pytest-base-url> - A very small plugin, no 
>> commits in over a year
>> https://github.com/pytest-dev/pytest-selenium 
>> <https://github.com/pytest-dev/pytest-selenium> - Jim is a developer, and 
>> helps out a lot with this one, he's taken care of much of the recent 
>> development and responding to issues
>> https://github.com/pytest-dev/pytest-html 
>> <https://github.com/pytest-dev/pytest-html> - This is probably the most 
>> popular plugin I’ve been maintaining, and I think there’s a lot of potential 
>> for enhancements (great ideas already in the tracker)
>> https://github.com/pytest-dev/pytest-metadata 
>> <https://github.com/pytest-dev/pytest-metadata> - Split off as a dependency 
>> for pytest-html, relatively small plugin and minimal maintenance needs. Jim 
>> is a developer for this plugin too
>> https://github.com/pytest-dev/pytest-variables 
>> <https://github.com/pytest-dev/pytest-variables> - Another small plugin with 
>> very few maintenance needs
>> https://github.com/pytest-dev/pytest-repeat 
>> <https://github.com/pytest-dev/pytest-repeat> - I don’t really maintain this 
>> one currently, but feel that it’s worth mentioning because I was one of the 
>> early contributors
>> 
>> I’m happy to answer any questions, and keen to hear any suggestions for 
>> handling any handover
>> 
>> I’m sure these are in safe hands, and I will continue to use them myself, 
>> and promote the use of them to others!
>> 
>> Cheers,
>> Dave
>> ___
>> pytest-dev mailing list
>> pytest-dev@python.org <mailto:pytest-dev@python.org>
>> https://mail.python.org/mailman/listinfo/pytest-dev 
>> <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] Looking for additional maintainers for pytest plugins

[Dave Hunt]

Due to a change in my role, I’m no longer going to be able to spend as much 
time as I have with maintaining the plugins listed below. The maintenance 
burden is very light, and releases are handled through Travis CI. I’ve already 
had some excellent help from Jim Brännlund (BeyondEvil), and have added him as 
a developer to a few of these. I’d appreciate any additional help from the 
community to support these plugins, and if you’re aware of somebody who would 
like to contribute please point them in my direction.

https://github.com/pytest-dev/pytest-base-url 
 - A very small plugin, no 
commits in over a year
https://github.com/pytest-dev/pytest-selenium 
 - Jim is a developer, and helps 
out a lot with this one, he's taken care of much of the recent development and 
responding to issues
https://github.com/pytest-dev/pytest-html 
 - This is probably the most popular 
plugin I’ve been maintaining, and I think there’s a lot of potential for 
enhancements (great ideas already in the tracker)
https://github.com/pytest-dev/pytest-metadata 
 - Split off as a dependency for 
pytest-html, relatively small plugin and minimal maintenance needs. Jim is a 
developer for this plugin too
https://github.com/pytest-dev/pytest-variables 
 - Another small plugin with 
very few maintenance needs
https://github.com/pytest-dev/pytest-repeat 
 - I don’t really maintain this 
one currently, but feel that it’s worth mentioning because I was one of the 
early contributors

I’m happy to answer any questions, and keen to hear any suggestions for 
handling any handover

I’m sure these are in safe hands, and I will continue to use them myself, and 
promote the use of them to others!

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

Re: [pytest-dev] keeping passwords out of code

[Dave Hunt]

This is what I originally developed pytest-variables for 
(https://pypi.org/project/pytest-variables/ 
). Maybe you’ll find that useful, 
but it sounds like you already have a similar solution. For Jenkins, we use the 
credentials plugin to store the variables files, and then reference them from 
the jobs via environment variables. See 
https://github.com/mozilla/mozillians-tests/blob/master/Jenkinsfile#L40 
 and 
https://github.com/mozilla/mozillians-tests/blob/master/Jenkinsfile#L53 
 for 
an example of where we use this in a Jenkins declarative pipeline.

> On 23 Sep 2018, at 19:47, Floris Bruynooghe  wrote:
> 
> Hi Derek,
> 
> On Sat 22 Sep 2018 at 09:19 -0700, Derek Sisson wrote:
>> I currently use a local yaml file, with passwords keyed to account ids,
>> along with a data model of users in the codebase keyed to the same IDs. My
>> conftest queries the yaml file with the ids to grab the passwords, and it's
>> set up to throw exceptions if there is anything out of sync between the
>> data model and the yaml file data.
>> 
>> Cumbersome, but works locally. I need to port the framework to Jenkins,
>> so I need a better and secure system.
>> 
>> Suggestions on better ways of managing passwords and secrets in a
>> pytest/jenkins context?
> 
> This isn't really a pytest question to be fair.  It's just that you
> happen to stumble into secrets management via testing, which is
> certainly one common way of discovering this rabbit hole.
> 
> The simple version which is still somewhat sub-optimal is pass the
> secrets via environment variables or something, for Jenkins specifically
> you should probably look at it's Credentials Binding plugin or so.
> 
> The full-blow solution is to use something like vaultproject.io to
> manage secrets.  Obviously this is a fair amount of work but you'll get
> good secrets management at the end.
> 
> 
> Cheers,
> Floris
> ___
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev



signature.asc
Description: Message signed with OpenPGP
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Code of conduct for pytest organisation on GitHub

[Dave Hunt]

I’d like to add a code of conduct for my pytest plugins, and as they’re mostly 
under the pytest organisation on GitHub I thought it would make sense to use 
the same as the pytest project. I was surprised to find that the pytest project 
does not currently have a code of conduct according to 
https://github.com/pytest-dev/pytest/community 
. Is there one documented 
elsewhere? If not, which should we adopt?

Cheers,
Dave


signature.asc
Description: Message signed with OpenPGP
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] [tox-dev] EuroPython 2018: help desk

[Dave Hunt]

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-...@python.org
> https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/



signature.asc
Description: Message signed with OpenPGP
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Proposal: Move davehunt/pytest-metadata to pytest-dev/metadata

[Dave Hunt]

Thanks everyone! Bruno, I’ve initiated the transfer.

Dave

> On 1 Dec 2017, at 18:11, Bruno Oliveira  wrote:
> 
> Great, thanks everyone!
> 
> Dave, feel free to transfer to me when you have the chance and I will follow 
> with the procedure. :)
> 
> On Fri, Dec 1, 2017 at 2:32 PM Florian Bruhin  > wrote:
> On Fri, Dec 01, 2017 at 10:06:51AM -0300, Ana Ribeiro wrote:
> > I don't know if my +1 means anything since I am not an active maintainer of
> > pytest, but I definitely give a +1
> 
> I'll +1 your +1 then ;-)
> 
> Florian
> 
> --
> https://www.qutebrowser.org   | 
> m...@the-compiler.org  (Mail/XMPP)
>GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc 
> 
>  I love long mails!  | https://email.is-not-s.ms/ 
> 
> ___
> 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



signature.asc
Description: Message signed with OpenPGP
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] Proposal: Move davehunt/pytest-metadata to pytest-dev/metadata

[Dave Hunt]

Great, thanks Bruno. We just need one more +1 in order to proceed.

Cheers,
Dave

> On 30 Nov 2017, at 16:18, Bruno Oliveira <nicodde...@gmail.com> wrote:
> 
> 
> 
> On Thu, Nov 30, 2017 at 2:16 PM Dave Hunt <dh...@mozilla.com 
> <mailto:dh...@mozilla.com>> wrote:
> I’d like to propose moving the pytest-metadata plugin to pytest-dev.
> 
> Definitely +1!
> 
> Cheers,
> Bruno.
> 
> It’s a dependency for pytest-html, which is already in the pytest-dev 
> organisation, so I believe this makes sense. I would still be the 
> owner/maintainer, but it means that if I’m unavailable then others could land 
> emergency fixes. The repository is configured to deploy after a successful 
> Travis CI build whenever a tag is pushed, so anyone with push access would be 
> able to release a new version.
> 
> https://pypi.python.org/pypi/pytest-metadata/ 
> <https://pypi.python.org/pypi/pytest-metadata/>
> 
> Cheers,
> Dave
> ___
> pytest-dev mailing list
> pytest-dev@python.org <mailto:pytest-dev@python.org>
> https://mail.python.org/mailman/listinfo/pytest-dev 
> <https://mail.python.org/mailman/listinfo/pytest-dev>



signature.asc
Description: Message signed with OpenPGP
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

[pytest-dev] Proposal: Move davehunt/pytest-metadata to pytest-dev/metadata

[Dave Hunt]

I’d like to propose moving the pytest-metadata plugin to pytest-dev. It’s a 
dependency for pytest-html, which is already in the pytest-dev organisation, so 
I believe this makes sense. I would still be the owner/maintainer, but it means 
that if I’m unavailable then others could land emergency fixes. The repository 
is configured to deploy after a successful Travis CI build whenever a tag is 
pushed, so anyone with push access would be able to release a new version.

https://pypi.python.org/pypi/pytest-metadata/ 


Cheers,
Dave


signature.asc
Description: Message signed with OpenPGP
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] [tox-dev] Suggestion: EuroPython pytest/tox/devpi helpdesk

[Dave Hunt]

Unfortunately not. Might be able to attend a pytest sprint if one is planned, 
but otherwise it’ll probably be next year for me.

> On 24 Apr 2017, at 16:00, Oliver Bestwalter <oli...@bestwalter.de> wrote:
> 
> Hi Dave,
> 
> no problem - was looking forward to see you to though. Are you attending 
> Pycon US? I might be there for the sprints.
> 
> Cheers,
> Oliver
> 
> On Mon, 24 Apr 2017 at 15:56 Dave Hunt <dh...@mozilla.com 
> <mailto:dh...@mozilla.com>> wrote:
> Unfortunately I’ve decided not to attend EuroPython this year, so I’ll need 
> to revoke my offer to help out. Hopefully next year..!
> 
>> On 28 Mar 2017, at 09:21, Dave Hunt <dh...@mozilla.com 
>> <mailto:dh...@mozilla.com>> wrote:
>> 
>> I’m thinking of coming to EuroPython, and would be happy to spend some time 
>> at the helpdesk. My particular area of expertise would be the plugins I 
>> maintain, but I’m sure I can also answer some pytest/tox/devpi queries too.
>> 
>> Cheers,
>> Dave
>> 
>>> On 27 Mar 2017, at 21:42, Oliver Bestwalter <oli...@bestwalter.de 
>>> <mailto:oli...@bestwalter.de>> wrote:
>>> 
>>> Hi all,
>>> 
>>> EuroPython is on the horizon and they have a new thing (or at least new for 
>>> me) called "helpdesk"
>>> 
>>> > Helpdesk / 10 slots
>>> 
>>> > Helpdesks are a great way to share your experience on a technology, by 
>>> > offering to help people answering their questions and solving their 
>>> > practical problems. You can run a helpdesk by yourself or with colleagues 
>>> > and friends. Each helpdesk will be open for 3 hours in total, 1.5 hours 
>>> > in the morning and 1.5 hours in the afternoon. People looking for help 
>>> > will sign up for a 30 minute slot and talk to you. There is no specific 
>>> > preparation needed; you just need to be proficient in the technology you 
>>> > run the helpdesk for.
>>> 
>>> see: https://ep2017.europython.eu/en/call-for-proposals/ 
>>> <https://ep2017.europython.eu/en/call-for-proposals/>
>>> 
>>> I would be interested to try this and volunteer to help with questions 
>>> about tox mainly. Would anybody else interested in that kind of thing? If 
>>> we find a handful of people that would want to do that, we could have a 
>>> tox/pytest/devpi helpdesk :)
>>> 
>>> Cheers,
>>> Oliver
>>> ___
>>> tox-dev mailing list
>>> tox-...@python.org <mailto:tox-...@python.org>
>>> https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/ 
>>> <https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/>
>> 
> 

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

Re: [pytest-dev] [tox-dev] Suggestion: EuroPython pytest/tox/devpi helpdesk

[Dave Hunt]

Unfortunately I’ve decided not to attend EuroPython this year, so I’ll need to 
revoke my offer to help out. Hopefully next year..!

> On 28 Mar 2017, at 09:21, Dave Hunt <dh...@mozilla.com> wrote:
> 
> I’m thinking of coming to EuroPython, and would be happy to spend some time 
> at the helpdesk. My particular area of expertise would be the plugins I 
> maintain, but I’m sure I can also answer some pytest/tox/devpi queries too.
> 
> Cheers,
> Dave
> 
>> On 27 Mar 2017, at 21:42, Oliver Bestwalter <oli...@bestwalter.de 
>> <mailto:oli...@bestwalter.de>> wrote:
>> 
>> Hi all,
>> 
>> EuroPython is on the horizon and they have a new thing (or at least new for 
>> me) called "helpdesk"
>> 
>> > Helpdesk / 10 slots
>> 
>> > Helpdesks are a great way to share your experience on a technology, by 
>> > offering to help people answering their questions and solving their 
>> > practical problems. You can run a helpdesk by yourself or with colleagues 
>> > and friends. Each helpdesk will be open for 3 hours in total, 1.5 hours in 
>> > the morning and 1.5 hours in the afternoon. People looking for help will 
>> > sign up for a 30 minute slot and talk to you. There is no specific 
>> > preparation needed; you just need to be proficient in the technology you 
>> > run the helpdesk for.
>> 
>> see: https://ep2017.europython.eu/en/call-for-proposals/ 
>> <https://ep2017.europython.eu/en/call-for-proposals/>
>> 
>> I would be interested to try this and volunteer to help with questions about 
>> tox mainly. Would anybody else interested in that kind of thing? If we find 
>> a handful of people that would want to do that, we could have a 
>> tox/pytest/devpi helpdesk :)
>> 
>> Cheers,
>> Oliver
>> ___
>> tox-dev mailing list
>> tox-...@python.org <mailto:tox-...@python.org>
>> https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/
> 

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

Re: [pytest-dev] [tox-dev] Suggestion: EuroPython pytest/tox/devpi helpdesk

[Dave Hunt]

I’m thinking of coming to EuroPython, and would be happy to spend some time at 
the helpdesk. My particular area of expertise would be the plugins I maintain, 
but I’m sure I can also answer some pytest/tox/devpi queries too.

Cheers,
Dave

> On 27 Mar 2017, at 21:42, Oliver Bestwalter  wrote:
> 
> Hi all,
> 
> EuroPython is on the horizon and they have a new thing (or at least new for 
> me) called "helpdesk"
> 
> > Helpdesk / 10 slots
> 
> > Helpdesks are a great way to share your experience on a technology, by 
> > offering to help people answering their questions and solving their 
> > practical problems. You can run a helpdesk by yourself or with colleagues 
> > and friends. Each helpdesk will be open for 3 hours in total, 1.5 hours in 
> > the morning and 1.5 hours in the afternoon. People looking for help will 
> > sign up for a 30 minute slot and talk to you. There is no specific 
> > preparation needed; you just need to be proficient in the technology you 
> > run the helpdesk for.
> 
> see: https://ep2017.europython.eu/en/call-for-proposals/ 
> 
> 
> I would be interested to try this and volunteer to help with questions about 
> tox mainly. Would anybody else interested in that kind of thing? If we find a 
> handful of people that would want to do that, we could have a 
> tox/pytest/devpi helpdesk :)
> 
> Cheers,
> Oliver
> ___
> tox-dev mailing list
> tox-...@python.org
> https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/

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

Re: [pytest-dev] Google Summer of Code

[Dave Hunt]

This is a great idea! I blogged about my experiences with mentoring last year 
at http://davehunt.co.uk/mozilla/2016/09/26/lessons-from-mentoring.html 
<http://davehunt.co.uk/mozilla/2016/09/26/lessons-from-mentoring.html> and I’m 
happy to answer any questions.

> On 20 Jan 2017, at 12:49, Bruno Oliveira <nicodde...@gmail.com> wrote:
> 
> Hi Ana,
> I think that is a great idea, thanks for bringing this to attention of the 
> group!
> 
> I did take a quick look at the site, and for those who don’t know (myself 
> included) what it means for us (as Pytest organization), here’s an excerpt 
> from their overview <https://summerofcode.withgoogle.com/how-it-works/>:
> 
> Organizations
> Open source projects apply to be mentor organizations. Once accepted, 
> organizations discuss possible ideas with students and then decide on the 
> proposals they wish to mentor for the summer. They provide mentors to help 
> guide each student through the program.
> 
> Mentors
> Existing contributors with the organizations can choose to mentor a student 
> project. Mentors and students work together to determine appropriate 
> milestones and requirements for the summer. Mentor interaction is a vital 
> part of the program.
> 
> So before moving ahead I think we just need to see if:
> 
> Who wants to volunteer to be a mentor? I suppose it doesn’t take too much 
> time, only a few hours per week to synchronize activities, track progress and 
> answer the eventual question from the student. Dave Hunt might add some 
> comments here based on his experience on mentoring Ana for Mozilla.
> I think we have a ton of small improvements that could be tackled by a 
> learning student, but I suppose we can also try to work on a single larger 
> improvement. Either way, I think that’s for the mentor/student to ultimately 
> decide.
> Anybody has any reason to oppose for applying at all?
> I think it is a great opportunity to promote pytest and help students around 
> the globe.
> 
> Although I would love to, I can’t volunteer as I already have little free 
> time to work on pytest as it is. :/
> 
> Thoughts?
> 
> Cheers,
> Bruno.
> 
> On Fri, Jan 20, 2017 at 12:13 AM Ana Ribeiro <aninhacostaribe...@gmail.com 
> <mailto:aninhacostaribe...@gmail.com>> wrote:
> 
> 
> 
> Hello Fellows, 
> 
> Applications to Google Summer of Code to organizations are open! We should 
> apply as Pytest!
> 
> https://summerofcode.withgoogle.com/ <https://summerofcode.withgoogle.com/>
> 
> I think I can help with the application (Writing it), but I can not be an 
> organization admin because I am eligible to apply as a student and I think 
> I'll do that (either applying to Mozilla or Pytest).
> 
> Best Regards,
> Ana 
> ___
> pytest-dev mailing list
> pytest-dev@python.org <mailto:pytest-dev@python.org>
> https://mail.python.org/mailman/listinfo/pytest-dev 
> <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] EuroPython Talk on pytest 3.0

[Dave Hunt]

"You can now run pytest without using py dot test" then drop the mic and walk 
off to rapturous applause.  #dropthedot

Dave Hunt

> On 8 Jul 2016, at 20:59, Raphael Pierzina <raph...@hackebrot.de> wrote:
> 
> Hi pytest-friends,
> 
> as we are getting closer to EuroPython and my talk on Pytest 3.0, I would be 
> delighted if you could send me your ideas on what you feel is most important 
> to cover. I will be spending the weekend to work on my talk and send around 
> what I have early next week.
> 
> https://ep2016.europython.eu/conference/talks/pytest-30
> 
> Holger sent around a list of features/improvement that we hope to ship with 
> pytest (and tox); search for “[pytest-dev] pytest-3.0 / tox-2.4 release 
> plans” from 25 June. What’s the current status and what do you think will be 
> merged in the next couple of days to be included in the release?
> 
> Any feedback or questions, please let me know.
> 
> Cheers
> Raphael
> ___
> 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] Request for additional plugin maintainers on PyPI

[Dave Hunt]

Last week the following plugins of mine were moved into pytest-dev:
https://github.com/pytest-dev/pytest-selenium 
<https://github.com/pytest-dev/pytest-selenium>
https://github.com/pytest-dev/pytest-html 
<https://github.com/pytest-dev/pytest-html>
https://github.com/pytest-dev/pytest-variables 
<https://github.com/pytest-dev/pytest-variables>
https://github.com/pytest-dev/pytest-base-url 
<https://github.com/pytest-dev/pytest-base-url>
I fully intend to continue to support these plugins myself. The main reason for 
moving these is to ensure that patches for important fixes can be made without 
me. I’d also like to add at least one maintainer for each of these projects in 
PyPI so that releases can be pushed without me.

Please respond with your GitHub username if you would like to be added as a 
developer for any of the above plugins, and your PyPI username if you would 
like to be considered as a maintainer (so you can push new releases). At this 
time I would like to restrict new developers and maintainers to pytest core 
committers.

Thanks,

--
Dave Hunt
Automation Engineer
Mozilla Corporation
dh...@mozilla.com

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

Re: [pytest-dev] Climbing at the sprint

[Dave Hunt]

I’m in, though the one and only time I’ve done indoor bouldering I cracked a 
rib. ;)

Dave

> On 14 Jun 2016, at 10:53, Floris Bruynooghe  wrote:
> 
> On 14 June 2016 at 08:32, Andreas Pelme  wrote:
>> 
>>> On 14 juni 2016, at 09:17, Florian Bruhin  wrote:
>>> 
>>> Is there something I can join without climbing experience and without
>>> being too much of a sports guy? If so, count me in, because it *does*
>>> sound like fun :P
>> 
>> Yes for sure! It’s easy to get started and there are usually problems for
>> all kinds of levels. You can most likely rent shoes/harness at the
>> climbing gym. It is a lot of fun! :D
> 
> I'll confirm this, anyone with or without experience is free to join,
> climbing walls normally cater for all levels and can provide the gear.
> So we'll be more then happy to help anyone who wants to come along.
> 
> Floris
> ___
> 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] pytest crowdfunding: t-shirt/sticker designs?

[Dave Hunt]

> On 2 Jun 2016, at 13:13, Vasily Kuznetsov  wrote:
> 
> "1337 passed in 0.42 seconds"

<3 this___
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?

[Dave Hunt]

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 
>> <mailto: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 
>>>> <mailto: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> <mailto: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 
>>>>> <mailto: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? 
>>>>> 
>>>>> We could publish them via updates every few days. Any takers? 
>>>>> -- 
>>>>> Sent using mobile touch keys, increased chances for errors and 
>>>>> misunderstandings. Enjoy! 
>>>>> ___
>>>>> pytest-dev mailing list
>>>>> pytest-dev@python.org <mailto:pytest-dev@python.org> 
>>>>> <mailto:pytest-dev@python.org <mailto:pytest-dev@python.org>>
>>>>> https://mail.python.org/mailman/listinfo/pytest-dev 
>>>>> <https://mail.python.org/mailman/listinfo/pytest-dev> 
>>>>> <https://mail.python.org/mailman/listinfo/pytest-dev 
>>>>> <https://mail.python.org/mailman/listinfo/pytest-dev>>
>>>>> 
>>>>> ___
>>>>> pytest-dev mailing list
>>>>> pytest-dev@python.org <mailto:pytest-dev@python.org> 
>>>>> <mailto:pytest-dev@python.org <mailto:pytest-dev@python.org>>
>>>>> https://mail.python.org/mailman/listinfo/pytest-dev 
>>>>> <https://mail.python.org/mailman/listinfo/pytest-dev>
>>>> 
>>> 
>> 
>> -- 
>> about me:http://holgerkrekel.net/about-me/ 
>> <http://holgerkrekel.net/about-me/>
>> contracting: http://merlinux.eu <http://merlinux.eu/>
> 

___
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?

[Dave Hunt]

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  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"  > 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? 
> 
> We could publish them via updates every few days. Any takers? 
> -- 
> Sent using mobile touch keys, increased chances for errors and 
> misunderstandings. Enjoy! 
> ___
> 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] New plugin for generating HTML report (and request for help)

[Dave Hunt]

Thanks for the help! I’ve just released the plugin on PyPI:
https://pypi.python.org/pypi/pytest-html

--
Dave Hunt
Firefox OS Automation Engineer
Mozilla Corporation
dh...@mozilla.com

 On 19 Apr 2015, at 09:16, holger krekel hol...@merlinux.eu wrote:
 
 On Thu, Apr 16, 2015 at 17:46 +0100, Dave Hunt wrote:
 Thanks Bruno, the custom hook works well. Here’s the change: 
 https://github.com/davehunt/pytest-html/commit/2a405a3cdc638c1896ab3d1074296496bb1fa3a8
  
 https://github.com/davehunt/pytest-html/commit/2a405a3cdc638c1896ab3d1074296496bb1fa3a8
 
 Now I need to work out why I get issues when I use this with pytest-xdist. 
 It looks like it’s complaining about the extra report details not being 
 serializable?! See traceback below:
 
 Yes, you need to make sure that anything extra you put on the report is 
 marshallable.
 In the case of your url you may just send a string and parse as url on
 the logreport/master side.
 
 holger
 
 
 test_login.py::TestLogin::test_invalid_username INTERNALERROR Traceback 
 (most recent call last):
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/main.py,
  line 84, in wrap_session
 INTERNALERROR doit(config, session)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/main.py,
  line 122, in _main
 INTERNALERROR config.hook.pytest_runtestloop(session=session)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 521, in __call__
 INTERNALERROR return self._docall(self.methods, kwargs)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 528, in _docall
 INTERNALERROR firstresult=self.firstresult).execute()
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 394, in execute
 INTERNALERROR res = method(*args)
 INTERNALERROR   File remote exec, line 56, in pytest_runtestloop
 INTERNALERROR   File remote exec, line 72, in run_tests
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 521, in __call__
 INTERNALERROR return self._docall(self.methods, kwargs)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 528, in _docall
 INTERNALERROR firstresult=self.firstresult).execute()
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 393, in execute
 INTERNALERROR return wrapped_call(method(*args), self.execute)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 113, in wrapped_call
 INTERNALERROR return call_outcome.get_result()
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 138, in get_result
 INTERNALERROR py.builtin._reraise(*ex)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 123, in __init__
 INTERNALERROR self.result = func()
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 394, in execute
 INTERNALERROR res = method(*args)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/runner.py,
  line 65, in pytest_runtest_protocol
 INTERNALERROR runtestprotocol(item, nextitem=nextitem)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/runner.py,
  line 75, in runtestprotocol
 INTERNALERROR reports.append(call_and_report(item, call, log))
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/runner.py,
  line 123, in call_and_report
 INTERNALERROR hook.pytest_runtest_logreport(report=report)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 521, in __call__
 INTERNALERROR return self._docall(self.methods, kwargs)
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib/python2.7/site-packages/pytest-2.7.0-py2.7.egg/_pytest/core.py,
  line 528, in _docall
 INTERNALERROR firstresult=self.firstresult).execute()
 INTERNALERROR   File 
 /Users/dhunt/.virtualenvs/tmp-97b1b20a17ffb8d0/lib