#1113: Testing Framework Limitations
---------------------+------------------------------------------------------
Reporter: jake | Owner: felix
Type: defect | Status: assigned
Priority: high | Milestone: 1.0.2
Component: testing | Version: 1.0.1
Severity: normal | Keywords:
Has_patch: 0 |
---------------------+------------------------------------------------------
Changes (by felix):
* status: new => assigned
Comment:
I'll go look into the assertions, I'm pretty certain they did work at some
point. I guess we need testcases for the testing subsystem. However,
everything in the testing system is pretty alpha so a certain caution
while using is advised.
I don't think that doing a full dispatch and capturing the output is the
right way to solve this. That actually duplicates what the current flow-
test does and it introduces a ton of new variables in the testing harness
- there'd be the action, all action and global filters... The intended use
for the view-test is to test a view, isolated from any other framework
component (well, as far as that's possible).
The directory structure issue could best be solved by not messing with any
absolute path. You could then specify
%core.module_dir%/path/to/your/module/tests/TestFile.php as path. This
solution is more flexible than allowing for a module parameter - it covers
libraries with own tests as well as any other test location you'd prefer.
It also requires less extra code to handle, so that's probably the best
way to go.
--
Ticket URL: <http://trac.agavi.org/ticket/1113#comment:1>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
