Book Image

Polished Ruby Programming

By : Jeremy Evans
Book Image

Polished Ruby Programming

By: Jeremy Evans

Overview of this book

Anyone striving to become an expert Ruby programmer needs to be able to write maintainable applications. Polished Ruby Programming will help you get better at designing scalable and robust Ruby programs, so that no matter how big the codebase grows, maintaining it will be a breeze. This book takes you on a journey through implementation approaches for many common programming situations, the trade-offs inherent in each approach, and why you may choose to use different approaches in different situations. You'll start by refreshing Ruby fundamentals, such as correctly using core classes, class and method design, variable usage, error handling, and code formatting. Then you'll move on to higher-level programming principles, such as library design, use of metaprogramming and domain-specific languages, and refactoring. Finally, you'll learn principles specific to web application development, such as how to choose a database and web framework, and how to use advanced security features. By the end of this Ruby programming book, you’ll be a well rounded web developer with a deep understanding of Ruby. While most code examples and principles discussed in the book apply to all Ruby versions, some examples and principles are specific to Ruby 3.0, the latest release at the time of publication.
Table of Contents (23 chapters)
1
Section 1: Fundamental Ruby Programming Principles
8
Section 2: Ruby Library Programming Principles
17
Section 3: Ruby Web Programming Principles

Chapter 11

  1. ruby -wc filename.
  2. In general, using behavior-driven development is a waste of time if the programmers are writing the specifications, since the programmers could more easily write the executable test code directly, compared to writing the specifications and maintaining the code that converts the specification to executable test code.
  3. Not always, it depends on the type of abstraction. Moving setup code to methods and using enumerables to define multiple test methods are both good uses of abstractions in test code.
  4. Model testing is in general more reliable and less likely to result in false positives and false negatives compared to unit testing.
  5. Nothing. But less than 100% code coverage means some code is not being tested at all.