CI Factory Beta 0.8.0.27

jayflowers.com — There is a new beta for CI Factory, version 0.8.0.27. There are a lot of new features in this release. The changes are documented here. There are 22 new NAnt tasks, 13 new NAnt functions, 9 new CCNet plugins, and 10 new CI Factory Packages! read more...

add a comment | category: Open Source | Views: 1

Do You Smell That?

jayflowers.com — In this post I explorer a domain of smells focused on testability of product code. So there has been this enormous discussion on the Yahoo TDD Group about testability: it was kicked off by Marcus. I used this dialogue as an opportunity to explorer something my gut has been bothering me about. read more...

add a comment | category: Unit Testing | Views: 0

YAGNI and Testability

jayflowers.com — This post delves into the question: Is designing for testability justified? read more...

add a comment | category: Unit Testing | Views: 0

The Law of Demeter and Testability

jayflowers.com — This post looks at the relationship Testability has with the Law of Demeter. read more...

add a comment | category: Unit Testing | Views: 1

New Feature - Doubler 0.5.6.1

jayflowers.com — I guess the talk about Doubler got me motivated: I added a new feature. You can now select an entire assembly to create test stub recorders for! This feature can be useful to maintain a mirror assembly of recorders. If the abstracts types in the subject assembly change the doubles will no longer compile. This can be managed by hand, yuck!, regenerating each file individually, maybe okay?, and now regenerate the entire assembly. This will make it intuitive for developers to know where to look for a double as well. It is in the assembly name <SubjectAssemblyName>.TestDoubles.dll, in the namespace <SubjectNamespace>.TestDouble, with a class name… in the case of test stub recorders Recorder<SubjectTypeName>. read more...

add a comment | category: Unit Testing | Views: 1

Custom CCNET Branch - New Features That Could Not Wait!

jayflowers.com — This custom branch of CCNET offers new configuration options to create relationships between project (e.g. not only when projects should build but not build). It also offers the popular feature request of a user force filter. The ccnet project config file can specify users and or groups that are allowed or not allowed to force a build. This feature is enforced on both the web dashboard and the cctray. read more...

add a comment | category: Open Source | Views: 0

Build Contention Equation

jayflowers.com — We are exploring new ways to build our software at work. I was trying to convey a thought on validating the feasibility of a build process today with the following equation. Number of Change Packages = 8 Hours * 60 Minutes / (Build Time + Preparation Time + Buffer) Filling out the right side of the equation will show how many change packages can be process by the build on an average day. The Build Time is how long it take the build to complete. The Preparation Time is how long it takes a developer to get the build started. This could represent claiming the build token, submitting to source control and waiting for the build process to begin. In the proposed build process only one developer could submit at a time; the build is triggered by a submission to source control. The Buffer is the tricky variable. Read the entry to find out why. read more...

add a comment | category: Tips & Tricks | Views: 0

Testability

jayflowers.com — This post explores what is testability. It works to define testability so that it can be meassured objectively. An experimental metric is even created. read more...

add a comment | category: Unit Testing | Views: 0