This is another experiment with longer posts. Previously, I used the time series example as the bed on which to test some ideas regarding feature design, to explain how we work and in general work out the rough patches along the way. I should probably note that these posts are purely fiction at this point. We have no plans to include a time series feature in RavenDB at this time. I am trying to work out some thoughts in the open and get your feedback. At any rate, yesterday we had a request for Cassandra style counters at
the mailing list. And as long as I am doing feature design series, I thought that I could talk about how I would go about implementing this. Again, consider this fiction, I have no plans of implementing this at this time. The essence of what we want is to be able to… count stuff. Efficiently, in a distributed manner, with optional support for cross data center replication. Very roughly, the idea is to have “sub counters”, unique for every node in the system. Whenever you increment the value, we log this to our own sub counter, and then replicate it...(Read whole news on source site)
Software Release Version 3.1.0 knockout/knockout - Steve Sanderson announces the 3.1 release of KnockoutJS, introducing a number of performance, stability and compatibility improvements. Upcoming .NET NuGet Releases - Richard Lander gives an update on the next pre-release NuGet set of releases from the Core .NET Framework team Information Repositories On Top UnitOfWork Are Not a Good Idea [...]
Test doubles are objects that replace the dependent-on-component (DOC) in a test context so that the system under test gets an API as the real DOC and can perform activities against the API thinking that it is a real one!!!
There are different variations in the type of test doubles depending on the intent and context of usage. Ref: Test double patterns at XUnitPatterns.com.
In this post I’ll demonstrate the usage of the four main test doubles (Dummy, Fake, Stub and Mock) in the context of Microsoft Fakes and scenarios on how they can be implemented in your projects to
enhance code coverage. All the definitions for the patterns are copied from Gerard Meszaros XUnitPatterns catalog.
Dummy: A dummy is an object that is passed as a method argument or used as an attribute in a test context but never actually used. Usually they are just used to fill parameter lists.
var dummyCustomer = new StubCustomer();
var sut = new Invoice(dummyCustomer);
var book = new Product("XUnitPatterns");
var actual = sut.GetAllLineItems();
Assert.IsTrue(actual.Count() == 1);
Dansk IT afholder konferencen “Financial Tech Hub”, der sætter fokus på trends i IT-udvikling i den finansielle verden. Til konferencen har jeg fået lov til at tale lidt om “Design og brugeroplevelse til apps”. Der ligger en en masse muligheder netop indenfor den finansielle verden, som jeg glæder mig til at tale om. Læs mere […]
Map · Chapter 9: Creating an Augmented Reality App · Chapter 10: Creating a Templatable Compass Control · Chapter 11: Cross Platform Development
Download the book · Lulu.com · Direct download (pdf, 17MB)
Code sample Code samples for the book can be downloaded here....(Read whole news on source site)