Fixtures / Runner.CallMethod
Hi, I would like to implement fixtures for my tests, that is, I want to initialise (reset and start) some things, then run a set of tests, then tear it down (clean up and close). I was thinking...
Forum Discussion
Hello Robert,
Thank you for your very quick response. I did think about data driven testing, but I think in our case it would be hard to apply. For each run, we restore a database from file, start the application, then perform different tasks (different access paths and settings through menus and different dropdown boxes and whatnots) that can vary widely between tests, and then close the application. What is common is that the database needs to be restored between each test. If you still think we could benefit from some kind of DDT, please do tell me and I will investigate it further.
About aqObject.CallMethod, I tried to grasp how to use it, but to little avail. Currently I have each test case in its own test unit, with a method I call 'Run' that runs the test. Would I somehow wrap this in a class and instantiate that?
If you have any hints on this, I would be grateful.
Thank you again,
Johan
Thank you for your very quick response. I did think about data driven testing, but I think in our case it would be hard to apply. For each run, we restore a database from file, start the application, then perform different tasks (different access paths and settings through menus and different dropdown boxes and whatnots) that can vary widely between tests, and then close the application. What is common is that the database needs to be restored between each test. If you still think we could benefit from some kind of DDT, please do tell me and I will investigate it further.
About aqObject.CallMethod, I tried to grasp how to use it, but to little avail. Currently I have each test case in its own test unit, with a method I call 'Run' that runs the test. Would I somehow wrap this in a class and instantiate that?
If you have any hints on this, I would be grateful.
Thank you again,
Johan
