Re-fix some confusing cases

Author: hazzik

src/NHibernate.Test/SystemTransactions/DistributedSystemTransactionFixture.cs

@@ -539,10 +539,11 @@ public void CanUseSessionOutsideOfScopeAfterScope(bool explicitFlush)
 				}
 				var count = 0;
 				Assert.DoesNotThrow(() => count = s.Query<Person>().Count(), "Failed using the session after scope.");
-				if (count != 1)
+				const int expectedCount = 1;
+				if (count != expectedCount)
 					// We are not testing that here, so just issue a warning. Do not use DodgeTransactionCompletionDelayIfRequired
 					// before previous assert. We want to ascertain the session is usable in any cases.
-					Assert.Warn($"Unexpected entity count: {count} instead of 1. The transaction seems to have a delayed commit.");
+					Assert.Warn($"Unexpected entity count: {count} instead of {expectedCount}. The transaction seems to have a delayed commit.");
 			}
 		}
 

src/NHibernate.Test/SystemTransactions/SystemTransactionFixture.cs

@@ -284,10 +284,11 @@ public void CanUseSessionOutsideOfScopeAfterScope(bool explicitFlush)
 				}
 				var count = 0;
 				Assert.DoesNotThrow(() => count = s.Query<Person>().Count(), "Failed using the session after scope.");
-				if (count != 1)
+				const int expectedCount = 1;
+				if (count != expectedCount)
 					// We are not testing that here, so just issue a warning. Do not use DodgeTransactionCompletionDelayIfRequired
 					// before previous assert. We want to ascertain the session is usable in any cases.
-					Assert.Warn($"Unexpected entity count: {count} instead of 1. The transaction seems to have a delayed commit.");
+					Assert.Warn($"Unexpected entity count: {count} instead of {expectedCount}. The transaction seems to have a delayed commit.");
 			}
 		}