See also bug #538070 and the Parameterized Tests blueprint at
https://blueprints.launchpad.net/nunit-3.0/+spec/parameterized-tests.
Creation of static test cases is done at the time of loading the test,
so it's not merely a question of order - it's done only once per load
rather than once per test run.
Dynamic test cases will not exist until the test is run and we'll make
sure in the implementation that TestFixtureSetUp can influence the
creation of the tests.
** Changed in: nunit-3.0
Status: New => Triaged
** Changed in: nunit-3.0
Importance: Undecided => High
--
TestCaseSource and TestFixtureSetUp
https://bugs.launchpad.net/bugs/664018
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
Status in NUnit Test Framework: Triaged
Bug 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. ;-)
_______________________________________________
Mailing list: https://launchpad.net/~nunit-core
Post to : nunit-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nunit-core
More help : https://help.launchpad.net/ListHelp
