| Description |
1 online resource (1 video file (59 min.)) : sound, color |
| Summary |
Ideas like TDD, BDD and Continuous Delivery are great, but how do you introduce them to legacy systems? Practically, hands-on, how do you change legacy-code to make it testable? When Kent Beck wrote about TDD he introduced a profoundly valuable engineering practice to software development. In his book " Working Effectively with Legacy Code" Michael Feathers defines a legacy system as "a system without automated tests". So how can we take advantage of the benefits of TDD when our code is the wrong shape, when it was developed without automated tests? In this 3-part Video Course. Dave demonstrates his preferred "Four Steps to Refactoring, Approval Testing and De-cluttering", applies them to some very nasty code: making it testable and discovering some surprising things along the way. What you'll learn and how you can apply it How to change legacy-code safely, in small steps, to make it testable. Using Approval testing to ensure changes are safe. Understand a four-step process to guide refactoring in even complex code. This course is for you because... You're a programmer interested in learning how to refactor legacy code so that it is testable. You're looking to introduce TDD, BDD and Continuous Delivery to legacy systems. You want to become more proficient at working with legacy code and improving your code base. Prerequisites: Writing code in one language Basic software developer skills Some knowledge of TDD and testing is helpful |
| Performer |
David Farley, presenter |
| Notes |
Online resource; title from title details screen (O'Reilly, viewed August 14, 2023) |
| Subject |
Software refactoring.
|
|
Software refactoring.
|
| Genre/Form |
Instructional films.
|
|
Internet videos.
|
|
Nonfiction films.
|
|
Instructional films.
|
|
Nonfiction films.
|
|
Internet videos.
|
|
Films de formation.
|
|
Films autres que de fiction.
|
|
Vidéos sur Internet.
|
| Form |
Streaming video
|
| Author |
Farley, David, presenter
|
|
O'Reilly (Firm), publisher.
|
|
