Functions

functions should be small functions should be smaller than that! Functions should hardly ever be 20 lines long

Functions should do one thing. they should do it well. they should do it only!

One way you can know if a function is doing more than one thing is if you can extract another function from it with a name that is not merely a restatement of its implementation

The step down rule - the code should read like a top-down narrative. Every function should be be followed by the next level of abstraction one at a time

• To include the setups and teardowns, we include setups, then we include the test page content, and then we include the teardowns.
  • To include the setups, we include the suite setup if this is a test suite, then we include the regular setup.
    • To include the suite setup, we search the parent hierarchy for the 'SuiteSetup' page and add an include statement with the path of that page
      • To search the parent hierarchy...