Adding Unit Test To Legacy Code
Upcoming SlideShare
Loading in...5
×
 

Adding Unit Test To Legacy Code

on

  • 1,438 views

Some experience sharing about adding unit test to legacy code in large embedded system.

Some experience sharing about adding unit test to legacy code in large embedded system.

Statistics

Views

Total Views
1,438
Views on SlideShare
1,433
Embed Views
5

Actions

Likes
3
Downloads
18
Comments
0

2 Embeds 5

http://www.linkedin.com 4
http://coderwall.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Adding Unit Test To Legacy Code Adding Unit Test To Legacy Code Presentation Transcript

  • terry.yinzhe@gmail.com
  • Agenda Background Motivation Principles Practices What is fun?
  • BACKGROUND
  • Large scale softwareTelecommunication device10+ years old1,000 people10,000,000 lines of code in one buildC, SDLSome very complicatedThousands LOCs functionsCyclomatic complexity > 50.Duplicate rate > 100%!
  • Where do we usually call it legacy code?
  • MOTIVATION
  • Its NOT about finding bugs!The purpose of unit testing is to facilitatechanges
  • You still have the choice and reasons not to do it.
  • PRINCIPLES
  • BASIC UNIT TESTINGPRINCIPLES
  • PRINCIPLE 1KEEP IT VERY SIMPLE, VERY STUPID It is not that the more test cases the better Actually, it is on the contrary, the less the better. The purpose of UT is to facilitate change It can only facilitate change if it survive Therefore, it needs maintainability So, it needs to be simple "The only way for humans to deal with complexity is to avoid it ..."
  • PRINCIPLE 2DONT TRY TO ADD GOOD UT TO BAD CODE
  • PRINCIPLE 3DONT MAKE ASSUMPTION Exploding stub error_t release_message_received( msg_header_t * msg ) { DO_FAIL_TEXT("Im called!!"); return SUCCESS_EC; }
  • PRINCIPLE 4STOP MAKING LEGACY CODE Test drive new code Add tests to legacy code before modification Test drive changes to legacy code Boy Scout Principle
  • PRINCIPLE 5EDUCATE THE PEOPLE Do NOT let just one or two people do it. NEVER let interns do it!
  • WHERE TO START?
  • Setup the framework To setup the framework for legacy code can be very challenging. Choose the test framework We use CppUTest Ask for performance
  • Domain Modeling Reverse engineering to clarify the concepts used in the legacy code And their relationships Use the terms consistently in your unit testing. It will also give your refactoring a road-map.
  • Identify the hot area Start from the hot area will be most cost-efficient Example Through SVN log Along with the new work and bug fixing
  • Bottom-up? Have some integration test first Then, One practical approach is bottom-up Get a higher level of abstraction
  • Learn the function by testing it Characterization Test Start from the 1st (failing) exit Write your plan on a piece of paper
  • Make the legacy code testable Use safe refactoring techniques to change the legacy code without unit testing. Extract function If you are using C ‘Data injection’ to break the dependency on globals.
  • Break Dependency
  • WHAT IS FUN
  • Bring chaos to orderLearn the featureDelete tons of codeFeel the peace of your heart
  • REFERENCES
  • Acknowledgement