Isolating Functional Units: Why We Need Stubs
I’m planning a short set of articles on testing, summarising my thoughts from the slides presented at RefTest (here). This first one looks at the traditional split between unit tests, in which tests are generally isolated, and functional tests, which exercise an entire call stack.
About
I’ve worked with software and with computers for a while now. Long enough to sometimes be useful but not so long as to have lost interest.
My experiences of late have largely focused around distribted caching, in particular with Coherence, and this has inevitably shaped my understanding of systems, so keep that in mind as you read on.
The articles here really fall into two categories: Coherence stuff that I know, and wider issues of distributed computing, running projects and the like, which I find interesting. You can read a little more about me here.
Coherence
- Coherence Part I: An Introduction
- Coherence: The Fallacy of Linear Scalability
- Performing Efficient Cross-Cache Joins in Coherence
- How do I calculate how much data I can store in a Coherence cluster?
- How Fault Tolerant Is Coherence Really?
- Merging Data And Processing: Why it doesn’t “just work”
- Coherence Part IV: Merging Data And Processing
- Coherence Part III: The Coherence Toolbox
- Coherence Part II: Delving a Little Deeper
Other Stuff
- Disruptive Technologies in the Data Layer
- Shared Nothing v.s. Shared Disk Architectures: An Independent View
- Mapping Personal Practices
- Beyond Stubs: Why We Need Interaction Testing
- Isolating Functional Units: Why We Need Stubs
- Are Mocks All They Are Cracked Up To Be?
- Are You an HPC Architect?
- Software Writing and the Intellectual Superiority Complex
- Component Software. Where is it going?
- Do Metrics Have a Place in Software Engineering Today?
Categories
- Architecture (3)
- Coherence (9)
- Database (2)
- HPC (2)
- Rant (1)
- Software Development (6)
- TDD (3)
- Team Development (1)