Just Coding : Agile

Great ALM Icons

rido — Wed, 18 Nov 2009 23:20:31 GMT

TMap for Visual Studio 2010 [ http://tmap.codeplex.com/ ] is a testing focused process guidance, looks great !! ..and it has a nice icon set to illustrate the software lifecycle like the development and test ones...(read more)

Moles

rido — Thu, 05 Nov 2009 21:37:00 GMT

I’ve been interesting in unit testing for some years now. One major aspect of unit testing is about how use designs that allows a separation of concerns so you can test your program as units (usually at class level), for this the interface basic programming...(read more)

TestResults Reports in TFS Builds

rido — Thu, 24 May 2007 21:54:00 GMT

If you use TFSBuilds with VS UnitTests, you know how to inspect the TestResults: you must download the whole directory to your local machine, and sometimes this folder could be pretty huge. So, if you want to check the error details of your tests, you...(read more)

Testing with VS2005 Demo

rido — Mon, 27 Nov 2006 17:12:00 GMT

Today's workshop was based on a demo to show all the vs features about testing, it covers: Unit Tests (With MockObjects) Integration Tests (Using ASP.Net Host) Functional Tests (With Web Tests) Load Tests (With testcontrollers and test agents) I've packed...(read more)

My Workshop about testing

rido — Mon, 27 Nov 2006 03:42:00 GMT

Tomorrow I will be talking about Testing with VS2005, here is my presentation: http://blogs.msdn.com/rido/attachment/1156243.ashx If you are interested in the code samples, please let me know and I will send you the latest version...(read more)

Using Code Coverage with Manual Testing

rido — Tue, 29 Aug 2006 00:46:00 GMT

http://blogs.msdn.com/marcalt/archive/2006/07/02/654157.aspx A good thing to remember about CodeCoverage in VSTS... however I wonder how to evaluate this metric because "manual testing" is slow... I don't think you could reach more than 20% CC with manual...(read more)

Two Rules from Grady Booch

rido — Mon, 21 Aug 2006 14:09:04 GMT

Grady Booch (the legendary methodologist) talks in an interview about architectural patterns. I loved one sentence from this interview, when he answered the question: "What are the hallmarks of successful large software projects?", he said: "Here are...(read more)

trx2html

rido — Tue, 23 May 2006 04:06:00 GMT

Updated !! now this tool has it's own homepage at codeplex www.codeplex.com/trx2html ----------------------------------------------------------------- As I said in my previous post , I'm working on a tool to convert trx files (TestRun Results from VSTS)...(read more)

Rido's agile books list

rido — Thu, 08 Dec 2005 02:26:00 GMT

I have published aan Amazon list with my favorite agile books http://www.amazon.com/gp/richpub/listmania/fullview/1LHHR9AYGE60N/002-6823113-7530423 (comments are in spanish)

NUnit 2.2.3

rido — Thu, 17 Nov 2005 02:49:00 GMT

I was waiting for the new version, it has been tested with .Net 2.0 RTM.

http://sourceforge.net/project/showfiles.php?group_id=10749

Petzold and new IDEs

rido — Sat, 05 Nov 2005 23:15:00 GMT

With the proximity of VS 2005 launch everybody is talking about IDEs. I know it's not a new discussion, IDE vs Editors, VS vs Notepad, Eclipse vs VIM ...

Charles Petzold has written a piece http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.html that has been popular see http://it.slashdot.org/article.pl?sid=05/10/26/1935250&tid=156&tid=166&tid=8 and http://lambda-the-ultimate.org/node/view/1084. He talks about VS tools like Intellisense, form editors and other kind of code generators inside the IDE.

I think every programmer has the same feelings about VS, sometimes you love it, and some times you hate the editors.

If VS is generating code that is far from readable, we must know that, and try to separate VS generated code, from "our code", and partial classes are going to help too much here. But we need more support to differenciate both.

I like to use Static Analysis Tools like FxCop (now integrated with the IDE), you will see how IDEGeneratedCode does not the default Rules. I also use VIL or NDepend to look for common not recommended practices like, Methods longer than 100 lines, or classes with more than 50 fields, obviously the InitializeComponent method never satisfy this simple rules.

The other big problem with this kind of IDE tools is the Bottom-Up design. I have felt comfortable with Intellisense until I tried (and got inlove ) with TDD, Why I have to write the same things twice? (the first in the test, and the second in the implementation). I need a smart IDE that could infere the method signatures and class interfaces from my test definitions, and I know I would be writing without Intellisense. But maybe another coding tools like CodeSnippets or AutoCode templates can help.

From the testing point of view, you should think "Who cares if IDEGeneratedCode has unit tests while It Works?". However if you write real programs you know that "ItWorks" it's not enough, you will have to change your code, and Unit tests can help you a lot with that, but the code generated by the IDE does not include unit tests. But the new VS (only some versions) include a wizard to generate unit tests for your classes, and sincerely I have tried to use it and I think it does not help too much, just creating the unit test skeleton.

There is no simple advice about code generation and IDEs, when, where and how much should we use these tools?

Like everything is a matter of balance, try to figure the future changes in your code, how can you test the main interfaces of the generated code, and how hard is change it.

My best recommendation is taken from the old (but still great) book "The Pragmatic Programmer". http://www.pragmaticprogrammer.com/ppbook/extracts/wizards.html

Don't Use Wizard Code You Don't Understand

NUnit vs VSTS

rido — Sun, 30 Oct 2005 19:52:00 GMT

NUnit is the most popular unit tests framework for .Net. The new VSTS has a chance to replace NUnit in corporate environments, however there are some minor issues you must know before take a decission… ...(read more)

HowToUseXmlDataDocument

rido — Thu, 27 Oct 2005 01:55:00 GMT

One test is better that thousand words...

[TestFixture]

public class XmlDataDemo

{

[Test]

public void LoadDataSet()

{

EmployeeDataSet ds = new EmployeeDataSet();

ds.ReadXml(@".\..\..\Employee.xml");

Assert.AreEqual(1,ds.employee.Rows.Count);

}

[Test]

public void XmlDataDoc()

{

XmlDataDocument doc = new XmlDataDocument(new EmployeeDataSet());

doc.Load (@".\..\..\Employee.xml");

XmlDocument d = UntypeAndModifyAge(doc, "22");

EmployeeDataSet ds2 = new EmployeeDataSet();

ds2.ReadXml(CreateEmployeeValidatingReader(d.InnerXml));

Assert.AreEqual(1,ds2.employee.Rows.Count);

Console.WriteLine("After modify .....");

Console.WriteLine(ds2.GetXml());

}

[Test, ExpectedException(typeof(XmlSchemaException))]

public void XmlDataDocValidatingException()

{

XmlDataDocument doc = new XmlDataDocument(new EmployeeDataSet());

doc.Load (@".\..\..\Employee.xml");

XmlDocument d = UntypeAndModifyAge(doc, "22a");

EmployeeDataSet ds2 = new EmployeeDataSet();

ds2.ReadXml(CreateEmployeeValidatingReader(d.InnerXml));

}

private XmlValidatingReader CreateEmployeeValidatingReader(string xml)

{

XmlValidatingReader vr = new XmlValidatingReader(xml, XmlNodeType.Document, null);

vr.ValidationEventHandler +=new System.Xml.Schema.ValidationEventHandler(vr_ValidationEventHandler);

XmlSchemaCollection sc = new XmlSchemaCollection();

sc.Add("urn:rido.code/Employee", new XmlTextReader(@".\..\..\EmployeeDataSet.xsd"));

vr.Schemas.Add(sc);

return vr;

}

private XmlDocument UntypeAndModifyAge(XmlDocument doc, string ageToModify)

{

((XmlDataDocument)doc).DataSet.EnforceConstraints = false;

doc.GetElementsByTagName("Age")[0].InnerText = ageToModify;

((XmlDataDocument)doc).DataSet.EnforceConstraints = true;

string s = doc.InnerXml;

XmlDocument result = new XmlDocument();

result.LoadXml(s);

Console.WriteLine("modified from untyped.....");

Console.WriteLine(s);

return result;

}

[Test]

public void LoadDataSetWithBadNamespace()

{

EmployeeDataSet ds = new EmployeeDataSet();

ds.ReadXml(@".\..\..\EmployeeNoNs.xml");

Assert.AreEqual(0,ds.employee.Rows.Count);

}

[Test]

public void LoadDataSetWithBadXml()

{

EmployeeDataSet ds = new EmployeeDataSet();

ds.ReadXml(@".\..\..\XmlFile1.xml");

Assert.AreEqual(0,ds.employee.Rows.Count);

}

private void vr_ValidationEventHandler(object sender, System.Xml.Schema.ValidationEventArgs e)

{

//Assert.Fail(e.Message);

throw e.Exception;

}

<?xml version="1.0" encoding="utf-8" ?>

<xs:schema id="EmployeeDataSet" targetNamespace="urn:rido.code/Employee" elementFormDefault="qualified"

attributeFormDefault="qualified" xmlns="urn:rido.code/Employee" xmlns:mstns="urn:rido.code/Employee"

xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">

<xs:element name="EmployeeDataSet" msdata:IsDataSet="true">

<xs:complexType>

<xs:sequence>

<xs:element name="employee" type="Employee" minOccurs="1" />

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:complexType name="Employee">

<xs:sequence>

<xs:element name="Name" type="xs:string" minOccurs="0" />

<xs:element name="Age" type="xs:int" minOccurs="0" />

</xs:sequence>

</xs:complexType>

</xs:schema>

<?xml version="1.0" encoding="utf-8" ?>

</employee>

</EmployeeDataSet>

Scrum for MSProject 2003

rido — Sat, 15 Oct 2005 18:21:00 GMT

Honeslty, MSProject it's not my favorite tool to track software development projects (or at least the kind of projects where I use to work).

I agree Mr Spolsky about his opinion of the product, and I prefer Excel, and Shared lists to track project information. http://www.joelonsoftware.com/articles/fog0000000245.html

However, today I've found a new MSProject Add-In to create product-sprint backlogs, so I will try to learn new tips & tricks to use it in an agile way

http://msdn.microsoft.com/office/default.aspx?pull=/library/en-us/odc_pj2003_ta/html/OfficePJScrumToolSolStarter.asp?_r=1

Note that the Addin to create Excel charts is provided as VB6 source code with no binaries, so you must look for your old VB6 to build it.

PrinciplesOfObjectOrientedDesign

rido — Mon, 03 Oct 2005 13:50:48 GMT

Does everybody agree about the "Principles Of Object Oriented Design" ?

from: http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfObjectOrientedDesign

"…

The first five principles are principles of class design. They are:

SRP	The Single Responsibility Principle	A class should have one, and only one, reason to change.
OCP	The Open Closed Principle	You should be able to extend a classes behavior, without modifying it.
LSP	The Liskov Substitution Principle	Derived classes must be substitutable for their base classes.
DIP	The Dependency Inversion Principle	Depend on abstractions, not on concretions.
ISP	The Interface Segregation Principle	Make fine grained interfaces that are client specific.

The next six principles are about packages. In this context a package is a binary deliverable like a .jar file, or a dll as opposed to a namespace like a java package or a C++ namespace.

The first three package principles are about package cohesion, they tell us what to put inside packages:

REP	The Release Reuse Equivalency Principle	The granule of reuse is the granule of release.
CCP	The Common Closure Principle	Classes that change together are packaged together.
CRP	The Common Reuse Principle	Classes that are used together are packaged together.

The last three principles are about the couplings between packages, and talk about metrics that evaluate the package structure of a system.

ADP	The Acyclic Dependencies Principle	The dependency graph of packages must have no cycles.
SDP	The Stable Dependencies Principle	Depend in the direction of stability.
SAP	The Stable Abstractions Principle	Abstractness increases with stability.

…"