Simon JAILLET

It's possible to skip specific files but not a specific function. What is the motivation behind trying to ignore the code coverage for some functions ?

Would definitely be a must have :+1: Since the DSL functions can't be loaded through the composer files entry (to avoid collision), they are dynamically created [right there](https://github.com/kahlan/kahlan/blob/f28d97e268c1fd5054280932b880e06417eddb6f/src/Cli/Kahlan.php#L646) and unfortunately...

Hello @ezzatron, were you able to find some compatible configuration with Kahlan on this topic ?

Hi, You're totally right about your hypothesis. Indeed executed files are in the `sys_get_temp_dir()` so I guess your breakpoints should be setted on the files there. It's indeed not ideal...

I agree `markTestIncomplete` can be handled with `xdescribe()`. In regards to `Mocha` & `Rspec`, for them skip as the same meaning as `xit` of `xdescribe`. To actually "skip" a test...

nope !

The previous behavior didn't respect the separation of concerns. Imo this "PHP ambiguity issue" should be managed by the Model class. Why not overriding `Model::__call` in your base model class...

Hi @nateabele, sorry for the delay. Indeed I thought to a plugin which works using a specific naming convention for its controller's action (like the 'Action' suffix (convention used by...

If plugins are allowed to enable their own `admin_*()` methods, indeed rules need something like a "scope" but with something like: ``` Dispatcher::rules('app', array( 'admin' => array('action' => 'admin_{:action}') ));...

Just adding a comment here to get notifications about this issue since I'm also interested about this concern. Indeed we already [had a debate around it](https://github.com/kahlan/kahlan/issues/146) but we didn't find...