You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading about bugs and other issues here and on the mailing list, I see that it's common when the problem, being fixed in one version, comes back two versions later to bite developers in the ass. So I'd like to propose that we have integration tests - that means going all the way from configuring the mapping to creating ISessionFactory/ISession and doing some basic operations.
I think this can grant us at least two things -
a) bugs won't come back, or at least, these situations will pop up with less frequency
b) we'll be able to pin point the problems when upgrading to future versions of NH
Any thoughts? Of course such goal can't be accomplished in a month, that's a long term investment.
What's more interesting about it - I think we can even turn some current unit-tests into integration tests by adding code to [TestFixtureTearDown] method.
The text was updated successfully, but these errors were encountered:
I agree this is a good long-term goal. My team is just getting started with FNH, so likely will not be able to help very soon, but we do want to eventually contribute.
After reading about bugs and other issues here and on the mailing list, I see that it's common when the problem, being fixed in one version, comes back two versions later to bite developers in the ass. So I'd like to propose that we have integration tests - that means going all the way from configuring the mapping to creating ISessionFactory/ISession and doing some basic operations.
I think this can grant us at least two things -
a) bugs won't come back, or at least, these situations will pop up with less frequency
b) we'll be able to pin point the problems when upgrading to future versions of NH
Any thoughts? Of course such goal can't be accomplished in a month, that's a long term investment.
What's more interesting about it - I think we can even turn some current unit-tests into integration tests by adding code to [TestFixtureTearDown] method.
The text was updated successfully, but these errors were encountered: