Mailman 3 May 2014 - pytest-dev

final logo selection tomorrow morning
by holger krekel May 27, 2014

May 27, 2014

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-t… if you have anything to add or comment, please let me know and quickly :) best, holger

1 0

Re: [pytest-dev] pytest logo previews / please check drafts out
by Laura Creighton May 27, 2014

May 27, 2014

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

5 4

pytest logo previews / please check drafts out
by holger krekel May 27, 2014

May 27, 2014

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-t… My current favorites are #4 and #5 but i also like a few others. Any comments/feedback welcome. best, holger

8 11

Re: [pytest-dev] pytest logo previews / please check drafts out
by Laura Creighton May 20, 2014

May 20, 2014

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-t… > >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

2 1

pytest logo / comments welcome
by holger krekel May 15, 2014

May 15, 2014

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

5 6

Using Pytest 2.5.2 to Automate Testing of a Non-Python Application
by Peter May 1, 2014

May 1, 2014

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

1 0