Browse Source

New chapter: Languages with tests

master
Julio Biason 6 years ago
parent
commit
953ab02206
  1. 1
      content/books/things-i-learnt/_index.md
  2. 25
      content/books/things-i-learnt/languages-tests/index.md
  3. 2
      content/books/things-i-learnt/throw-away/index.md

1
content/books/things-i-learnt/_index.md

@ -15,3 +15,4 @@ template = "section-contentless.html"
* [Tests Make Better APIs](tests-apis) * [Tests Make Better APIs](tests-apis)
* [Make Tests That You Know How To Run on the Command line](tests-in-the-command-line) * [Make Tests That You Know How To Run on the Command line](tests-in-the-command-line)
* [Be Ready To Throw Your Code Away](throw-away) * [Be Ready To Throw Your Code Away](throw-away)
* [Good Languages Come With Tests](languages-tests)

25
content/books/things-i-learnt/languages-tests/index.md

@ -0,0 +1,25 @@
+++
title = "Things I Learnt The Hard Way - Good Languages Come With Tests"
date = 2019-06-20
[taxonomies]
tags = ["en-au", "books", "things i learnt", "programming languages", "tests"]
+++
You can be sure that if a language brings a testing framework -- even minimal
-- in its standard library, the ecosystem around it will have better tests
than a language that doesn't carry a testing framework, no matter how good the
external testing frameworks for the language are.
<!-- more -->
The reason is kinda obvious on this one: When the language itself brings a
testing framework, it reduces the friction for people to start writing tests,
and that includes the authors of the language itself and the community.
Sure, better frameworks may come along, and languages that don't have a
testing framework in their standard library may have options with better
support and easier access but, again, when they are there from the start, the
start is better and the final result is better.
{{ chapters(prev_chapter_link="/books/things-i-learnt/throw-away", prev_chapter_title="Be Ready To Throw Your Code Away") }}

2
content/books/things-i-learnt/throw-away/index.md

@ -35,4 +35,4 @@ solves the problem, but also the tests for that code.
... unless you focus mostly on [integration ... unless you focus mostly on [integration
tests](/books/things-i-learnt/integration-tests). tests](/books/things-i-learnt/integration-tests).
{{ chapters(prev_chapter_link="/books/things-i-learnt/tests-in-the-command-line", prev_chapter_title="Make Tests That You Know How To Run on the Command line") }} {{ chapters(prev_chapter_link="/books/things-i-learnt/tests-in-the-command-line", prev_chapter_title="Make Tests That You Know How To Run on the Command line", next_chapter_link="/books/things-i-learnt/language-tests", next_chapter_title="Good Languages Come With Tests") }}

Loading…
Cancel
Save