http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660If you are using NUnit and making the names long to give a better description, you might want to consider using the Description attribute instead. This way you can keep your method names a little more succint and still give a decent error message in the output on failure http://nunit.com/index.php?p=description&r=2.4.1 http://ayende.com/2492/debugging-nhibernate#comment3http://ayende.com/2492/debugging-nhibernate#comment3Tue, 05 Jun 2007 14:35:40 GMT...Or you can break the name in a subclass/method pair. Even better if you find commonalities: [TestFixture] public class CanMakeCriteriaQueryAcrossBothAssociations { [Test] public void WhenSomePreconditionHappens1() { } [Test] public void WhenSomePreconditionHappens2() { } } http://ayende.com/2492/debugging-nhibernate#comment2http://ayende.com/2492/debugging-nhibernate#comment2Mon, 04 Jun 2007 19:54:16 GMTThere is a point at which comments once again become more useful than method names!!!!! http://ayende.com/2492/debugging-nhibernate#comment1http://ayende.com/2492/debugging-nhibernate#comment1Mon, 04 Jun 2007 14:43:38 GMT