goos-code-examples
Code examples from later chapters of Growing Object-Oriented Software, Guided by Tests (by npryce)
| goos-code-examples | Practices | |
|---|---|---|
| 6 | 1 | |
| 72 | 10 | |
| - | - | |
| 10.0 | 10.0 | |
| over 8 years ago | about 4 years ago | |
| Java | ||
| - | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
goos-code-examples
Posts with mentions or reviews of goos-code-examples.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-20.
-
Don't Use Mocks
A very good way to use mocks (not like illustrated here) is explained in the GOOS book by Freeman and Pryce: http://www.growing-object-oriented-software.com/
-
Resources for learning TDD
Further read: Growing Object Oriented Software
-
Steel threads are a technique that will make you a better engineer
On the subject of TDD, the way I've done TDD has been very similar to the technique described in the article. Work in very small increments, try to get a very thin vertical slice of functionality working through the system as soon as possible and, whatever you build, try to get it working end-to-end as soon as you can. Of course, I use tests to drive the work but I find it very helpful to use tests to drive those thin vertical slices of functionality.
The book that really helped me to start working in this way is Growing Object Oriented Software, Guided by Tests by Steve Freeman and Nat Pryce [0]. The book has been around for a few years at this point and tech has moved on since then, as have some of the techniques, but it's still a very interesting read. (Disclosure: I was lucky enough to briefly work with one of the authors a few years ago but I was a fan of the book long before then.)
[0] http://www.growing-object-oriented-software.com/
-
Unit testing best practices
I think this is still the most referenced work. You probably know that one like the back of your hand, but it's still good to reference in general to convey confidence in the topic.
-
Sleeping is not the best option
[3] Have a look at the testing asynchronous systems examples in the GOOS Code examples repository for a more object-oriented implementation of helper for the polling for changes strategy, and also examples of the capturing notifications strategy.
Practices
Posts with mentions or reviews of Practices.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-20.
-
Don't Use Mocks
I agree with the premise and have taken a [deeper dive](https://github.com/osmyn/Practices/blob/master/UnitTestGuide...) if anyone is interested in learning more about creating tests that aren't brittle. I did this after suffering through poorly written tests that made our team afraid of any refactoring.
What are some alternatives?
When comparing goos-code-examples and Practices you can also consider the following projects:
fff - A testing micro framework for creating function test doubles