On Oct 30, 1:48 am, euromark <[email protected]> wrote: > One needs to get used to them, I guess. > My current problem is that exceptions jump out of the current method > if triggered. > > So in test cases for example not all tests get executed. > This can be a good thing. > But sometimes it would be better if it behaved like errors in 1.3 > > lets say we are testing an Inflector method. > And we use a testInflector() method and 10-20 asserts. > If the first one fails, all others won't even be triggered. What if > all would pass except the first one?
You are describing a bad test. > It would help to see them all at once. > > Or the other way around. > The first one fails - and it displays: 1 fail. (it used to display all > fails - like 14 fails). > Now we could make the false assumption that 13 of 14 pass... Why would you assume that. > At the beginning I didnt even notice that most of the asserts of some > test cases are not checked due to a single fail. > > Yes, I could make an own method for each and every assert. Don't do that. A test should test one specific case; not 20 similar cases that call the same method. > But I was kinda hoping that they can be adjusted to not jump out of > the current method... > at least for test cases this would help :) welll i doubt it. i think you are comparing simpletest (its so long since ive used it,does it do what you describe?) to phpunit without realizing - phpunit will stop the test as soon as it has failed, by any means. AD -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
