*much* snarkier than I intended. Rest assured, I've
asked questions the same way many times in the past in a number of
public forums, and been told pretty much the same thing: give us code,
and give us a detailed description.
Kind Regards,
Brian Wisti
http://coolnamehere.com/
--~--~
constants.
Now that everything is basically working as advertised, it looks like
I'm going to experiment with the ModelUnitTestCase class at
http://cakephp.org/pastes/show/99b95734fbb3b5a90d9b20adbc381aa9 to
streamline the test database interaction.
Kind Regards,
Brian Wisti
http://coolnamehere
constants.
Now that everything is basically working as advertised, it looks like
I'm going to experiment with the ModelUnitTestCase class at
http://cakephp.org/pastes/show/99b95734fbb3b5a90d9b20adbc381aa9 to
streamline the test database interaction.
Kind Regards,
Brian Wisti
http://coolnamehere
7;ve already seen and dealt with a
similar error. I think it just needs a DS wedged in there.
Still, if anybody can offer a better way to test my models, I'd be
grateful.
Kind Regards,
Brian Wisti
http://coolnamehere.com/
--~--~-~--~~~---~--~~
You received t
ne 144
Now, I did have to define CORE_PATH in app/tests/tests.php
if (!defined('CORE_PATH')){
define('CORE_PATH', ROOT.DS);
}
In order to get things working at all. Should I have added another
definition in that file? I'm a little baffled at what I should be
doing
course the workaround itself may end up
annoying them, too. There's just no pleasing some folks.
Kind Regards,
Brian Wisti
http://coolnamehere.com/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP
