Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
When a Doing item has been coded, shouldn't it be tested before moving it to the Done column?
At least for me, code that I write seems to be logical and correct in my mind but often contains bugs that manifest during testing. When the song queue data structure was implemented in the class, why wasn't a test conducted to ensure that it works properly, before moving the associated Doing item into the Done column? I believe many other parts of the code were indeed given a preliminary test before the project item was advanced to the Done column.
Also, are the Backlog, ToDo, Doing and Done lists examples of Queue structures? Might be a nifty project to create a console based equivalent of the UI shown in the course video.
Craig DennisTreehouse Teacher
The way most teams work is that they create a definition of what Done means. In all cases, there should be tests written, and a quick demo to the Product Owner/Project Manager. Unfortunately our little simulation here doesn't have all those aspects, but I plan to add to what we are doing, and will definitely talk that through during our next courses.
Thanks for pointing that out!