Development > Software, Programming >

• Ruby > Ruby testing

Notes ∞

• It's not a test case if it touches the: disk, network, database

Terms

• Acceptance Testing
• Behavior Driven Development (BDD)
• Behaviour-Driven Development (BDD)
• Test All The Fucking Time (TAFT)
• Stub - Just returns a value

• Mock - More interactive than a stub. It actually cares about the parameters passed to it, how many times it's called, etc.

Qualities ∞

Technical:

1. Isolated from the outside world

   • Doesn't talk to the database, communicate across the network, touch the file system or do special things to the environment
   1. It is written gray-box, i.e. it reads as if it were black-box, but sometimes takes advantage of white-box knowledge. (Typically a critical factor in avoiding combinatoric issues.)

2. Isolated from other tests

   • Unaffected by the presence, absence, or results of other tests. No dependencies. Self-contained.
   1. Order Independent and Isolated - it should be possible to run the tests in whatever order the test runner chooses.
   2. be able to run at the same time as other unit tests, even concurrently with itself
   3. It does not test the object inside the running app, but instead in a purpose-built testing application.

3. Repeatable in every aspect

   1. Test your boundary conditions and Always keep your tests passing at 100%.

Social / Convenience:

1. Simplifies design and improves productivity. Improvements in code quality and a reduction in bugs are an important side effect.
2. Intention-revealing - the best unit tests make it clear to the reader how an objects API is intended to be used.

3. Easy to Setup

   1. Short, typically under a dozen lines of code.
   2. It invokes only a tiny portion of the code, most usually a single branch of a single function.
   3. Quick and easy to write
   4. It is generally written before the code-change it is meant to test.
   5. Maintainable

4. Fast to run/complete

   • As above, it's short and invokes a tiny portion of the code.
5. Unique (providing confidence not provided by other tests/uncorrelated with other tests)
6. Automated
7. Readable

8. Trustworthy

   1. Coded to the same standard as shipping code, i.e. the team's best current understanding of coding excellence.

9. Promotes code commits: In combination with all other microtests of an app, it serves as a 'gateway-to-commit'. That is, a developer is encouraged to commit anytime all microtests run green, and discouraged (strongly, even nastily) to commit otherwise.

I have no idea what that means:

• It avoids most or all usage of 'awkward' collaborators via a variety of slip-and-fake techniques.

Reading ∞

• Don't Become the Quality Police
• What are the Qualities of a Good Test? by Mark Levison on Oct 03, 2008

• https://www.satisfice.com/

  • https://www.satisfice.com/blog (RSS)
  • (old blog, archive)

• Linux Desktop Testing Project

  • The GNU/Linux Desktop (GUI Application) Testing Project (GNU LDTP) aims to produce a high quality test automation framework with cutting-edge tools that can be used to test and improve the GNU/Linux or Solaris desktops. It uses the Accessibility libraries to discover through the application's user interface. The framework also has tools to record test-cases based on user actions in an application.

Last updated 2020-05-19 at 16:13:08