Skip to content

Commit

Permalink
Merge branch 'main' into fix_issue_template
Browse files Browse the repository at this point in the history
  • Loading branch information
sarahcollyer authored Dec 5, 2024
2 parents bcd9236 + 48c90d5 commit 1101220
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions book/testing_code.md
Original file line number Diff line number Diff line change
Expand Up @@ -799,3 +799,13 @@ from simplified dummy data.

There are a range of established SQL testing frameworks. Examples include [tSQLt](https://github.com/tSQLt-org/tSQLt)
and [pgTAP](https://github.com/theory/pgtap/) for Postgres.


## In a time crunch? The risks to skipping tests
In an ideal world, testing code would never be skipped, keeping the software reliable,
and easily reproducible. However, in practice there are times when skipping tests may be necessary—
perhaps due to tight deadlines, limited resources, or the need to quickly get a feature up
and running. While this can save time in the moment, it’s important to be cautious, as
skipping tests can lead to hidden problems that may become harder to fix later, particularly
as the project grows. Whenever tests are set aside, it’s best to have a plan for going back to add
them, to avoid risks to the stability and quality of the software.

0 comments on commit 1101220

Please sign in to comment.