Individual Empowerment and agile…

(Interestingly, I find myself writing more about agile and team stuff now that I’m not on a development team….)   This is in response to a question about how you balance individual empowerment with the collaborative approach on a agile tem…    ***    Agile is all about the team, and being on an agile team requires participants to…

1

Moving from "write no tests" to TDD

There was a post on an internal alias about moving a team that has not been creating any developer-written tests to one that does TDD. I wrote a reply that I think may be of more general interest… Developers are fluent in code. I think any time you are talking to developers about engineering practices,…

5

Building Connection Center add-ins using WiX – part 2

To actually get anything installed, we’ll need a more reasonble WXS file. <?xml version=”1.0″?><Wix xmlns=”http://schemas.microsoft.com/wix/2003/01/wi”>  <Product Name=”Microsoft HealthVault Shortcut – Fabrikam WidgetTracker”     Id=”PUT-GUID-HERE”     Language=”1033″     Codepage=”1252″     Version=”1.0.0.0″     Manufacturer=”Fabrikam”     UpgradeCode=”PUT-GUID-HERE”>     <Package        Id=”PUT-GUID-HERE”       Description=”Microsoft HealthVault Shortcut – Fabrikam WidgetTracker”       Manufacturer=”Fabrikam”       InstallerVersion=”100″       Compressed=”yes”/>     <Property Id=”ARPNOMODIFY” Value=”1″ />    <Property Id=”ARPNOREPAIR” Value=”1″ />     <Media Id=”1″ Cabinet=”CCextend.cab” EmbedCab=”yes”/>   …

2

Building Connection Center add-ins using WiX – part 1

I’m writing this specifically for developers who need to add links into HealthVault Connection Center, but I think the topic is of general interest to anyone who wants to create installer packages. We’re going to be using the WiX (Windows Installer XML) toolset to create msi files. Note 1: While I find the mixed case…

1

Unit testing through the UI

One of my readers asked whether there were any UI unit testing tools. While I have seen some ASP.net tools like this, in general I’d expect that you would unit test a UI by making the UI a very thin layer (one that doesn’t really need testing), and writing the unit tests to talk to…

3

xUnit.net…

From Jim Newkirk, one of the original NUnit authors…  xunit.net

1

Beautiful code…

O’reilly publishes Beautiful Code Jonathan Edwards counters with a beautiful explanation. Now, I haven’t read the new book, but I have a strong resonance with what Edwards wrote.  You should definitely read the whole thing, but I few sentences jumped out at me. A lesson I have learned the hard way is that we aren’t…

10

Member names and UI controls

A follow-on to the previous discussion about member names. There were a variety of opinions, some of which argued for using no prefix at all. For those of you who are in the group, I’m interested in how you manage things when you are doing UI work, and having to deal with your 3 member variables…

15

YAGNI and unit tests…

Thanks for your comments. I decided to go ahead and write the unit tests for that layer, both because I knew what not writing them would be like, and I wanted to play with wrapping/mocking a system service. I also decided – as some of you commented – to do the right thing and encapsulate…

7

Does YAGNI ever apply to tests?

I’ve been writing a small utility to help us do some configuration setup for testing. It needs to walk a directory structure, find all instances of a specific xml file, and then make some modifications to the file. I TDD’d the class that does the XML file stuff, and I’m confident that it’s working well….

8