From p-santoro at sbcglobal.net Fri May 2 00:32:19 2014 From: p-santoro at sbcglobal.net (Peter) Date: Thu, 01 May 2014 18:32:19 -0400 Subject: [pytest-dev] Using Pytest 2.5.2 to Automate Testing of a Non-Python Application Message-ID: <5362CB73.8060001@sbcglobal.net> Firstly, I'd like to thank Holger Krekel and the rest of the pytest team for all their hard work (including the very good documentation and videos). I'm a novice pytest user and I wanted to run a scenario by more experienced pytest users, before potentially going down the wrong path. I would appreciate feedback on the helper functions below (limited testing suggests that they do work) and suggestions for alternative approaches. Thank you, Peter Santoro ============================ GIVEN: Pytest will be used to automate the running and evaluation of tests for a system that is not written in Python. I have already prototyped this in Python without using pytest. I'm currently converting my prototype code to conform with pytest APIs, rules, and conventions. So far so good. There will eventually be hundreds of tests, each of which requires the copying of a test specific directory tree structure from a source location to a destination location (required by the system being tested). I want to avoid copying any extra directory trees, because: 1) it will increase the time it takes the copying fixture(s) to run 2) it will also cause the system actually running the tests (outside of pytest, but run via a fixture) to do unnecessary work (i.e. waste time by running too many tests) I also want to limit the amount of work required to create each test function, so I plan to use helper functions that utilize the unique docid to collect the specific test results from the system being tested and use asserts to compare the result with the previously stored expected results. The proposed test function naming convention is test_doctype_docyear_schema_docid, where: doctype = document type docyear = document's year schema = document's xml schema version docid = globally unique document id In addition to using pytest markers, this naming convention (via pytest -k command line option), will allow for easy selection of the tests to be run from the pytest command line. The proposed source location directory tree structure (holds test input files and expected results record): docyear_schema | ------- doctype | ------------ docid The destination directory tree structure is fixed per the software that will be actually running the tests: location based on doctype | ------------ docid POSSIBLE SOLUTIONS TO DIRECTORY TREE COPYING FIXTURE(S): 1) Write a separate copying fixture function for each test; however, this seems like too much work. 2) Use pytest markers to logically group tests (see marker related helper functions below), but this becomes problematic if only a small subset of the marked group(s) needs to be run. 3) Use a suitable test function naming convention that would allow a single copying fixture function to handle the copying for all selected tests. This of course requires that the copying fixture knows what tests actually requested itself (see fixture_test* functions below). This is my preferred approach. # marker helper functions def markers(node): for v in node.keywords.values(): if isinstance(v, (MarkDecorator, MarkInfo)): yield v def marker_names(node): return [m.name for m in markers(node)] def request_markers(request): for n in request.node.items: yield from markers(n) def request_marker_names(request): return [m.name for m in request_markers(request)] # helper functions to get the applicable tests for a given fixture def fixture_test_names(name, request): return [n.name for n in fixture_tests(name, request)] def fixture_tests(name, request): for n in request.node.items: if name in n.fixturenames: yield n # sample hook function using a helper function to get list of marker names to make decisions on def pytest_collection_modifyitems(session, config, items): # hook for n, item in enumerate(items): print(n, item.nodeid, list(marker_names(item))) if 'func2' in item.nodeid: del items[n] # sample fixture using helper functions to get tests associated with itself @pytest.fixture(scope='session') def fcopy(request): """copy files for selected tests that use the fcopy fixture""" print(list(fixture_tests('fcopy', request))) print(fixture_test_names('fcopy', request)) # sample fixture using helper functions to get list of marker names @pytest.fixture(scope='session') def fcopy2(request): """copy files associated with certain marker(s)""" print(list(request_markers(request))) print(request_marker_names(request)) # sample test functions that use the fcopy fixture @pytest.mark.mymarker1 @pytest.mark.mymarker2 def test_function1(fcopy): pass @pytest.mark.mymarker3 @pytest.mark.mymarker4 def test_function2(fcopy): pass From holger at merlinux.eu Thu May 15 19:01:33 2014 From: holger at merlinux.eu (holger krekel) Date: Thu, 15 May 2014 17:01:33 +0000 Subject: [pytest-dev] pytest logo / comments welcome In-Reply-To: <20140429082817.GP1151@merlinux.eu> References: <20140429082817.GP1151@merlinux.eu> Message-ID: <20140515170133.GA1895@merlinux.eu> Hi all, Thanks for all the feedback. the logo competition is online: http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ I erred regarding the site btw. I choose 12designer because i could guarantee the payment and prepayed already. By contrast, 99designers allows to not select anything ("money back guarantee") which makes it even more of a gamble for designers than it already is. So in two weeks pytest is going to have a logo. I plan to involve you people here in the selection so stay tuned :) And oh, if someone wants to add some money i can still raise the price. (Just sent me a private mail and we arrange it). best, holger On Tue, Apr 29, 2014 at 08:28 +0000, holger krekel wrote: > Hi all, > > am thinking of providing pytest with a logo finally ... gets about > time after all those years i guess :) > > My plan is to go for 99designs and guarantee some 250 euros for the > final logo. There are a few questions they want as background where i'd > like to hear opinions :) > > - should it be a little animal? should it be abstract? > > - should it contain the text "pytest" or "py.test" or nothing? > > - should it have snakes? > > - should it have a goat in some way in it? > > - any colors you'd prefer? > > - any testing tool related logos you like? > > happy about any comments/feedback as i feel a bit overwhelmed :) > > best, > holger > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From holger at merlinux.eu Tue May 20 10:12:30 2014 From: holger at merlinux.eu (holger krekel) Date: Tue, 20 May 2014 08:12:30 +0000 Subject: [pytest-dev] pytest logo previews / please check drafts out Message-ID: <20140520081230.GX1895@merlinux.eu> Hi all, The competition for the new pytest logo has one week to go and we can feedback to designers. See here for current design drafts: http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ My current favorites are #4 and #5 but i also like a few others. Any comments/feedback welcome. best, holger From haraldarminmassa at gmail.com Tue May 20 10:43:05 2014 From: haraldarminmassa at gmail.com (Harald Armin Massa[legacy]) Date: Tue, 20 May 2014 10:43:05 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520081230.GX1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> Message-ID: Hi, I do not understand the panflute-motive that is dominating the designs. Can somebody please enlighten the LightningTalkMan? While enlightning: what ist the reason behind the first "P" of Pytest a capital letter, as for me pytesting something has more a "function", "method" appeal than a "Class"-appeal. >From the designs I favour #10; from #4 and #5 I would be more found of #5; with the panflute only having one and a half family of colours. I think putting a claim ("helps you...") into a logo is a challenge - it is allways hard to keep that claim readable in various scalings. Anyway, #4 and #5 would surely also work without the claim :) Harald 2014-05-20 10:12 GMT+02:00 holger krekel : > Hi all, > > The competition for the new pytest logo has one week to go and we > can feedback to designers. See here for current design drafts: > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > My current favorites are #4 and #5 but i also like a few others. > Any comments/feedback welcome. > > best, > holger > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev -- LightningTalkMan a brand of GHUM GmbH Spielberger Stra?e 49 70435 Stuttgart 0173/9409607 From holger at merlinux.eu Tue May 20 10:50:08 2014 From: holger at merlinux.eu (holger krekel) Date: Tue, 20 May 2014 08:50:08 +0000 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: References: <20140520081230.GX1895@merlinux.eu> Message-ID: <20140520085008.GY1895@merlinux.eu> Hi Harald, On Tue, May 20, 2014 at 10:43 +0200, Harald Armin Massa[legacy] wrote: > Hi, > > I do not understand the panflute-motive that is dominating the > designs. Can somebody please enlighten the LightningTalkMan? Tarek came up with the idea and i liked it: testing in python has an inofficial mascott: the testing goat. And a shepherd who takes care of the flock uses a pan flute. Pan is the "the god of the wild, shepherds and flocks, nature of mountain wilds ..." according to Wikipedia. That's roughly the background. > While enlightning: what ist the reason behind the first "P" of Pytest > a capital letter, as for me pytesting something has more a "function", > "method" appeal than a "Class"-appeal. I already fed back that i'd like to have this lower case. > >From the designs I favour #10; from #4 and #5 I would be more found of > #5; with the panflute only having one and a half family of colours. You mean the panflute itself should only have one color? I like the multi-colors ... > I think putting a claim ("helps you...") into a logo is a challenge - > it is allways hard to keep that claim readable in various scalings. > Anyway, #4 and #5 would surely also work without the claim :) Yes, the logo needs to work without the claim but it's also nice if it works with it - we could change the entry page of pytest.org to make it fit i guess. best, holger > Harald > > > > > 2014-05-20 10:12 GMT+02:00 holger krekel : > > Hi all, > > > > The competition for the new pytest logo has one week to go and we > > can feedback to designers. See here for current design drafts: > > > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > > > My current favorites are #4 and #5 but i also like a few others. > > Any comments/feedback welcome. > > > > best, > > holger > > > > _______________________________________________ > > Pytest-dev mailing list > > Pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > -- > LightningTalkMan > a brand of GHUM GmbH > Spielberger Stra?e 49 > 70435 Stuttgart > 0173/9409607 > From haraldarminmassa at gmail.com Tue May 20 11:06:40 2014 From: haraldarminmassa at gmail.com (Harald Armin Massa[legacy]) Date: Tue, 20 May 2014 11:06:40 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520085008.GY1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> <20140520085008.GY1895@merlinux.eu> Message-ID: > Tarek came up with the idea and i liked it: testing in python > has an inofficial mascott: the testing goat. And a shepherd > who takes care of the flock uses a pan flute. Pan is the > "the god of the wild, shepherds and flocks, nature of mountain wilds ..." > according to Wikipedia. That's roughly the background. That is a great story. Have you published it ? And would you please share the story behind the testing goat? >> While enlightning: what ist the reason behind the first "P" of Pytest >> a capital letter, as for me pytesting something has more a "function", >> "method" appeal than a "Class"-appeal. > I already fed back that i'd like to have this lower case. excellent! maybe also adjust the mailinglist-name from Pytest-* to pytest-*, to have a unified branding? >> >From the designs I favour #10; from #4 and #5 I would be more found of >> #5; with the panflute only having one and a half family of colours. > You mean the panflute itself should only have one color? "1 1/2 family of colours" (which is in #5, where there is the red and yellow family)... having it in all colours brings challenges if you want to use that logo on any other background than black or white. As in having goat-brown-t-shirts or mugs :) And reproduction can get less colours wrong :) > Yes, the logo needs to work without the claim but it's also nice > if it works with it - we could change the entry page of pytest.org > to make it fit i guess. Absolutely! Especially if you adjust the claim later on, when pytest is adapted to do control cell-culture-based testing of anti-cancer medicine. Harald -- LightningTalkMan a brand of GHUM GmbH Spielberger Stra?e 49 70435 Stuttgart 0173/9409607 From brianna.laugher at gmail.com Tue May 20 11:10:19 2014 From: brianna.laugher at gmail.com (Brianna Laugher) Date: Tue, 20 May 2014 19:10:19 +1000 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520085008.GY1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> <20140520085008.GY1895@merlinux.eu> Message-ID: Woohoo bikeshedding! :) Some of the very stylised flutes kind of look like charts, where you could imagine your test coverage increasing over time - I like that. Although they are kind of the wrong way around. But! I also really like #16, which has the old-school feel similar to the Flask logo. (Maybe just a different font for the name?) And it has the dots, which are like watching your passing tests fly by. For the flatter style, #4 and #5 are nice. Bordering on boring though. :) If we use a coloured one, I like the idea in #20-23 that "py" is coloured differently to "test". cheers Brianna On 20 May 2014 18:50, holger krekel wrote: > Hi Harald, > > On Tue, May 20, 2014 at 10:43 +0200, Harald Armin Massa[legacy] wrote: > > Hi, > > > > I do not understand the panflute-motive that is dominating the > > designs. Can somebody please enlighten the LightningTalkMan? > > Tarek came up with the idea and i liked it: testing in python > has an inofficial mascott: the testing goat. And a shepherd > who takes care of the flock uses a pan flute. Pan is the > "the god of the wild, shepherds and flocks, nature of mountain wilds ..." > according to Wikipedia. That's roughly the background. > > > While enlightning: what ist the reason behind the first "P" of Pytest > > a capital letter, as for me pytesting something has more a "function", > > "method" appeal than a "Class"-appeal. > > I already fed back that i'd like to have this lower case. > > > >From the designs I favour #10; from #4 and #5 I would be more found of > > #5; with the panflute only having one and a half family of colours. > > You mean the panflute itself should only have one color? > I like the multi-colors ... > > > I think putting a claim ("helps you...") into a logo is a challenge - > > it is allways hard to keep that claim readable in various scalings. > > Anyway, #4 and #5 would surely also work without the claim :) > > Yes, the logo needs to work without the claim but it's also nice > if it works with it - we could change the entry page of pytest.org > to make it fit i guess. > > best, > holger > > > Harald > > > > > > > > > > 2014-05-20 10:12 GMT+02:00 holger krekel : > > > Hi all, > > > > > > The competition for the new pytest logo has one week to go and we > > > can feedback to designers. See here for current design drafts: > > > > > > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > > > > > My current favorites are #4 and #5 but i also like a few others. > > > Any comments/feedback welcome. > > > > > > best, > > > holger > > > > > > _______________________________________________ > > > Pytest-dev mailing list > > > Pytest-dev at python.org > > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > > > > -- > > LightningTalkMan > > a brand of GHUM GmbH > > Spielberger Stra?e 49 > > 70435 Stuttgart > > 0173/9409607 > > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From anthon at mnt.org Tue May 20 12:10:32 2014 From: anthon at mnt.org (Anthon van der Neut) Date: Tue, 20 May 2014 12:10:32 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520081230.GX1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> Message-ID: <537B2A18.5030900@mnt.org> Nr 4 has my preference The graphic from that one (without the text) also makes a usable and recognisable icon (for desktop, website favicon.ico etc). #5 has the same advantage but makes it too much of an Ubuntu color scheme clone. Several others are Pleasing as well, but don't have the iconifiable (?) advantage of #4. On 2014-05-20 10:12, holger krekel wrote: > Hi all, > > The competition for the new pytest logo has one week to go and we > can feedback to designers. See here for current design drafts: > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > My current favorites are #4 and #5 but i also like a few others. > Any comments/feedback welcome. > > best, > holger > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From bubenkoff at gmail.com Tue May 20 10:18:45 2014 From: bubenkoff at gmail.com (Anatoly Bubenkov) Date: Tue, 20 May 2014 10:18:45 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520081230.GX1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> Message-ID: commented on 8 On 20 May 2014 10:12, holger krekel wrote: > Hi all, > > The competition for the new pytest logo has one week to go and we > can feedback to designers. See here for current design drafts: > > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > My current favorites are #4 and #5 but i also like a few others. > Any comments/feedback welcome. > > best, > holger > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -- Anatoly Bubenkov -------------- next part -------------- An HTML attachment was scrubbed... URL: From tarek at ziade.org Tue May 20 11:25:46 2014 From: tarek at ziade.org (=?ISO-8859-1?Q?Tarek_Ziad=E9?=) Date: Tue, 20 May 2014 11:25:46 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520081230.GX1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> Message-ID: <537B1F9A.3000304@ziade.org> Le 20/05/14 10:12, holger krekel a ?crit : > Hi all, > > The competition for the new pytest logo has one week to go and we > can feedback to designers. See here for current design drafts: > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > My current favorites are #4 and #5 but i also like a few others. > Any comments/feedback welcome. > > best, > holger > I like #4 best - I wonder how it would look with another typo though. From lac at openend.se Tue May 20 15:18:19 2014 From: lac at openend.se (Laura Creighton) Date: Tue, 20 May 2014 15:18:19 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: Message from holger krekel of "Tue, 20 May 2014 08:12:30 -0000." <20140520081230.GX1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> Message-ID: <201405201318.s4KDIJ9r010325@fido.openend.se> In a message of Tue, 20 May 2014 08:12:30 -0000, holger krekel writes: >Hi all, > >The competition for the new pytest logo has one week to go and we >can feedback to designers. See here for current design drafts: > >http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > >My current favorites are #4 and #5 but i also like a few others. >Any comments/feedback welcome. > >best, >holger For what is it worth ... I'd like the image in #4 and #5 the best, but would like it better if the pipes were colour coded the way errors/skips are in pytest. The other images mostly do not look 'simple' or 'elegant' enough for my taste. I like the effect of having 'py' in one colour and 'test' in another, as the same artist who did #4 and #5 did in #3. But I would prefer if 'pytest' were all lower case. Laura From holger at merlinux.eu Tue May 20 15:42:18 2014 From: holger at merlinux.eu (holger krekel) Date: Tue, 20 May 2014 13:42:18 +0000 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <537B1F9A.3000304@ziade.org> References: <20140520081230.GX1895@merlinux.eu> <537B1F9A.3000304@ziade.org> Message-ID: <20140520134218.GB1895@merlinux.eu> On Tue, May 20, 2014 at 11:25 +0200, Tarek Ziad? wrote: > Le 20/05/14 10:12, holger krekel a ?crit : > > Hi all, > > > > The competition for the new pytest logo has one week to go and we > > can feedback to designers. See here for current design drafts: > > > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > > > My current favorites are #4 and #5 but i also like a few others. > > Any comments/feedback welcome. > > > best, > > holger > > > I like #4 best - I wonder how it would look with another typo though. There are a few new ones from the some person #29-#32 reacting to your suggestions (which i relayed). holger From holger at merlinux.eu Tue May 20 15:46:26 2014 From: holger at merlinux.eu (holger krekel) Date: Tue, 20 May 2014 13:46:26 +0000 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <201405201318.s4KDIJ9r010325@fido.openend.se> References: <20140520081230.GX1895@merlinux.eu> <201405201318.s4KDIJ9r010325@fido.openend.se> Message-ID: <20140520134626.GC1895@merlinux.eu> Hey Laura, On Tue, May 20, 2014 at 15:18 +0200, Laura Creighton wrote: > In a message of Tue, 20 May 2014 08:12:30 -0000, holger krekel writes: > >Hi all, > > > >The competition for the new pytest logo has one week to go and we > >can feedback to designers. See here for current design drafts: > > > >http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ > > > >My current favorites are #4 and #5 but i also like a few others. > >Any comments/feedback welcome. > > > >best, > >holger > > For what is it worth ... thanks, it is valuable to me! And nice to hear form you. > I'd like the image in #4 and #5 the best, but would like it better if the > pipes were colour coded the way errors/skips are in pytest. The other > images mostly do not look 'simple' or 'elegant' enough for my taste. > > I like the effect of having 'py' in one colour and 'test' in another, as > the same artist who did #4 and #5 did in #3. But I would prefer if > 'pytest' were all lower case. Just also mailed to Tarek, designs #29-#32 go in this direction i think. With pytest runs we use red/yellow these days (although mostly red). Apart from the foreground color which might be black or white. I do like the blue from the "vgroup" designs although pytest is not using it (yet? :). best, holger > Laura > From tarek at ziade.org Tue May 20 15:49:33 2014 From: tarek at ziade.org (=?ISO-8859-1?Q?Tarek_Ziad=E9?=) Date: Tue, 20 May 2014 15:49:33 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520134218.GB1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> <537B1F9A.3000304@ziade.org> <20140520134218.GB1895@merlinux.eu> Message-ID: <537B5D6D.1080909@ziade.org> Le 20/05/14 15:42, holger krekel a ?crit : > On Tue, May 20, 2014 at 11:25 +0200, Tarek Ziad? wrote: >> Le 20/05/14 10:12, holger krekel a ?crit : >>> Hi all, >>> >>> The competition for the new pytest logo has one week to go and we >>> can feedback to designers. See here for current design drafts: >>> >>> http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ >>> >>> My current favorites are #4 and #5 but i also like a few others. >>> Any comments/feedback welcome. >>> best, >>> holger >>> >> I like #4 best - I wonder how it would look with another typo though. > > There are a few new ones from the some person #29-#32 reacting to > your suggestions (which i relayed). > > holger #32 is now my favorite. The only thing to fix imo is the color of "helps you write better programs" If you back off your screen a little bit, it's very hard to read because it's too clear and I am pretty sure it will be the same on shirts. I would go with a black text there. but overall it's a very nice logo! Cheers Tarek From lac at openend.se Tue May 20 16:05:21 2014 From: lac at openend.se (Laura Creighton) Date: Tue, 20 May 2014 16:05:21 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: Message from holger krekel of "Tue, 20 May 2014 13:46:26 -0000." <20140520134626.GC1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> <201405201318.s4KDIJ9r010325@fido.openend.se><20140520134626.GC1895@merlinux.eu> Message-ID: <201405201405.s4KE5LkG011462@fido.openend.se> I like 31 the best now, then 29. I don't like the 'dark to light shading effect in 32'. And the 'helps you write better programs' -- I don't think that this is particularly apt or useful slogan for pytest, whose strengths I thought were simplicity, and readability -- so I would not be surprised if we changed it over time. As in as soon as somebody who is good at coming up with slogans -- I am particularly dreadful at it -- comes up with the pithy phrase. So as long as we have room to change, I would not worry about it too much. What is desirable in colour choice for text varies depending on size, and the materials that the printing is being done in -- so as long as it is always possible to get dark grey, which in some cases is the only thing that reads well, I think we will be in great shape. Laura From marc.schlaich at gmail.com Tue May 20 17:28:27 2014 From: marc.schlaich at gmail.com (Marc Schlaich) Date: Tue, 20 May 2014 17:28:27 +0200 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <201405201405.s4KE5LkG011462@fido.openend.se> References: <20140520081230.GX1895@merlinux.eu> <201405201318.s4KDIJ9r010325@fido.openend.se> <20140520134626.GC1895@merlinux.eu> <201405201405.s4KE5LkG011462@fido.openend.se> Message-ID: Me too, #31 is really nice. On Tue, May 20, 2014 at 4:05 PM, Laura Creighton wrote: > I like 31 the best now, then 29. I don't like the 'dark to light shading > effect in 32'. And the 'helps you write better programs' -- I don't think > that this is particularly apt or useful slogan for pytest, whose strengths > I thought were simplicity, and readability -- so I would not > be surprised if we changed it over time. As in as soon as somebody who > is good at coming up with slogans -- I am particularly dreadful at it -- > comes up with the pithy phrase. So as long as we have room to change, I > would not worry about it too much. > > What is desirable in colour choice for text varies depending on size, > and the materials that the printing is being done in -- so as long as > it is always possible to get dark grey, which in some cases is the > only thing that reads well, I think we will be in great shape. > > Laura > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From digitalxero at gmail.com Tue May 20 19:18:08 2014 From: digitalxero at gmail.com (Dj Gilcrease) Date: Tue, 20 May 2014 10:18:08 -0700 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: References: <20140520081230.GX1895@merlinux.eu> <201405201318.s4KDIJ9r010325@fido.openend.se> <20140520134626.GC1895@merlinux.eu> <201405201405.s4KE5LkG011462@fido.openend.se> Message-ID: I added #38 as a concept, I am not an artist and I have no interest in the prize money, but if someone wants to take the concept of the Y being the Pan Flute and run with it feel free. Dj Gilcrease ____ ( | \ o () | o |`| | | /`\_/| | | ,__ ,_, ,_, __, , ,_, _| | | / | | |/ / / | |_/ / | / \_|_/ (/\___/ |/ /(__,/ |_/|__/\___/ |_/|__/\__/|_/\,/ |__/ /| \| On Tue, May 20, 2014 at 8:28 AM, Marc Schlaich wrote: > Me too, #31 is really nice. > > > On Tue, May 20, 2014 at 4:05 PM, Laura Creighton wrote: > >> I like 31 the best now, then 29. I don't like the 'dark to light shading >> effect in 32'. And the 'helps you write better programs' -- I don't think >> that this is particularly apt or useful slogan for pytest, whose strengths >> I thought were simplicity, and readability -- so I would not >> be surprised if we changed it over time. As in as soon as somebody who >> is good at coming up with slogans -- I am particularly dreadful at it -- >> comes up with the pithy phrase. So as long as we have room to change, I >> would not worry about it too much. >> >> What is desirable in colour choice for text varies depending on size, >> and the materials that the printing is being done in -- so as long as >> it is always possible to get dark grey, which in some cases is the >> only thing that reads well, I think we will be in great shape. >> >> Laura >> _______________________________________________ >> Pytest-dev mailing list >> Pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Fri May 23 21:50:18 2014 From: flub at devork.be (Floris Bruynooghe) Date: Fri, 23 May 2014 20:50:18 +0100 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: References: <20140520081230.GX1895@merlinux.eu> <201405201318.s4KDIJ9r010325@fido.openend.se> <20140520134626.GC1895@merlinux.eu> <201405201405.s4KE5LkG011462@fido.openend.se> Message-ID: FWIW I quite like #37 which adds black & white variations to #31 which already seems popular. On 20 May 2014 18:18, Dj Gilcrease wrote: > I added #38 as a concept, I am not an artist and I have no interest in the > prize money, but if someone wants to take the concept of the Y being the Pan > Flute and run with it feel free. > > > > Dj Gilcrease > ____ > ( | \ o () | o |`| > | | /`\_/| | | ,__ ,_, ,_, __, , ,_, > _| | | / | | |/ / / | |_/ / | / \_|_/ > (/\___/ |/ /(__,/ |_/|__/\___/ |_/|__/\__/|_/\,/ |__/ > /| > \| > > > On Tue, May 20, 2014 at 8:28 AM, Marc Schlaich > wrote: >> >> Me too, #31 is really nice. >> >> >> On Tue, May 20, 2014 at 4:05 PM, Laura Creighton wrote: >>> >>> I like 31 the best now, then 29. I don't like the 'dark to light shading >>> effect in 32'. And the 'helps you write better programs' -- I don't >>> think >>> that this is particularly apt or useful slogan for pytest, whose >>> strengths >>> I thought were simplicity, and readability -- so I would not >>> be surprised if we changed it over time. As in as soon as somebody who >>> is good at coming up with slogans -- I am particularly dreadful at it -- >>> comes up with the pithy phrase. So as long as we have room to change, I >>> would not worry about it too much. >>> >>> What is desirable in colour choice for text varies depending on size, >>> and the materials that the printing is being done in -- so as long as >>> it is always possible to get dark grey, which in some cases is the >>> only thing that reads well, I think we will be in great shape. >>> >>> Laura >>> _______________________________________________ >>> Pytest-dev mailing list >>> Pytest-dev at python.org >>> https://mail.python.org/mailman/listinfo/pytest-dev >> >> >> >> _______________________________________________ >> Pytest-dev mailing list >> Pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org From stephan.obermann at dolby.com Fri May 23 23:15:04 2014 From: stephan.obermann at dolby.com (Obermann, Stephan) Date: Fri, 23 May 2014 21:15:04 +0000 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <20140520081230.GX1895@merlinux.eu> References: <20140520081230.GX1895@merlinux.eu> Message-ID: <9CB4A0F69E145D4A95944FB16DD4D6A534684F2A@DLB-XCHPW01.dolby.net> #37 (black on white ground) looks nice - simple and elegant. /stephan On [21] 2014-05-20 10:12 , "holger krekel" wrote: >Hi all, > >The competition for the new pytest logo has one week to go and we >can feedback to designers. See here for current design drafts: > >http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a- >tool-for-testing-computer-software/ > >My current favorites are #4 and #5 but i also like a few others. >Any comments/feedback welcome. > >best, >holger > >_______________________________________________ >Pytest-dev mailing list >Pytest-dev at python.org >https://mail.python.org/mailman/listinfo/pytest-dev From lahwran0 at gmail.com Tue May 27 03:53:49 2014 From: lahwran0 at gmail.com (lahwran) Date: Mon, 26 May 2014 19:53:49 -0600 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: <9CB4A0F69E145D4A95944FB16DD4D6A534684F2A@DLB-XCHPW01.dolby.net> References: <20140520081230.GX1895@merlinux.eu> <9CB4A0F69E145D4A95944FB16DD4D6A534684F2A@DLB-XCHPW01.dolby.net> Message-ID: I love, love #37's flexibility - it doesn't need color to work, but has color to be used. It could be used to set the color scheme on the website. It's also very simple and modern, which I feel like is the thing I like about py.test. -- lahwran On Fri, May 23, 2014 at 3:15 PM, Obermann, Stephan < stephan.obermann at dolby.com> wrote: > #37 (black on white ground) looks nice - simple and elegant. > > /stephan > > > On [21] 2014-05-20 10:12 , "holger krekel" wrote: > > >Hi all, > > > >The competition for the new pytest logo has one week to go and we > >can feedback to designers. See here for current design drafts: > > > > > http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a- > >tool-for-testing-computer-software/ > > > >My current favorites are #4 and #5 but i also like a few others. > >Any comments/feedback welcome. > > > >best, > >holger > > > >_______________________________________________ > >Pytest-dev mailing list > >Pytest-dev at python.org > >https://mail.python.org/mailman/listinfo/pytest-dev > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Tue May 27 16:53:59 2014 From: holger at merlinux.eu (holger krekel) Date: Tue, 27 May 2014 14:53:59 +0000 Subject: [pytest-dev] pytest logo previews / please check drafts out In-Reply-To: References: <20140520081230.GX1895@merlinux.eu> <201405201318.s4KDIJ9r010325@fido.openend.se> <20140520134626.GC1895@merlinux.eu> <201405201405.s4KE5LkG011462@fido.openend.se> Message-ID: <20140527145359.GA1895@merlinux.eu> On Tue, May 20, 2014 at 10:18 -0700, Dj Gilcrease wrote: > I added #38 as a concept, I am not an artist and I have no interest in the > prize money, but if someone wants to take the concept of the Y being the > Pan Flute and run with it feel free. thanks for chiming in and helping! holger > > > Dj Gilcrease > ____ > ( | \ o () | o |`| > | | /`\_/| | | ,__ ,_, ,_, __, , ,_, > _| | | / | | |/ / / | |_/ / | / \_|_/ > (/\___/ |/ /(__,/ |_/|__/\___/ |_/|__/\__/|_/\,/ |__/ > /| > \| > > > On Tue, May 20, 2014 at 8:28 AM, Marc Schlaich wrote: > > > Me too, #31 is really nice. > > > > > > On Tue, May 20, 2014 at 4:05 PM, Laura Creighton wrote: > > > >> I like 31 the best now, then 29. I don't like the 'dark to light shading > >> effect in 32'. And the 'helps you write better programs' -- I don't think > >> that this is particularly apt or useful slogan for pytest, whose strengths > >> I thought were simplicity, and readability -- so I would not > >> be surprised if we changed it over time. As in as soon as somebody who > >> is good at coming up with slogans -- I am particularly dreadful at it -- > >> comes up with the pithy phrase. So as long as we have room to change, I > >> would not worry about it too much. > >> > >> What is desirable in colour choice for text varies depending on size, > >> and the materials that the printing is being done in -- so as long as > >> it is always possible to get dark grey, which in some cases is the > >> only thing that reads well, I think we will be in great shape. > >> > >> Laura > >> _______________________________________________ > >> Pytest-dev mailing list > >> Pytest-dev at python.org > >> https://mail.python.org/mailman/listinfo/pytest-dev > >> > > > > > > _______________________________________________ > > Pytest-dev mailing list > > Pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > _______________________________________________ > Pytest-dev mailing list > Pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From holger at merlinux.eu Tue May 27 16:55:07 2014 From: holger at merlinux.eu (holger krekel) Date: Tue, 27 May 2014 14:55:07 +0000 Subject: [pytest-dev] final logo selection tomorrow morning Message-ID: <20140527145507.GB1895@merlinux.eu> Hi all, thanks for everyone who gave feedback. I plan to close the pytest logo contest tomorrow morning. My favorite remains #47, although a few recent additions also have some interesting aspects. I also asked the author to provide a b/w and w/b version as in #47. See here for all designs: http://www.12designer.com/en/project/11977/details/Logo-logo-design-for-a-tool-for-testing-computer-software/ if you have anything to add or comment, please let me know and quickly :) best, holger