Just Coding : Code

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)

Debugging VB6 code with Visual Studio 2008

rido — Mon, 05 Oct 2009 15:54:29 GMT

I was reviewing an old DNA app (more on this in a different post) and I got really surprised when I saw that we can debug VB6 code with VS2008 !!!...(read more)

RidoCode

rido — Wed, 26 Sep 2007 12:03:00 GMT

Since gotdotnet is phased out, I'm moving all my samples to codeplex ( http://www.codeplex.com/ridocode ), including the famous FileRollerTraceListener...(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)

Mocking SQLException

rido — Sun, 26 Nov 2006 16:30:12 GMT

I'm working on a presentation about Testing, and one of the technics I would like to show is MockObjects. One of the mock objects I want to create is a DataAccess Layer, and this one should throw SqlExceptions, however the SqlException class is sealed...(read more)

Some workaround for ObjectDataSource: could not find a non-generic method '...'

rido — Thu, 07 Sep 2006 23:04:12 GMT

Today I was playing with the new DataBind capabilities of ASP.Net 2.0, and found this error.. here are some links to possible solutions Link to Some workaround for ObjectDataSource: could not find a non-generic method '...'...(read more)

The Future of Programming Languages

rido — Mon, 21 Aug 2006 15:32:28 GMT

Two years ago I wrote about "The Future of Programming" bercause it was the keynote at OOPSLA04. I found a nice presentation from VSLive! Toronto 2006 where Lohn Lam talks about RUBY as an example of a language of the future (with lessig style) Link to...(read more)

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>

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.

…"

MockObjects again

rido — Wed, 28 Sep 2005 15:58:00 GMT

Finally my article about TDD, MockObjects and Dependency Injection is updated to this new URL:

http://msdn.microsoft.com/es-es/library/bb932285.aspx

It's in Spanish, but the sample code is English readable !!

I'm waiting for your feedback.

Unit Test Rules

rido — Wed, 21 Sep 2005 13:05:01 GMT

Michael Feathers has posted a set of Unit Tests Rules http://www.artima.com/weblogs/viewpost.jsp?thread=126923

he said:

A test is not a unit test if:

It talks to the database

It communicates across the network

It touches the file system

It can't run at the same time as any of your other unit tests

You have to do special things to your environment (such as editing config files) to run it.

I understand his motivations to write this, however I think his position is very aggressive. Frankly, I have learned UnitTests reading tests from other people, and I've always seen some kind of dependencies with the Filesystem and sometimes a Database, and I don't think this makes these tests less Unit.

I would like to reconsider each of first three points:

It talks to the database.

use different db for unit and integration testing
the database can be created from scratch easily
tests uses the smallest amount of data they could
unit tests always execute though a local db instance

It communicates across the network

I always avoid to depend in another machine, so if you need to use the network always use localhost, and like the db, you must be able to setup the server side easily in your dev/build box.

It touches the file system

I completely disagree this one, it's like if you said "it touches the memory". I don't like to depend on predefined paths and I always try to put my testfiles as resources of my test library, however there are too many situations where using the FS make things easier.

Finally I agree with the last two sentences…

How to learn Design Patterns

rido — Sat, 03 Sep 2005 20:35:00 GMT

Jeremy D. Miller talks in his blog about how to learn and apply Design Patterns.

http://codebetter.com/blogs/jeremy.miller/archive/2005/09/01/131509.aspx

I completely agree with his ideas, however I've been in frustrating situations when you come to an existing project, and you want to apply patterns, If the product is working ¿how do you convince to Project Managers how important is a well-design to a long term solution?

In my experience, PMs only cares about milestones, calendars, and maybe features (they don't care how well designed it is), or better if the customer feels like if the feature is completed, without any quality measurement.

I love design patterns, and I would like to improve my knowledge about them to be a better developer. I think every good programmer agree with me.

But what we need to learn is "how to teach" the importance of design patterns to Project Managers.

Look at this code !!

rido — Thu, 01 Sep 2005 21:50:00 GMT

At the beginning of this blog I started to submit intersting URL, or sites I don't want to forget.

Since I discovered Del.Icio.Us (social bookmark manager) I just post my new links there, but today I've found a blog dedicated to the most horrible code sinppets you've never seen.

http://thedailywtf.com

Have fun...