In bootcamp you explored the principles of TDD (what is a test, writing a test before code, red-green-refactor, etc.). Before we meet up again to go deeper into testing, I'd like you to explore how testing works on your projects.
To submit your answers, you must first create a branch of this repository, then edit this README file.
-
Describe the approach to TDD on your delivery. In general, how strict are people writing tests before code? (This is not a judgement, just an observation of what you are noticing). What makes it difficult to start with tests? What might make it easier?
-
What testing frameworks are in use? Is the same framework used for everything, or do you have a framework for testing code, and one for testing a website or service?
-
Looking at the language(s) used, list at least 5 other testing frameworks. What do they have in common, and what's their unique proposition?
-
Using a coverage tool, what is the test coverage on the project (If there's more than one project, choose one). What might that result suggest? In what area would you discuss adding more tests?
-
Looking at the tests written, how confident would you say they:
- describe what is happening
- correctly document what the code should be doing
- drive development of the code (because of this test this feature and only this feature was made)