👨‍💻
Software Engineering
Clean Code: Agile Software Craftsmanship
Clean Code: Agile Software Craftsmanship
  • Clean Code
  • 1: Clean Code
    • There Will Be Code
    • Bad Code
    • The Total Cost of Owning a Mess
    • Schools of Thought
    • We are Authors
    • The Boy Scout Rule
    • Prequel and Principles
    • Conclusion
  • 2: Meaningful Names
  • 3: Functions
  • 4: Comments
  • 5: Formatting
  • 6: Objects and Data Structures
  • 7: Error Handling
  • 8: Boundaries
  • 9: Unit tests
  • 10: Classes
  • 12: Emergence
  • 13: Concurrency
    • Why Concurrency?
    • Challenges
    • Concurrency Defense Principles
    • Know Your Library
    • Know Your Execution Models
    • Beware Dependencies between Synchronized Methods
    • Keep Synchronized Sections Small
    • Writing Correct Shut-Down Code is Hard
    • Testing Threaded Code
    • Conclusion
Powered by GitBook
On this page
  • Treat Spurious Failures as Candidate Threading Issues
  • Get Your Nonthreaded Code Working First
  • Make Your Threaded Code Pluggable
  • Make Your Threaded Code Tunable
  • Run with More Threads Than Processors
  • Run on Different Platforms
  • Instrument Your Code To Try and Force Failures
  • Hand-Coded
  • Automated
  1. 13: Concurrency

Testing Threaded Code

Treat Spurious Failures as Candidate Threading Issues

asdf

Get Your Nonthreaded Code Working First

asdf

Make Your Threaded Code Pluggable

asdf

Make Your Threaded Code Tunable

asdf

Run with More Threads Than Processors

asdf

Run on Different Platforms

asdf

Instrument Your Code To Try and Force Failures

asdf

Hand-Coded

asdf

Automated

asdf

PreviousWriting Correct Shut-Down Code is HardNextConclusion

Last updated 9 months ago