Is it completed?

[Atlantic777]

Hey, I was very pleased to find out about this book! I have to ask you, is it completed and if it's not, how can we track progress and see what else needs to be done/written?

And thank you for sharing. :)

Nikola

[grzesiek-galezowski]

Hi, Nicola!

Thanks for your interest in this project. Here are the answers:

The tutorial is actually more 'started' than complete. I started it just few weeks ago by copying over most of my blog posts with relevant material into github. Now I'm writing the book from cover to cover looking at what material I can reuse.

Currently, the "finished" chapters are:

1. Motivations
2. Three essential tools
3. It's not a test

and I am working on fourth one (related to 'why' behind the Test-First approach). Note that by saying "finished", I mean something that you can read from beginning to end, because the concept is for the tutorial to stay "incomplete" always in a sense of being open for new contributions and corrections.

Good news is that I'm quite active on the project - you can see the activity on the Commits tab. Also, you can subscribe to RSS for commits, so you'll get information on what's going on in the project right in your favorite news reader.

As for what needs to be done - I don't have a clear plan yet, but things I certainly want to include are:

1. Mocks and how to use them as an aid in evolutionary design (this is going to be a hard part - explaining mocks in other way than "dependency breaking tools" is challenging, but necessary :-))
2. Triangulation
3. The importance of testability with examples
4. Setup/Teardown and some best practices on using them
5. A little refactoring and working with legacy code (maybe some mention of the Mikado Method?)
6. I'm also thinking on how much design knowledge to put in. Should I explain SOLID principles? Should I explain code qualities? Should I explain other design techniques? What way should I do this - in a separate chapter or 'as I go'?
7. Some frequently asked questions

Also, I'm planning on dividing the tutorial into two parts - basic (that will get you up and running) and advanced (that will discuss more concrete topics like partial mocks, test-driving attributes etc.). Also, I plan to incorporate some kind of "achievements" into the tutorial, signs of which can already be seen.

Thinking about your question leads me a conclusion that it would be beneficial to put some kind of marker inside the tutorial to separate the "finished" part from the raw material, so that everyone knows how much is "ready" to be read.

Thanks again and don't hesitate to submit issues or comment on this one should you have any suggestions or corrections!

[grzesiek-galezowski]

Chapter 4 is complete. Feel free to read through and submit any suggestions or corrections!

[grzesiek-galezowski]

Chapter 5 is complete. Hope you like it!

[grzesiek-galezowski]

chapters 6-8 are ready for public!

[grzesiek-galezowski]

chapter 11 is ready!

[grzesiek-galezowski]

The book binaries are transitioned to Leanpub. The book is now considered 30% done

[coosmiin]

I see on Leanpub that it is 40% complete. Do you have any plan in mind about a finish date? Should I start reading it or it's better to wait for few months?

[grzesiek-galezowski]

Hi,
The book is planned as a continuous effort, but I'm currently reviewing what I have already written and stabilising the existing material. The last reviewed chapter is "Specifying functional boundaries and conditions" so you can read it and preceeding chapters without worrier, they are not going to change in a significant way anytime soon.