I got some feedback today from someone who said they were looking through the pythontesting.net/start-here page and were still a bit confused as to how to start testing.
I totally understand that and want to improve it. I want to make the site more friendly to people new to testing.
What info would help?
(try to answer that before reading further as it might color your answer)
(seriously, think about your answer first before reading further)
Would these kinds of things help?
- How granular should your test be?
- Should you be using mocks?
- What are mocks anyway?
- Tests answer questions about my code. What are those questions?
- Exactly what tests should I write?
- How to develop test cases.
- What’s a test case?
- Actually, what’s the minimum of terminology I need to start testing?
- Developer tests for the:
- 1 person team
- dev that will pass their code to a QA team/person working with the dev team/person
- dev team that does all the QA
- How do I organize tests?
- How do I visualize test results?
- How important is code coverage?
- What is code coverage?
- When should I write tests?
- Testing and test case strategies like behavior coverage, equivalence partitioning, boundary value analysis, state machine models, act-like-a-customer tests, functionality units, dependency testing, …
- Lean testing
- test suite versioning
Are any of these helpful?
What’s better, written posts, podcast episodes, videos (I don’t do videos yet but plan to)?
Thanks in advance.