Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Kaunas Java User Group, profile picture
Uploaded byKaunas Java User Group
PPTX, PDF1,310 views

Bye Bye Cowboy Coder Days! (Legacy Code & TDD)

The document discusses the importance of changing software through various methods such as adding features, fixing bugs, and optimizing resource usage, emphasizing the need for unit tests. It outlines strategies for dealing with legacy code, including the sprout and wrap methods and the use of test-driven development (TDD) to ensure changes don't break existing functionality. Additionally, it promotes Agile practices and highlights upcoming Agile tours and master classes.

Technology◦
Downloaded 12 times
Bye Bye Cowboy-Coder days!
What do developers do for living? Change the code!
Four Reasons to Change Software • Adding a feature • Fixing a bug • Improving the design • Optimizing resource usage
Changing Software Adding a Feature Fixing a Bug Refactoring Optimizing Structure Changes Changes Changes New Changes Functionality Functionality Changes Resource Usage Changes
Preserving behavior Existing Behavior New Behavior
Risky Change 1. What changes do we have to make? 2. How will we know that we've done them correctly? 3. How will we know that we haven't broken anything?
How?
Working with Feedback! Yes, Unit Tests…
Few qualities of Unit Tests • They run fast • They help us localize problems
Dependencies… • No way to run separately • Takes time to load • Hard to localize problem
GUI Tests Integration Tests Unit Tests
GUI Tests Integration Tests Unit Tests
Lag Time Time to fix/Price 1 Minute 10 Minutes 1 Hour 1 Day 1 Week Time to fix/Price
The Legacy Code Dilemma When we change code, we should have tests in place. To put tests in place, we often have to change code.
The Legacy Code Change Algorithm 1. Identify change points 2. Find test points 3. Break dependencies 4. Write tests 5. Make changes and refactor
Sensing and Separation • We break dependencies to sense when we can't access values our code computes • We break dependencies to separate when we can't even get a piece of code into a test harness to run
Faking Collaborators • Fake Objects • Mock Objects • Nothing!
Sprout
Sprout Method 1. Identify where to change 2. Wdown a method call and then comment it out. 3. Determine what local variables you need for the call 4. Determine return value 5. Develop the sprout method using test-driven development 6. Remove the comment in the source method
Sprout Class 1. Identify where you need to make your code change. 2. Write class in that place, and call a method; then comment those lines out 3. Determine what local variables you need from the source method, and make them arguments to the classes' constructor 4. Determine return values to the source method and add a call in the source method to receive those values. 5. Develop the sprout class test first 6. Remove the comment in the source
Wrap
Wrap Method 1. Identify a method you need to change 2. If the change can be formulated as a single sequence of statements in one place, develop a new method for it using test-driven development 3. Create another method that calls the new method and the old method
Wrap Class 1. Identify a method where you need to make a change. 2. Create a class that accepts the class you are going to wrap as a constructor argument. 3. Create a method on that class, using test-driven development. 4. Write another method that calls the new method and the old method on the wrapped class 5. Instantiate the wrapper class in your code in the place where you need to enable the new behavior
TDD and Legacy Code 1. Get the class you want to change under test 2. Write a failing test case 3. Get it to compile 4. Make it pass (Try not to change existing code as you do this) 5. Remove duplication 6. Repeat
Allways check if tests are testing 1. Write test and new code in separate changelist 2. Shelve new code change list 3. Ensure tests are failing
Characterization Tests 1. Use a piece of code in a test harness 2. Write an assertion that you know will fail - let the failure tell you what the behavior is 3. Change the test so that it expects the behavior that the code produces 4. Repeat
I Can't Get This Class into a Test Harness • Lean on the Compiler • Extract Interface • Extract Implementer • Subclass and Override Method • Parameterize Constructor • Parameterize Method • Extract and Override Getter • Extract and Override Factory Method • Singleton Design Pattern
When All Else Fails, Do Some Scratch Refactoring
Questions?
Agile Turas Lietuvoje • Agile Tour Kaunas – rugsėjo 25 d. • Agile Tour Vilnius – spalio 9 d. • Agile Master Classes www.agileturas.lt
The World’s Best Intro to TDD • J. B. Rainsberger, Kanada • 2 Dienų mokymai, Kaune • Rugsėjo 23 - 24 d. www.agileturas.lt/master-classes