This is my suspicion: stackoverflow.com/.../nunit-assert-equals-what-...

Reflector tells me that you are not using nunit but xunit and that xunit does not do a reference comparison in Assert.Equals which I hat expected.

Second guess: you have to call SaveChanges.

< should be <= ?

Not calling session.SaveChanges() ?

My guess: You already have a value in the DB with a value about 1.331m?

@configurator: the first line in the tests creates a fresh db

I don't have 2 hours, sorry, but maybe something wrong with Range indexing for decimal values (i.e. in your Where (x=> x.M ...) )? Cast or something? As far as I remember Db create 2 indexes, maybe it use wrong one and you get not correct result? ;-)

You set up your test using float and decimal. I remember from somewhere (maybe the first time I've actually put an MS certification into use) that float is stored as binary and should not be used in situations where you need to verify equality on large numbers.

Needs more round trips to the server

Either decimal will accurately represent 1.33 and so your 1.331 comparison will fail, or you need to use a tolerance value for comparison, like absolute value of val - 1.33 > 0.01?

Hmm, there's nothing wrong with the comparison & data types, unless there's something odd with the unit test framework you're using. (I've verified the behaviour of the data type comparisons with NUnit.)

I don't know much about RavenDB but my guess would be that you haven't told it to retrieve the data, there is no Select or SelectFields, so would the Linq2Object .Where() condition have anything to search through?

The session.Store() does nothing until the session ends. So session.Query() will never find anything because it is not stored yet.

Wrapping session.Store() in its own session, and 2x session.Quer() in another will pass the test.

Or does calling session.Query() flush first?

@Alwin, @Thomas Freudenberg etc - I think its not necessary to call session.SaveChanges() due to usage of WaitForNonStaleResults, or?

My another attempt: maybe you forgot to do initialization (i.e. say documentStore.Initialize();) in NewDocumentStore() method that you forgot to show here as well :D

But still I feel that something wrong with Where(...) and decimal values like from my previous comment :)

Common, Ayende, let us know issue that you spend 2 hours :)

I assume that if you spend 2 hours debugging it, it's simply not so easy to found such bug in just few minutes that most of us have :D

ha ha ha :D Nice that such things happens not only with me :D

P.S. I was think that WaitForNonStaleResults should actually do promote changes in context into database for given index... i.e. it's little bit confusing to wait for index to updated in storage with fact that you still have some documents in memory that not yet added to index......