D
DenDuze
Guest
Hi Phani, I can't answer that ;-) I'm not so familiar with UnitTesting but I find it interesting. What I want to do is to always prepare a DB with all expected records in my tests. Then run the tests with the needed for each-statements for the specific tests. I expected then to see how many calls of a specific tests failed due to other result then expected. But I see that ABLunit always stops a test when the first failure in that test occurs and I was wondering if I can prevent that. example: I have a BL that adds 1 to the last number from an input value. this input string can be , , , , , .... So I would create a record for every possible combination Do a for each on these records and call for every record the test-method Check on Assert:Equals In that way I can check my BL on returning a expected value for all situations in 1 run. Now I need to create for every situation a @test-method and in that @test-method I need to find the record (or hardcode the input value), call the BL and check the result. I find that much overhead but OK if it must be done this way then it has to (I guess) Isn't there some way to keep running the same test (with other input) when a failure has occured and see the sum of all failures of that test? Thanks Didier
Continue reading...
Continue reading...