This document discusses frameworks and alternative approaches to object-oriented programming and testing. It argues that frameworks do a lot but alternatives like simple object orientation, inversion of control, and message-based testing can achieve similar results without as much complexity. An example is provided of testing account transactions without directly touching the account object by sending it messages in different scenarios and checking the outcomes. The document questions if frameworks are always needed and presents alternatives for developing and testing code through lighter-weight object practices and external messaging.

1. It’s a Framework Thing
IOC, AOP, Testing without Magic

2. Ashic Mahtab
http://www.heartysoft.com
@ashic
ashic@heartysoft.com

3. Frameworks – we love ‘em

4. but…

5. But, but…but they do so much.
Do they?

6. Alternative?
Simple Object Orientation Practices
[And Object Orientation need not
require an “object oriented” language]

7. Inversion of Control /Dependency
Injection
It’s about the source code dependency pointing
the opposite way of the runtime dependency –
however way you achieve that

8. Command Pattern
Decorator Pattern
Partial Application

9. Message Based Testing
How to Test Something Without Touching it

10. When I Do This Domain These Things Happen

11. Example Doc
Given –
1. An account registered with an account ID “x” and initial balance of
£200
2. An overdraw attempt is made to debit £300 from account “x”
3. An overdraw attempt is made to debit £300 from account “x”
When-
An attempt to debit £300 from account “x”
Then –
1. An overdraw attempt is made to debit £300 from account “x”
2. Account “x” is locked

12. Questions?