Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,124 | Comments: 45,483

filter by tags archive

Test refacotring

time to read 3 min | 404 words

I just posted about a horribly complicated test, I thought I might as well share the results of its refactoring:

public class IndexedEmbeddedAndCollections : SearchTestCase
	private Author a;
	private Author a2;
	private Author a3;
	private Author a4;
	private Order o;
	private Order o2;
	private Product p1;
	private Product p2;
	private ISession s;
	private ITransaction tx;

	protected override IList Mappings
			return new string[]

	protected override void OnSetUp()

		a = new Author();
		a.Name = "Voltaire";
		a2 = new Author();
		a2.Name = "Victor Hugo";
		a3 = new Author();
		a3.Name = "Moliere";
		a4 = new Author();
		a4.Name = "Proust";

		o = new Order();
		o.OrderNumber = "ACVBNM";

		o2 = new Order();
		o2.OrderNumber = "ZERTYD";

		p1 = new Product();
		p1.Name = "Candide";
		p1.Authors.Add(a2); //be creative

		p2 = new Product();
		p2.Name = "Le malade imaginaire";
		p2.Orders.Add("Emmanuel", o);
		p2.Orders.Add("Gavin", o2);

		s = OpenSession();
		tx = s.BeginTransaction();

		tx = s.BeginTransaction();


	protected override void OnTearDown()
		// Tidy up
		s.Delete("from System.Object");




	public void CanLookupEntityByValueOfEmbeddedSetValues()
		IFullTextSession session = Search.CreateFullTextSession(s);

		QueryParser parser = new MultiFieldQueryParser(new string[] { "name", "authors.name" }, new StandardAnalyzer());

		Lucene.Net.Search.Query query = parser.Parse("Hugo");
		IList result = session.CreateFullTextQuery(query).List();
		Assert.AreEqual(1, result.Count, "collection of embedded (set) ignored");

	public void CanLookupEntityByValueOfEmbeddedDictionaryValue()
		IFullTextSession session = Search.CreateFullTextSession(s);
		TermQuery  query = new TermQuery(new Term("orders.orderNumber", "ZERTYD"));
		IList result = session.CreateFullTextQuery(query).List();
		Assert.AreEqual(1, result.Count, "collection of untokenized ignored");
		query = new TermQuery(new Term("orders.orderNumber", "ACVBNM"));
		result = session.CreateFullTextQuery(query).List();
		Assert.AreEqual(1, result.Count, "collection of untokenized ignored");

	public void CanLookupEntityByUpdatedValueInSet()
		Product p = s.Get<Product>(p1.Id);

		QueryParser parser = new MultiFieldQueryParser(new string[] { "name", "authors.name" }, new StandardAnalyzer());
		IFullTextSession session = Search.CreateFullTextSession(s);
		Query query = parser.Parse("Proust");
		IList result = session.CreateFullTextQuery(query).List();
		Assert.AreEqual(1, result.Count, "update of collection of embedded ignored");


It is almost the same as before, the changed are mainly structural, but it is so much easier to read, understand and debug.



Instead of cleaning up using deletes, why don't you just rollback the transaction?


And replacing tx.Commit with s.Flush(); s.Clear(); in your tests

Benny Thomas

I'm missing the factory method for Author, Order and Product.

Ayende Rahien


What you don't see here is that there are transaction syncronizations going on behind the scene to sync the index.

I have to use tx.

Ayende Rahien


Not worth it, this is not a test for an application, this is a test for NH Search, so we have LOTS of stuff like that

Jonathan Allen

So instead of a single test you can easily follow you have a tangle of implied function calls.

And what if one of those implied calls, say "OnSetUp" fails? Do you get bombarded with false positives or does it just silently ignore your tests?

And what if you want a different setup? Do you have to build a whole new class for each data scenario?

The original test wasn't perfect, but this new one seems to be both over engineered and inflexible at the same time.

Benny Thomas

@Ayende: I know it's not worth it, but it is good practice. And this is codesmell and people who wan't to learn what happens behind the scene will get a nearly Kobe feeling ;)

The power of example.

Frank Quednau

Finally a prominent proponent for PascalCasedTestNames. Allthisunderscoreseparationisgettingoutofhand! ;)

Victor Kornov

@Frank Quednau

I'd say that's naming convention in NH which Oren just follows.

John Simons

Not sure if it's intentional or not but you may want to fix the spelling mistake "Refactoring" Cheers John

Ciaran Jessup

I notice in your OnTearDown you're deleting every mapped thing in your NHibernate Configuration, which means (unless I'm mistaken, which I could well be) that if there was any data in there that was global reference data that was shared by all tests it would be blown away.

I've always been told to strive for Idempotence in my tests so would traditonally have just removed what I created in my setup, am I wasting my time with this approach ?

In a non-trivial test where you can setup the entire database as you need it in your setup then I guess its ok to do this each time, but when you're running hundreds or thousands of tests over a complex system that has data that has a lot of shared reference values that would slow the tests down quite a lot I think ?

Ayende Rahien


The lack of context is tripping you.

In fact, I am blowing away the database schema each time I run the test.

Ciaran Jessup

Interesting, does this not slow down your tests a lot ?

Ayende Rahien


a) no

b) you haven't asked what I am testing, this is part of the NH Search test suite

Ciaran Jessup

I didn't mean to cause offence, was just interested! And i'll take your word for it then :)

Comment preview

Comments have been closed on this topic.


  1. RavenDB 3.5 whirl wind tour: I’ll find who is taking my I/O bandwidth and they SHALL pay - 3 hours from now
  2. The design of RavenDB 4.0: Physically segregating collections - about one day from now
  3. RavenDB 3.5 Whirlwind tour: I need to be free to explore my data - 2 days from now
  4. RavenDB 3.5 whirl wind tour: I'll have the 3+1 goodies to go, please - 5 days from now
  5. The design of RavenDB 4.0: Voron has a one track mind - 6 days from now

And 12 more posts are pending...

There are posts all the way to May 30, 2016


  1. RavenDB 3.5 whirl wind tour (14):
    02 May 2016 - You want all the data, you can’t handle all the data
  2. The design of RavenDB 4.0 (13):
    03 May 2016 - Making Lucene reliable
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats