Comments on: Example of Removing Some Pain: Grid Fluent API

By: Derick Bailey

Derick Bailey — Mon, 30 Jun 2008 18:02:47 +0000

that’s basically what I was thinking, too. The only reason I would bother with DI for testability would be when the layout of the control was truly really a business concern. Off-hand, though, I can’t think of any real examples where the layout would be the business concern, except for the business of custom controls.

By: Chad Myers

Chad Myers — Mon, 30 Jun 2008 17:55:46 +0000

Derick:

You could do that as an interaction test. What we ended up doing was just checking that the Grid had the columns we expected in the end. I was less concerned with the interaction with the GridLayout FI than I was with the end state (in this case).

It made for easier state based testing so we could do things like:

layoutForm.Grid.ShouldHaveColumn(“Description”);

By: Derick Bailey

Derick Bailey — Mon, 30 Jun 2008 17:41:11 +0000

Is it worth creating an IGridLayout interface that can be injected, so that this layout code can be unit tested? (i have my own opinion, but want to see what you think)

By: Jeff Certain

Jeff Certain — Mon, 30 Jun 2008 13:10:45 +0000

Chad,

I just finished doing something similar for a bunch of our “helper methods” for these same controls. I’d been wondering about the Appearance verbosity, and now I’ve got a good pointer for the right road to go down.

Thanks!

Jeff

By: Macca

Macca — Sun, 29 Jun 2008 11:09:06 +0000

Chad,

Nice, thanks for taking the time to elaborate on your previous post (and so quickly too!). Very useful indeed.

By: Florian Potschka

Florian Potschka — Sun, 29 Jun 2008 06:48:46 +0000

How true. Especially GUI code often tends to be extreme verbose and repetitive. So a fluent API is a great benefit for this kind of code.