elialbert/testing_mindset.txt

## testing_mindset.txt
 Exercise: Knows why we "Don't trust the developer"
- Developers are a tricksey bunch. Name some reasons why you shouldn't just trust the person who wrote the code.

I understand the thinking here. It's easy to write code and be really proud of it, which means you wouldn't necessarily notice issues with the code. Easy to be blinded by pride, or arrogance kind of thing.

- Name some mental pitfalls that you should watch out for when testing code.

I think all developers should try to stay in the testing mindset. It's always broken. It's never perfect. Strive for excellence, expect bugs. So the pitfall is the "it's done" mindset.

- So then, why shouldn't we be satisfied with testing our own code?
I kind of disagree. I think with training and discipline we can be satisfied with our own testing. I think with effectively written tests, we should be OK.
I do think that a second test writer for E2E tests makes sense, especially when validating business logic.
	Exercise: Knows why we "Don't trust the developer"
	- Developers are a tricksey bunch. Name some reasons why you shouldn't just trust the person who wrote the code.

	I understand the thinking here. It's easy to write code and be really proud of it, which means you wouldn't necessarily notice issues with the code. Easy to be blinded by pride, or arrogance kind of thing.

	- Name some mental pitfalls that you should watch out for when testing code.

	I think all developers should try to stay in the testing mindset. It's always broken. It's never perfect. Strive for excellence, expect bugs. So the pitfall is the "it's done" mindset.

	- So then, why shouldn't we be satisfied with testing our own code?
	I kind of disagree. I think with training and discipline we can be satisfied with our own testing. I think with effectively written tests, we should be OK.
	I do think that a second test writer for E2E tests makes sense, especially when validating business logic.