Lessons learned about testing and TDD
Formal Metadata
| Title | Lessons learned about testing and TDD |
|
| Title of Series | |
| Part Number | 129 |
| 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 | Marco Buttu - Lessons learned about testing and TDD
One day our software will go in production, and so shortly we will pay
dearly for our youthful mistakes. Without regression tests, we will be
in deep trouble. If we have regression tests, but we did not have
performed TDD, we should probably increase the effort in bug fixing
and
maintenance, since we do not have enough code coverage and our tests
come out complex.
By retracing the author youthful mistakes, we will see a complete
development workflow, from the user story to the low-level tests, in
order to highlight the differences between functional, integration and
unit tests, the best practices, and the lessons learned by the author
during the development of the [Sardinia Radio Telescope] control
software. |
|
| Keywords | |