Build 930 - Unit test results layout improvement suggestions

Continua CI Feature Requests
1

Well I've got to say I'm excited about build 930 as lots of things are working well and I'm getting a good picture of how Continua is going to work with our CI process. Great work guys!

I've got a couple of suggestions for the nunit test screen layout (no particular order). These are fairly minor suggestions, it looks great!

  1. Please can the Not Run orange box be applied to the results that are currently called Ignored red boxes as I have decorated those unit tests with the nunit IGNORE attribute.  I believe they represent the same statistic in the results.
  2. If I use BDD naming conventions for my unit tests the layout doesn't accommodate the much longer method/class naming that you find. As I have 3-4 lines in those columns and lots of white space.
  3. If I use BDD naming could you parse out the underlines for spaces in those results so non programming "people" could read those? Eg. "Can_get_percents_for_specific_record_type_for_the_appropriate_system_configuration" become "Can get percents for specific record type for the appropriate system configuration". I can see business analysts wanting this.
  4. Please can we shrink the Namespace and assembly columns.
  5. When "shelving" a unit test, can the option to apply that to project or configuration be a radio button, so we don't have to constantly click the drop down to change them to "project". (1 click vs 2).
  6. Please can some of the unit test results get pasted into the "Build" column on the left of the screen or shown in the summary views elsewhere in Continua? All I'm going to care about is "Passes, Failed and Errors" anything "ignored or shelved" wouldn't be an immediate problem.  I'd be happy for a JS rollover popup of unit test results if they existed. 

Unit test Test Naming - Behavioural Driven Design (BDD) 

http://dannorth.net/introducing-bdd/
http://nspec.org/

Arrange - Refers to setting up a test condition 
Act - refers to invoking the operation under test 
Assert - Checking the result. 

Example of BDD naming. 

Class: When_User_is_Authenticated_they

Unit Test Method: Could_change_own_password.



2

Hi Jamie

1) Will investigate, we did spend a lot of time working out how things worked for NUnit (and other unit test tools).

2) Agreed, spacing is a problem, there is only so much space available, we have changed the spacing a million times in the last year!

3) Good idea, we use BDD style test naming ourselves, switching underscores for spaces should be trivial (will only apply to new builds once done though).

4) Will try… we have some long namspaces and some of them wrap as well, so it’s a balancing act.

5) Should be able to do that, will look into it.

6) We’ll look into it. My main concern would be the impact on performance.

Thanks for the feedback, much appreciated.