HunabKu

SharpTestsEx 1.0.0Beta : Satisfy your test

2009-12-25T15:43:00.002-03:00

SharpTestsEx 1.0.0 was released today. You can download it from here. More than few improvements, regarding some assertions and its failure message, and some internal refactoring, the mayor change is about the “satisfier”. To talk about the syntax of the satisfier is something hard basically because there is no syntax. From user side of view, using the satisfier, the assertion is a simple and

SharpTestsEx Alpha1: MsTests Extensions

2009-08-07T03:11:00.003-03:00

#TestsEx is a set of extensible extensions to work with MsTests. The main target is write short assertions where the Visual Studio intellisense is your guide. The story In the lasts two days I remembered why I’m not using MsTests. When I began working with VisualStudio, was using the Express edition that does not have the MsTests suite. One of my customer wants use MsTests because “it is fully

#TestsEx: who was born first the chicken or the egg?

2009-08-08T17:54:00.003-03:00

I’m refactoring and improving #TestsEx. For serialization assertion I found that the message was not so clear if the actual value, under test, is null. So I wrote this new test before change framework code: [TestMethod]public void SerializableNullShouldThrowClearException(){ Seri actual = null; ActionAssert.Throws(()=> actual.Should().Be.BinarySerializable()) .

Developing #TestsEx

2009-08-15T21:05:00.003-03:00

I’m developing some new features in SharpTestsEx. This is the test: [TestMethod]public void GetMessage(){ var ass = new OrAssertion(new AssertionStub("Left message"), new AssertionStub("Right message")); var lines = ass.GetMessage(1, null) .Split(new[] {Environment.NewLine}, StringSplitOptions.None); lines.Should().Have.SameSequenceAs("(Left message)", "Or", "(

#TestsEx Apla2 was released

2009-08-12T18:11:00.003-03:00

Sharp Tests Ex Alpha2 was released today (download). In the wiki is now available the Syntax overview. One of the challenge of this version was rewrite all failure messages to magnify the cause of the failing test. Similar messages are available for all other assertions. The next step.Should().Be. the syntax for lambda based assertions as: const int y = 2;const int

Sharp Tests Ex 0.3.0 : fluent and lambda assertions for MsTests, NUnit and xUnit

2009-09-23T02:34:00.003-03:00

#TestsEx 0.3.0 was released yesterday. News The first news is that #TestsEx is no more a “one-man-show”; Jason Diamond is now part of the team. The second news is that the new syntax, based on lambda expression, is now available (similar to the one available in NUnitEx). You can see an example in the download page. var var2 = 2;2.Satisfy(a => var2 == a);1.Satisfy(a => a == 1 || a != 0);The

Refactorizing tests

2009-11-15T11:00:00.003-03:00

I had read, in some place on the cloud, that SharpTestsEx make the test more verbose even if it is more readable. In NHibernate.Validator (NHV) we are using #TestsEx. After implements some new features I’m improving some stuff where I’m needing a little breaking change. This is an existing test using classic NUnit syntax: [Test]public void CreditCard(){ CreditCard card = new CreditCard();

From DB to RAM: WellKnowInstanceType

2009-08-01T00:54:00.005-03:00

How many times we are putting something in DB even if it is not needed ? No one ? sure ? In these days I’m reviewing an application after four year rolling. I have checked the persistent states of some entities and they are in exactly the same state they was four years ago; why entities should not persist in compiled code ? The enum is a special kind of these entities. If the value of the enum

The GuyWire

2009-11-22T17:38:00.004-03:00

In a afternoon of July I was working refactorizing a web-project. We was using the XML configuration of Castle.Windsor and Santiago Leguiza asked me a way to simplify the configuration. The natural way to go is the configuration via Fluent-Interface. At that time my opinion about fluent-conf of the IoC was not so good because the fluent-conf needs references to each layer of the application. We

The .NET’s Attribute hole

2009-11-19T17:16:00.005-03:00

Reading this post try to imagine how much I have worked, with my code, before create a test to test the behavior of the class Attribute. Assertion In .Net an Attribute is a class as any other and may have state and behavior. True ? so and so… first of all, as class, it has some restriction as: it must inherit from System.Attribute and can’t be a generic class; second as any class it was

NHibernate.Validator: Tags

2009-11-17T20:21:00.005-03:00

At the begin of NHibernate Validator we have talked about the exigency of assign a “gravity level” to each validation (for instance Error, Warning, Information). In the last year we had requests for “validation grouping” and “different validation, for the same entity, in different contexts”. Our answer is: validation tagging What is a tag In NHibernate Validator a tag has de same meaning you are

MVP in web-Forms using Ajax

2009-11-12T20:02:00.004-03:00

As you probably know I’m not neither an UX nor UI guy and in general, since the last few years, I’m trying to stay far away from something called “view”. I’m involved in an existing Web-Forms project as consultant and sometimes as developer. The project has some years of active development and, although its success improves day by day, from the point of view of maintenance of some parts we have

Validation Abstraction: Custom

2009-11-02T19:00:00.001-03:00

If you have read this post you know I’m having some psychological problem at work: multi-personality. My dear friend Fabio-NHV said me: hey man! I have a very good OSS validation framework strongly recommended if you are validating entities you are using with NHibernate. And I said: Cool!! but your framework is only an option for me… soon or later I’ll use something else and, btw, I need to mix

Validation through persistence: not synchronized

2009-10-31T07:00:00.000-03:00

In this series you saw mostly the configuration of NHibernate.Validator through Loquacious (our configuration based on fluent-interface). What is the ValidationDef ? If you are using the Satisfier (validation through lambdas) the ValidationDef become the class whose responsibility is validate a instance of T. If you need some validation, involving the persistence, and you want do it through

Validation through persistence: synchronized

2009-10-30T07:00:00.000-03:00

This post is about one possible answer to the question mememem ask me in this post (ah… nice nick). The task is create a validator to validate the uniqueness, of an entity instance, using some properties’ values instead its POID (Persistence Object ID). The implementation public class BlogPost{ public string Title { get; set; } public DateTime Date { get; set; } public string Content {

NHibernate visual Class and mapping generator integrated with VisualStudio2010

2009-10-29T13:51:00.003-03:00

Do you remember this post ? Now Microsoft gave us a step-by-step guide : POCO Templates for the Entity Framework Fantastic!!! Now we need a good soul starting the integration with NHibernate to generate POCO and mappings. There will be a little difference: The POCO template generates Entities that supports change notification.

NHibernate.Validator & NHibernate

2009-10-29T07:00:00.001-03:00

The validation is defined as a classic cross cutting concern… well… if we are talking about that we need to validate something everywhere I can agree with that definition, but if we are talking about the validation of domain entities I don’t agree. The validation of a domain-entity shouldn’t happen in the persistence-layer nor in the presentation-layer and even less in the persistence itself.

NHibernate.Validator : Customizing messages (Message Interpolator)

2009-10-28T07:00:00.001-03:00

The message interpolator is the responsible of the messages translation/composition. In the coming soon version (NHV-1.2.0) we had increase its power (and refactorized its implementation). Has default NHV has two implementations: DefaultMessageInterpolatorAggregator and DefaultMessageInterpolator. What is the usual you have seen in NHibernate’s eco-system ? Yes, you are right: Injectability!!!

NHibernate.Validator : Customizing messages (bases)

2009-10-27T07:00:00.002-03:00

One of the most powerful feature of NHibernate.Validator is its way to manage messages. In this post are the bases of the massage customization. The Price In the last moth this blog was visited from 101 countries but NHibernate.Validator has only 8 translations. The available cultures are: en, es, it, fr, de, nl, lv, pl. Are you seeing the translation in your language ? you don’t ? What you

NHibernate.Validator : Extending ValidationDef

2009-10-26T05:00:00.006-03:00

In various applications I’m using my implementation of Range. public interface IRange : IEquatable> where T : IComparable{T LowLimit { get; }T HighLimit { get; }bool IsEmpty { get; }bool Includes(T value);bool Includes(IRange other);bool Overlaps(IRange other);}As you can imagine I’m using it to represent various kind of ranges and in each usage I need to validate the range

Advanced NHibernate.Validator

2009-10-21T02:21:00.008-03:00

Since long time ago I’m not writing posts about the usage of NHibernate.Validator. I wrote the post “Diving in NHibernate.Validator” because I saw some wrong examples, and even a wrong usage in another framework using NHV. Yesterday, talking with José Romaniello, I have realized how much poor is our documentation and how few are our examples. I have decided to begin a new series of posts on NHV

NHibernate.Validator : The “Satisfy” way of custom Validators

2009-10-24T07:00:00.000-03:00

The Satisfy (perhaps it sound familiar to some SharpTestsEx users ;) ). To show how it work the example is a constraint for Person.Name: a Name is significant when it has more than three characters, is composed by letters and the first letter is in uppercase. To create a that validator, in the classic way, we should create an Attribute implementing IRuleArgs and then a class implementing

NHibernate.Validator : Fine grained and polymorphic validation

2009-10-23T07:00:00.001-03:00

If you know that you can define constraints for classes, properties and even for field, what mean “Fine grained validation” ? In NHV, when you define a validator you are defining a validator for a System.Type… well… for real you can define a validator for various types but let me simplify the concept a little bit (parafrasando lo psico nano: “mi consenta”). In OOP the Type can be polymorphic

Improving ADO exception management in NHibernate

2009-06-16T14:58:00.003-03:00

When you working with NHibernate you may need to manage some specific situation where an exception is thrown by the RDBMS/DataProvider. For example you may need to do something specific for a “constraint violation”, to manage a “deleted object” or a stale-object-state but generated by RDBMS (because isolation level for example).. and so on. All those ADO.NET exceptions are catch and wrapped, in

NHibernate.Validator : Extending Loquacious configuration

2009-10-22T07:00:00.002-03:00

The needs to extend the configuration come when you having some custom and reusable validators. For this post I will use a constraint to solve : if a string property is null or empty it is valid, but if it is not empty it must satisfy the minimal required number of characters. Creating the Validator The first step is create a class to hold the information needed during validation; in this case