Sometimes you've just got to deploy

Sun, 16 Oct 2016 18:44:00 +0100

Sometimes the deadline has arrived and you still have some failing tests. After a discussion with the dev team, you decide to deploy anyway and fix the bugs for the next release. You need to get the build server to ignore the tests.

One way is just to mark the test with the [Ignore] attribute.

1
2
3
4
5
6


[Test]
[Ignore] // TODO: Fix this test before the next release!
public void Test()
{
 // Some failing test code...
}

After the weekend, everyone forgets about the ignored tests and they never get fixed.

Testing the property signatures of DevExpress validation rules using NUnit and LINQ

Thu, 24 May 2012 16:39:00 +0100

One of the projects I work on uses the validation module of the eXpressApp Framework (XAF). Since the business logic is complex, there are many validation rules defined using the [RuleFromBoolProperty].

One of the recurring problems occurs when the signature of the associated property is incorrect. Consider the following:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11


[RuleFromBoolProperty("Invoice_IsAmountGreaterThanZero", 
 DefaultContexts.Save, 
 "Invoice amount must be greater than zero.", 
 UsedProperties = "Amount")]
public bool IsAmountGreaterThanZero
{
 get
 {
 return Amount > 0;
 }
}

Notice that the rule is declared public. This causes the getter to be executed when it is not required (see the note in the documentation). However another problem is that the default behaviour for public properties of XPObjects is to persist them to the datastore which means the application will attempt to create a new column called IsAmountGreaterThanZero.

Nunit on ZeroSharp

Sometimes you've just got to deploy

Testing the property signatures of DevExpress validation rules using NUnit and LINQ