michael_morris1 — 2013-05-16T08:31:01-04:00 — #1
I've been through this thing a dozen times now - at no point does it explain how to actually run a test. What's the bloody point of writing a test if running it is never explained?
cpradio — 2013-05-16T08:34:53-04:00 — #2
fretburner — 2013-05-16T09:18:02-04:00 — #3
This section of the manual deals with running tests from the command line: http://phpunit.de/manual/3.7/en/textui.html
salathe — 2013-05-16T17:13:11-04:00 — #4
Michael Morris: Worst Ability-To-Find-What-Is-Right-Under-Your-Nose Ever. (:
lemon_juice — 2013-05-16T17:43:35-04:00 — #5
I've found that at the beginning it's easiest to run tests from an IDE that supports PHPUnit. Recently, I set up Netbeans to run tests and it was super easy plus the test files with classes and method definitions were created for me automatically by the Skeleton Generator. Now I can run tests by using a menu item or a shortcut in Netbeans. Other IDE's should have similar support, I suppose.
However, I know there are people who will swear that command line rules!
michael_morris1 — 2013-05-16T18:27:20-04:00 — #6
I have a severe cold and at the time that was posted I was running a temperature of 101. I plead infection induced dementia your honor. (I was reading the PHP Unit manual on my ipad in bed, too weak to sit upright and type at length).
michael_morris1 — 2013-05-17T16:35:58-04:00 — #7
Ok, is there a way to chain tests together rather than run them one at a time? (Each test hits one class or a tight group of classes, but I'd like to be able to test the whole system).
salathe — 2013-05-17T17:31:02-04:00 — #8
michael_morris1 — 2013-05-17T18:22:14-04:00 — #9