This time, the turn is for Testing.Commons to find a new home and, again, as with NMoneys, such home will be GitHub.
JSON has become one of the most widely accepted data interchange/representation formats. Not only as a Web data interchange, but also as data representation of multiple document databases.
It’s rare these days to have a mostly free evening to look after some OSS.
A new sibling has joined of the Testing.Commons family. Testing ServiceStack services I have reviewed, worked (and presented) extensively on ServiceStack lately. With work done comes testing your work. And I found ServiceStack to require little plumbing to do integration tests. But there is some. And there, Testing.Commons.ServiceStack can help with your integration tests. Low barrier testing Create a class library project Install ServiceStack nuget package (the latest free version): Install-Package ServiceStack -Version 3.9.71 Install Testing.Commons.ServieStack nuget package: Install-Package Testing.Commons.ServiceStack Create a test that inherits from either SingleHostPerFixture or SingleHostPerTest Happy testing! More? Go to the documentation page for guidance or, better yet, project’s automated tests.
Get your best clothes ready and put your finest underwear on. NUnit 2.6.3 is here. Testing.Commons And with it, a newest version of Testing.Commons. There are no new features. Well, unless support for the latest version of NUnit is not considered a feature, which, for this type of package, it is.So there is. Enjoy it. Runners on a diet. Of course, those who use it (me, for instance) can benefit from my slimmed down package of test runners: NUnit.Runners.lite, updated with the latest binaries from NUnir.Runners.
That is an enigmatic title to write about serialization. Well, sort of, as one of the meanings of the word refers to that concept. But writing about successions is not my intention. My intention is to write about the technique that allows objects to be persisted to another medium different from their native memory space and more specifically on how to test serialization of objects.
The other day I read an interesting post about testing and a library that might help in some cases, its title is “Introducing the Expected Objects” library. I thought it might be useful and so I spent a spare evening writing some code to check whether is something that could be useful for my team. The Problem Imagine you are […]
Let’s throw a party! A Big Gap Wait a second? Last release was 0.4.0.0, when stuff to test the profile system was added. “Either you have been terribly busy or you are tricking us.” Well, more of the latter if you check the amount of code of the deltas committed. In reality my plan was to go 1.0 when all the code I previously had was ported. It turned out to be less than I thought as I trimmed out some parts I cannot use and clipped redundancies.
Configuration in enterprise application is a fact of life. My take on it is as follows: delay it as late as possible and hard-code in anger until someone asks for a change. Then, accepting the fact that is likely to happen again, the value is pushed into configuration. Configuration can be as simple as a collection of key-value pairs. But sometimes, configuration needs to be more complex than key-value pairs; just imagine some sort of hierarchical structure or a simple collection of related values.