1.2 KiB
+++ title = "Reveries About Testing" date = 2020-01-13
[taxonomies] tags = ["tests", "testing", "integration tests", "unit tests"] +++
Today, a large number of developers use some testing methodology. But what are tests? What are they for? What is the purpose of writing testes, anyway? Are we testing the right things?
{% note() %} This is a companion post for one my presentations, Filosofando Sobre Testes, which is in Portuguese. {% end %}
Before we start, let me give you some disclaimers:
-
I'm non-orthodox about tests. What I mean by that is that some of stuff I'll mention here are exactly the opposite of what everyone says and the opposite of the way people work with tests.
-
In no way, consider this a set of rules. What I really want is to stop people from writing tests without knowing why they are writing those tests.
-
You don't need to agree with anything here. Again, the idea is to sotp and think what is being tested before writing tests.
What I want to discuss:
- TDD, Kent Beck Style;
- "Fast Tests, Slow Tests";
- The Explosion of Slow Tests;
- Coverage;
- Mocks.