Sustainable way of testing your code
Formal Metadata
| Title | Sustainable way of testing your code |
|
| Title of Series | |
| Part Number | 64 |
| Number of Parts | 173 |
| Author | |
| License | CC Attribution - NonCommercial - ShareAlike 3.0 Unported: 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 | Eugene Amirov - Sustainable way of testing your code
How to write a test so you would remember what it does in a year from
now? How to write selective tests with different inputs? What is test?
How to subclass tests cases and yet maintain control on which tests
would run? How to extend or to filter inputs used in parent classes?
Are you a tiny bit intrigued now? :)
This is not another talk about how to test, but how to organize your
tests so they were maintainable. I will be using nose framework as an
example, however main ideas should be applicable to any other
framework you choose. Explaining how some parts of code works I would
have to briefly touch some advanced python topics, although I will
provide need-to-know basics there, so people with any level of python
knowledge could enjoy the ride. |
|
| Keywords | |