Invitation to "adopt pytest month"

[Thomas De Schampheleire]

On Wed, Mar 25, 2015 at 11:15 AM, Thomas De Schampheleire
<patrickdepinguin at gmail.com> wrote:
> Hi,
>
> On Mon, Mar 23, 2015 at 10:35 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>>
>> On 20 Mar 2015 09:32, "Mads Kiilerich" <mads at kiilerich.com> wrote:
>>>
>>> On 03/19/2015 11:30 PM, Brianna Laugher wrote:
>>>>
>>>> Hello,
>>>>
>>>> I am a contributor to the testing library pytest, and in April we are
>>>> holding "adopt pytest month". We are inviting open source projects who
>>>> are interested in possibly taking up pytest, to be paired with
>>>> experienced pytest users, who can help them convert and write tests,
>>>> and show ways to make the most of pytest. More info here:
>>>> https://pytest.org/latest/adopt.html
>>>>
>>>> Pytest tests typically require much less boilerplate and feel more
>>>> "Pythonic" than unittest style tests, and there are also 100+ plugins
>>>> available, as well as many API hooks for writing your own
>>>> customisations. (Although, it can run unittest style tests by default,
>>>> as well as nose and doctests.) So... we think it's pretty cool and
>>>> have lots of volunteers eager to help spread the love.
>>>>
>>>> This is a bit of a cold call email, so please excuse me for butting
>>>> in. Although I noticed testing is on your "road map", so... if there
>>>> is someone who would be interested in working with a
>>>> pytest volunteer on this...please let me know/sign up! :)
>>>
>>>
>>> Thank you for the offer! We could certainly use that - there is a lot of
>>> room for improvement here ;-)
>>>
>>> The big question is if someone "here" have time and timing to work on it
>>> on our side and pair with you. That would be awesome. Anyone?
>>
>> I would be interested in working on it, but I'd be a Kallithea newbie as
>> well when it came to actually submitting patches to the project.
>
> I would also like to express my support to this initiative.
> My time is also severely limited, but I'm willing to help guide a
> person from the pytest side via e-mail (in cooperation with others
> like Mads and Nick, hopefully).
>
> What would the scope of this month be, besides switching the test runner?
>
> - One aspect I recently inquired about myself is related to fixtures
> and the creation/modification of a repository for the execution of a
> test. See http://lists.sfconservancy.org/pipermail/kallithea-general/2015q1/000232.html
> and Mads' reply:
> http://lists.sfconservancy.org/pipermail/kallithea-general/2015q1/000272.html.
>   Fixing this would probably require both help from pytest as internal
> knowledge of Kallithea.
>
> - Improving existing tests to write them in a more pytest way could be
> interesting
>
> - Misc improvements
>   - do not dump all test files in /tmp but rather in a subdirectory
>   - check why parallel test execution seems to fail (at least on
> nosetests it does)

   - investigate/profile why each test takes relatively long to
complete, while really most tests are making a simple http request and
check some output.