Mashing up py.test, coverage.py and ast.py to take TDD to a new level
Formal Metadata
| Title | Mashing up py.test, coverage.py and ast.py to take TDD to a new level |
|
| Title of Series | |
| Part Number | 18 |
| Number of Parts | 173 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Bilbao, Euskadi, Spain |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Tibor Arpas - Mashing up py.test, coverage.py and ast.py to take TDD to a new level
Users and developers especially, hate waiting. Computing has adapted
and we almost never wait for the computer for more then 10 seconds.
One big exception is runnig a test suite which takes MINUTES on many
projects. That is incredibly distracting, frustrating and dragging the
whole concept of automated tests down.
I present a technique and a tool (py.test plugin called "testmon")
which automatically selects only tests affected by recent changes.
Does it sound too good to be true? Python developers rightfully have a
suspecting attitude towards any tool which tries to be too clever
about their source code. Code completion and symbol searching doesn't
need to be 100% reliable but messing with the test suite execution? I
show that we can cut test suite execution time significantly but
maintain it's reliability. |
|
| Keywords | |
