NUnit Framework

  1. Bug #664018
  2. Activity log

Activity log for bug #664018

Date Who What changed Old value New value Message
2010-10-20 16:49:44 Rechenelf bug added bug
2010-10-20 16:50:27 Rechenelf description Obviuosly, the current implementation is the following: - First, the Properties which are used for TestCaseSource are asked (static or not) - Then the methods attributed with TestFixtureSetUp are called. - Then test startup is done and the test called. It is possible to change the first two steps? The current behaviour is a problem for us. Because the property for the TestCaseSource should have some data from the database which the Connection is established in FixtureSetUp. The parameter vor the database, username, password and so on are set in the constructor of the class. Now, I have hacked they in manually. This is not quite a nice way. ;-) Obviously, the current implementation is the following: - First, the Properties which are used for TestCaseSource are asked (static or not) - Then the methods attributed with TestFixtureSetUp are called. - Then test startup is done and the test called. It is possible to change the first two steps? The current behaviour is a problem for us. Because the property for the TestCaseSource should have some data from the database which the Connection is established in FixtureSetUp. The parameter vor the database, username, password and so on are set in the constructor of the class. Now, I have hacked they in manually. This is not quite a nice way. ;-)
2010-10-20 18:34:16 Charlie Poole nunit-3.0: status New Triaged
2010-10-20 18:34:18 Charlie Poole nunit-3.0: importance Undecided High
2011-12-11 06:21:48 Charlie Poole tags framework
2012-01-16 21:08:03 Charlie Poole tags framework feature framework
2013-10-19 02:30:07 Charlie Poole tags feature framework github
2013-10-19 02:30:34 Charlie Poole description Obviously, the current implementation is the following: - First, the Properties which are used for TestCaseSource are asked (static or not) - Then the methods attributed with TestFixtureSetUp are called. - Then test startup is done and the test called. It is possible to change the first two steps? The current behaviour is a problem for us. Because the property for the TestCaseSource should have some data from the database which the Connection is established in FixtureSetUp. The parameter vor the database, username, password and so on are set in the constructor of the class. Now, I have hacked they in manually. This is not quite a nice way. ;-) [Issue now tracked at https://github.com/nunit/nunit-framework/issues/7] Obviously, the current implementation is the following: - First, the Properties which are used for TestCaseSource are asked (static or not) - Then the methods attributed with TestFixtureSetUp are called. - Then test startup is done and the test called. It is possible to change the first two steps? The current behaviour is a problem for us. Because the property for the TestCaseSource should have some data from the database which the Connection is established in FixtureSetUp. The parameter vor the database, username, password and so on are set in the constructor of the class. Now, I have hacked they in manually. This is not quite a nice way. ;-)