pytest has a long and interesting history. The first commit in this repository is from January 2007, and even that commit alone already tells a lot: The repository originally was from the py library (later split off to pytest), and it originally was a SVN revision, migrated to Mercurial, and finally migrated to git.
However, the commit says “create the new development trunk” and is already quite big: 435 files changed, 58640 insertions(+). This is because pytest originally was born as part of PyPy, to make it easier to write tests for it. Here’s how it evolved from there to its own project:
Late 2002 / early 2003, PyPy was born.
Like that blog post mentioned, from very early on, there was a big focus on testing. There were various
testsupportfiles on top of unittest.py, and as early as June 2003, Holger Krekel (@hpk42) refactored its test framework to clean things up (
pypy.tool.test, but still on top of
unittest.py, with nothing pytest-like yet).
In December 2003, there was another iteration at improving their testing situation, by Stefan Schwarzer, called
However, it didn’t seem to be around for long, as around June/July 2004, efforts started on a thing called
utest, offering plain assertions. This seems like the start of something pytest-like, but unfortunately, it’s unclear where the test runner’s code was at the time. The closest thing still around is this file, but that doesn’t seem like a complete test runner at all. What can be seen is that there were various efforts by Laura Creighton and Samuele Pedroni (@pedronis) at automatically converting existing tests to the new
Around the same time, for Europython 2004, @hpk42 started a project originally called “std”, intended to be a “complementary standard library” - already laying out the principles behind what later became pytest:
current “batteries included” are very useful, but
some of them are written in a pretty much java-like style, especially the unittest-framework
the best API is one that doesn’t exist
a testing package should require as few boilerplate code as possible and offer much flexibility
it should provide premium quality tracebacks and debugging aid
first of all … forget about limited “assertXYZ APIs” and use the real thing, e.g.:
assert x == y
this works with plain python but you get unhelpful “assertion failed” errors with no information
std.utest (magic!) actually reinterprets the assertion expression and offers detailed information about underlying values
In September 2004, the
py-devmailinglist gets born, which is now
pytest-dev, but thankfully with all the original archives still intact.
Around September/October 2004, the
stdproject was renamed to
py.test. This is also the first time the entire source code, seems to be available, with much of the API still being around today:
py.path.local, which is being phased out of pytest (in favour of pathlib) some 16-17 years later
The idea of the collection tree, including
In the same month, the
pylibrary gets split off from
It seemed to get rather quiet for a while, and little seemed to happen between October 2004 (removing
pyfrom PyPy) and January 2007 (first commit in the now-pytest repository). However, there were various discussions about features/ideas on the mailinglist, and a couple of releases every couple of months:
March 2006: py 0.8.0-alpha2
May 2007: py 0.9.0
March 2008: py 0.9.1 (first release to be found in the pytest changelog!)
August 2008: py 0.9.2
In August 2009, py 1.0.0 was released, introducing a lot of fundamental features:
Even back there, the FAQ said:
Clearly, [a second standard library] was ambitious and the naming has maybe haunted the project rather than helping it. There may be a project name change and possibly a split up into different projects sometime.
and that finally happened in November 2010, when pytest 2.0.0 was released as a package separate from
py(but still called
In August 2016, pytest 3.0.0 was released, which adds
py.test) as the recommended command-line entry point
Due to this history, it’s difficult to answer the question when pytest was started. It depends what point should really be seen as the start of it all. One possible interpretation is to pick Europython 2004, i.e. around June/July 2004.