Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D digitec-wiki
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Digitec
  • digitec-wiki
  • Wiki
  • smells and heuristics tests

smells and heuristics tests · Changes

Page history
rcabral created page: smells-and-heuristics-conclusion authored Mar 22, 2014 by Rene Cabral's avatar Rene Cabral
Hide whitespace changes
Inline Side-by-side
smells-and-heuristics-tests.markdown
View page @ 1a8d4304
......@@ -18,8 +18,7 @@ Coverage tools reports gaps in your testing strategy. They make it easy to find
#### T3: Don't Skip Trivial Tests
They are easy to write and their documentary value is higher than the cost to produce
them.
They are easy to write and their documentary value is higher than the cost to produce them.
#### T4: An Ignored Test Is a Question about an Ambiguity
......@@ -27,13 +26,11 @@ Sometimes we are uncertain about a behavioral detail because the requirements ar
#### T5: Test Boundary Conditions
Take special care to test boundary conditions. We often get the middle of an algorithm
right but misjudge the boundaries.
Take special care to test boundary conditions. We often get the middle of an algorithm right but misjudge the boundaries.
#### T6: Exhaustively Test Near Bugs
Bugs tend to congregate. When you find a bug in a function, it is wise to do an exhaustive
test of that function. You'll probably find that the bug was not alone.
Bugs tend to congregate. When you find a bug in a function, it is wise to do an exhaustive test of that function. You'll probably find that the bug was not alone.
#### T7: Patterns of Failure Are Revealing
......@@ -43,8 +40,7 @@ As a simple example, suppose you noticed that all tests with an input larger tha
#### T8: Test Coverage Patterns Can Be Revealing
Looking at the code that is or is not executed by the passing tests gives clues to why the
failing tests fail.
Looking at the code that is or is not executed by the passing tests gives clues to why the failing tests fail.
#### T9: Tests Should Be Fast
......
Clone repository
  • alpha beta testing
  • browser testing
  • camtasia licenses
  • code delivery processes
  • coding practices
  • css and sass coding standards
  • database schema standards
  • dependency management
  • development environments
  • digitec agile process
  • digitec gitlab styles
  • digitec software promises
  • digitec spec process
  • gitlab administration
  • gitlab issues tags
View All Pages