Writing Characterization Tests Before Refactoring
You cannot safely refactor untested legacy code. This lesson teaches characterization testing: capturing the current behavior of legacy Objective-C so refactors preserve it.
Writing Characterization Tests Before Refactoring is a free Objective-C iOS Development for Legacy & Enterprise Apps lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Objective-C iOS Development for Legacy & Enterprise Apps learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
The Refactoring Dilemma
Refactoring should not change behavior, but legacy code often has no tests proving what its behavior even is. Characterization tests solve this.
What Is a Characterization Test
A characterization test documents the code as it actually behaves, not as it should behave. It pins current output so any change becomes visible.
Find a Seam
A seam is a place you can call into the code without running the whole app. Public methods on a class are the easiest seams.
@interface PriceCalculator : NSObject
- (NSDecimalNumber *)totalForItems:(NSArray *)items
withTax:(double)taxRate;
@endCapture Current Output
Call the method with known inputs and record whatever it returns today, even if it looks wrong.
// Run once, observe, then assert the observed value
NSDecimalNumber *result = [calc totalForItems:items withTax:0.1];
NSLog(@"observed: %@", result); // -> 22.00Pin It With an Assertion
Turn the observed value into an assertion. This test now fails if behavior changes.
- (void)testTotalCharacterization {
NSDecimalNumber *r = [calc totalForItems:items withTax:0.1];
XCTAssertEqualObjects(r, [NSDecimalNumber decimalNumberWithString:@"22.00"]);
}Cover the Edge Cases
Add tests for empty input, zero tax, and large values. The goal is to surround the code so the refactor has a safety net.
Breaking Dependencies
If a method touches the network or disk, introduce a protocol seam and inject a fake so the test is fast and deterministic.
@protocol PriceFeed <NSObject>
- (double)currentRate;
@end
// Inject a fake PriceFeed in the testRefactor Under Green
With tests green, refactor in small steps, re-running tests after each change. Any red means you changed behavior and must reconsider.
Distinguish Bug From Behavior
A characterization test may pin a bug. That is fine: first preserve it, then fix it as a separate, deliberate change with its own test.
Delete When Replaced
Once proper unit tests describe the desired behavior, you can retire characterization tests that merely pinned legacy quirks.
Build the Net Incrementally
You do not need full coverage at once. Add characterization tests only around the code you are about to touch; the net grows as you refactor.
Quick Check
Test your characterization testing knowledge.
Recap
You learned to find seams, capture and pin current behavior, break dependencies with protocols, refactor under green, and grow a test net incrementally around legacy Objective-C.
Frequently asked questions
Is the “Writing Characterization Tests Before Refactoring” lesson free?
Yes — the full text of “Writing Characterization Tests Before Refactoring” is free to read here on the web, and the Objective-C iOS Development for Legacy & Enterprise Apps course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Objective-C iOS Development for Legacy & Enterprise Apps course, upgrade to CoddyKit PRO.
What will I learn in “Writing Characterization Tests Before Refactoring”?
You cannot safely refactor untested legacy code. This lesson teaches characterization testing: capturing the current behavior of legacy Objective-C so refactors preserve it. You practise Objective-C iOS Development for Legacy & Enterprise Apps with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Objective-C iOS Development for Legacy & Enterprise Apps?
No prior experience is required. Objective-C iOS Development for Legacy & Enterprise Apps on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Writing Characterization Tests Before Refactoring” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Objective-C iOS Development for Legacy & Enterprise Apps lesson?
Yes. Every Objective-C iOS Development for Legacy & Enterprise Apps lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Refactoring Legacy Objective-C
- Managing Technical Debt
- Long-Term Maintenance Strategies
- Writing Characterization Tests Before Refactoring