Comments on: Agile Chronicles #3: Branch Workflow

By: Getting Advanced in Flex | der hess

Getting Advanced in Flex | der hess — Sat, 09 May 2009 10:02:02 +0000

[…] Agile Chronicles #3: Branch Workflow […]

By: anatinae

anatinae — Mon, 19 Jan 2009 16:52:39 +0000

hey
did your team try mercurial instead of svn http://www.selenic.com/mercurial/wiki/ I think it has many advantages when agile developement. Well I red the comment and in previous post you wrote that business classes won’t change much so when project starts you simply write tests of this classes ( services, factories) other tests for me it’s a waste of time.
And finally about merge day. I think important is to have project lead or small parts of the application leaders that merge the code and know what is exactly going on with the project. The continous merge when Mercurial is easier and less waste
Keep it up nice blog :)

By: JesterXL

JesterXL — Sat, 29 Nov 2008 23:49:37 +0000

Scars never heal, buddy!

By: Matthew Campbell

Matthew Campbell — Sat, 29 Nov 2008 23:40:39 +0000

Haah that Code monkey thing was like 5 years ago ;) I can’t believe you are still talking about that.

By: JesterXL

JesterXL — Sat, 29 Nov 2008 19:22:32 +0000

Thank you very much for the excerpt and explanation, Robert! That helps a lot. After playing around with fluint, it doesn’t feel that game changing to me. It felt natural to write tests making sure my shiz works. I do that already using test harnesses to more easily test my GUI components in isolation as I work on them. It seems I just take it a step further, and write the tests even though the component doesn’t actually implement the implied API yet.