simpletest-support — Help, advice, bugs and workarounds.

Re: [Simpletest-support] Question about setReturnValue and objects in parameters

[Tarjei H. <ta...@sc...>]

Use setReturnValueAt()
T
On 11/02/2011 10:25 AM, Nicolas Terray wrote:
> Hi,
>
> I have a weird behavior and I would like to know if it is a bug in
> SimpleTest or my misunderstanding.
>
> A snippet is worth a thousand words:
> <?php
>
> class CarFactoryTest extends UnitTestCase {
>     function testPaint() {
>         $c1 = new MockCar();
>         $c2 = new MockCar();
>
>         $f = new MockCarFactory();
>         $f->setReturnValue('paint', true, array($c1));
>         $f->setReturnValue('paint', false, array($c2));
>
>         $this->assertTrue($f->paint($c1));
>         $this->assertFalse($f->paint($c2)); //fail :'(
>     }
> }
>
> class Car {
> }
> Mock::generate('Car');
>
> class CarFactory {
>     function paint(Car $car) {
>     }
> }
> Mock::generate('CarFactory');
>
> ?>
>
> The test is unfortunately red. I expect that two different objects
> should generate different results.
>
> Am I wrong?
>
> Thanks,
> Nicolas Terray
>
> ------------------------------------------------------------------------------
> RSA&#174; Conference 2012
> Save $700 by Nov 18
> Register now&#33;
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support


-- 
Regards / Med vennlig hilsen
Tarjei Huse
Mobil: 920 63 413

[Simpletest-support] Question about setReturnValue and objects in parameters

[Nicolas T. <nic...@gm...>]

Hi,

I have a weird behavior and I would like to know if it is a bug in
SimpleTest or my misunderstanding.

A snippet is worth a thousand words:
<?php

class CarFactoryTest extends UnitTestCase {
    function testPaint() {
        $c1 = new MockCar();
        $c2 = new MockCar();

        $f = new MockCarFactory();
        $f->setReturnValue('paint', true, array($c1));
        $f->setReturnValue('paint', false, array($c2));

        $this->assertTrue($f->paint($c1));
        $this->assertFalse($f->paint($c2)); //fail :'(
    }
}

class Car {
}
Mock::generate('Car');

class CarFactory {
    function paint(Car $car) {
    }
}
Mock::generate('CarFactory');

?>

The test is unfortunately red. I expect that two different objects
should generate different results.

Am I wrong?

Thanks,
Nicolas Terray

Re: [Simpletest-support] Segmentation fault when expecting an argument that refers to the invoked mock

[Tarjei H. <ta...@sc...>]

Hi, try to run php in a debugger and see what happens. If php segfaults,
that is most probably not a simpletest issue but a problem with php.

T
On 10/29/2011 04:58 PM, Mark Slade wrote:
> I realized last night that I neglected to include the important stuff:
>
> PHP version is 5.1.6, SimpleTest version is 1.1alpha3.
>
> On Fri, Oct 28, 2011 at 9:19 PM, Mark Slade <mar...@gm...> wrote:
>> Hi,
>>
>> I ran into a problem when writing up some test cases.  I'm new to
>> SimpleTest, so I'm not sure if this is me abusing SimpleTest or a bug
>> and wanted to run it by the list for some feedback.
>>
>> What I encountered was that if I create a mock object, and call
>> expectOnce with a data structure that refers back to that mock object,
>> I get a segmentation fault.  The proof of concept is below.
>>
>> ==== >8 =================================
>> <?php
>>
>> require_once 'simpletest/autorun.php';
>>
>> class PocClass
>> {
>>    function go($in)
>>    {
>>    }
>> }
>>
>> class TestPocClass extends UnitTestCase
>> {
>>    function testPoc()
>>    {
>>        Mock::generate('PocClass');
>>        $poc = new MockPocClass;
>>        $in = new stdClass;
>>        $in->poc = $poc;
>>        $poc->expectOnce('go', array($in));
>>        $poc->go($in);
>>    }
>> }
>>
>> ?>
>>
>> $ php poc.php
>> poc.php
>> Segmentation fault
>> ==== >8 =================================
>>
>> Is there a way to accomplish what I'm trying to do here?  My actual
>> test case is more complex than this but the idea's the same.  I have a
>> parser object, that parses special markup using handler objects.
>> Those handler objects are added to the parser, and when the parser
>> invokes them to handle some markup, it passes in contextual
>> information including a reference to itself.  This is necessary as a
>> single handler may be added to multiple parsers, so the handler needs
>> a reference to the parser that invoked it (and that parser will also
>> contain that handler).
>>
>> My test case creates a mock handler, adds it to the parser, then asks
>> the parser to parse a string.  I'm using expectOnce to make sure that
>> the parser calls the handler with the expected context.
>>
>> Thanks,
>> Mark
>>
> ------------------------------------------------------------------------------
> Get your Android app more play: Bring it to the BlackBerry PlayBook 
> in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
> for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
> it is! http://p.sf.net/sfu/android-dev2dev
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support


-- 
Regards / Med vennlig hilsen
Tarjei Huse
Mobil: 920 63 413

Re: [Simpletest-support] Segmentation fault when expecting an argument that refers to the invoked mock

[Mark S. <mar...@gm...>]

I realized last night that I neglected to include the important stuff:

PHP version is 5.1.6, SimpleTest version is 1.1alpha3.

On Fri, Oct 28, 2011 at 9:19 PM, Mark Slade <mar...@gm...> wrote:
> Hi,
>
> I ran into a problem when writing up some test cases.  I'm new to
> SimpleTest, so I'm not sure if this is me abusing SimpleTest or a bug
> and wanted to run it by the list for some feedback.
>
> What I encountered was that if I create a mock object, and call
> expectOnce with a data structure that refers back to that mock object,
> I get a segmentation fault.  The proof of concept is below.
>
> ==== >8 =================================
> <?php
>
> require_once 'simpletest/autorun.php';
>
> class PocClass
> {
>    function go($in)
>    {
>    }
> }
>
> class TestPocClass extends UnitTestCase
> {
>    function testPoc()
>    {
>        Mock::generate('PocClass');
>        $poc = new MockPocClass;
>        $in = new stdClass;
>        $in->poc = $poc;
>        $poc->expectOnce('go', array($in));
>        $poc->go($in);
>    }
> }
>
> ?>
>
> $ php poc.php
> poc.php
> Segmentation fault
> ==== >8 =================================
>
> Is there a way to accomplish what I'm trying to do here?  My actual
> test case is more complex than this but the idea's the same.  I have a
> parser object, that parses special markup using handler objects.
> Those handler objects are added to the parser, and when the parser
> invokes them to handle some markup, it passes in contextual
> information including a reference to itself.  This is necessary as a
> single handler may be added to multiple parsers, so the handler needs
> a reference to the parser that invoked it (and that parser will also
> contain that handler).
>
> My test case creates a mock handler, adds it to the parser, then asks
> the parser to parse a string.  I'm using expectOnce to make sure that
> the parser calls the handler with the expected context.
>
> Thanks,
> Mark
>

[Simpletest-support] Segmentation fault when expecting an argument that refers to the invoked mock

[Mark S. <mar...@gm...>]

Hi,

I ran into a problem when writing up some test cases.  I'm new to
SimpleTest, so I'm not sure if this is me abusing SimpleTest or a bug
and wanted to run it by the list for some feedback.

What I encountered was that if I create a mock object, and call
expectOnce with a data structure that refers back to that mock object,
I get a segmentation fault.  The proof of concept is below.

==== >8 =================================
<?php

require_once 'simpletest/autorun.php';

class PocClass
{
    function go($in)
    {
    }
}

class TestPocClass extends UnitTestCase
{
    function testPoc()
    {
        Mock::generate('PocClass');
        $poc = new MockPocClass;
        $in = new stdClass;
        $in->poc = $poc;
        $poc->expectOnce('go', array($in));
        $poc->go($in);
    }
}

?>

$ php poc.php
poc.php
Segmentation fault
==== >8 =================================

Is there a way to accomplish what I'm trying to do here?  My actual
test case is more complex than this but the idea's the same.  I have a
parser object, that parses special markup using handler objects.
Those handler objects are added to the parser, and when the parser
invokes them to handle some markup, it passes in contextual
information including a reference to itself.  This is necessary as a
single handler may be added to multiple parsers, so the handler needs
a reference to the parser that invoked it (and that parser will also
contain that handler).

My test case creates a mock handler, adds it to the parser, then asks
the parser to parse a string.  I'm using expectOnce to make sure that
the parser calls the handler with the expected context.

Thanks,
Mark

Re: [Simpletest-support] Helps to read the docs....

[Marcus B. <ma...@la...>]

Hi...

> 
> Sorry for the noise.

No problem. We should flag the bundled file somewhere on the site.

> 
> On another note any idea if there will be a beta for 1.1.0 or just go to 
> a release? 

The current version will go straight to release. Only held up on docs
which have been held up by children on summer holidays.


yours, Marcus

Re: [Simpletest-support] alpha3 doesn't work?

[Marcus B. <ma...@la...>]

Hi...

Mark Donohoe wrote:
> PHP Fatal error:  Call to undefined method TestSuite::addTestFile() in 
> /home/jenkins/.jenkins/jobs/Test-System-Cleanup/workspace/fossology/tests/runTestCleanup.php 
> on line 43

That was deprecated a while ago. See the bundled file
HELP_MY_TESTS_DONT_WORK_ANYMORE for details.

Just use $this->addFile(...) instead.

> I am really sorta stuck here, can someone help me get alpha3 working?   
> Thanks.

That should be enough. Try that and get back to me.

yours, Marcus

[Simpletest-support] Helps to read the docs....

[Mark D. <mar...@hp...>]

I posted earlier today about missing classes.  Helps if you read the 
documentation and the README.  Looks like things are working pretty well 
in php5.x good work simepletest team.
Somehow I was thinking there should be something on the simepletest web 
site or some sort of note about API changes.  Like in the box announcing 
the alpha3 release.  I should have known to look at the README and HELP 
MY.... files

Sorry for the noise.

On another note any idea if there will be a beta for 1.1.0 or just go to 
a release?  I will be using apha3 as a production version since we are 
executing on a PHP5.3 based system and using the older 1.0.1 release 
causes way too many exceptions, so the tests fail due the exceptions not 
due to test failures.

Looking forward to a released version of 1.1.

---
Mark Donohoe
OSPO, HP
FOSSology.org

[Simpletest-support] alpha3 doesn't work?

[Mark D. <mar...@hp...>]

Simpletesters,

I have tried alpha3 a number of times, each time my existing tests won't 
work?

For example here is a test that runs fine in simpletest 1.0.1:

But in simpletest1.1.0 I get:

jenkins@fonightly: ./runTestCleanup.php
Starting Cleanup Tests on: 2011-09-08 at 12.03.58-pm
Using Svn Version:4723M

PHP Fatal error:  Call to undefined method TestSuite::addTestFile() in 
/home/jenkins/.jenkins/jobs/Test-System-Cleanup/workspace/fossology/tests/runTestCleanup.php 
on line 43

Fatal error: Call to undefined method TestSuite::addTestFile() in 
/home/jenkins/.jenkins/jobs/Test-System-Cleanup/workspace/fossology/tests/runTestCleanup.php 
on line 43

the code looks like:

$test = new TestSuite('Fossology Test Clean Up');
$test->addTestFile('testCleanUp.php');

What happened to addTestFile?  Is there some release or transition notes 
that I am not seeing or reading?  Do I need to include some different files?

Right now the code includes:

require_once '/usr/local/simpletest/web_tester.php';
require_once '/usr/local/simpletest/reporter.php';

Basically I cannot get any of my existing 1.0.1 tests to work with alpha3.

Another issue is that since I can't get alpha 3 to work, the 1.0.1 
version causes a ton of exceptions on a system running php 5.3, which in 
turn causes the tests to fail with exceptions, when all the other test 
cases pass.  This is on Debian squeeze and ubuntu systems (lucid, 
maverick merkat).

I am really sorta stuck here, can someone help me get alpha3 working?   
Thanks.


-- 
---
Mark Donohoe
OSPO, HP
FOSSology.org

Re: [Simpletest-support] New user, idea for assertList() method

[Marcus B. <ma...@la...>]

Hi...

Mac Newbold wrote:
> As I was setting up some test cases, I found myself craving a way to
> run a list of similar asserts all at once, rather than copy-paste
> duplicating all the assert calls. I ended up with a method I added to
> my class that extends UnitTestCase like so:

How about something that uses array_map...?

array_map(
	function($subject, $expected) using $this {
		$this->assertIdentical($subject, $expected);
	},
	$vals);

Assuming you are using PHP5.3+.

> Being new, I wanted to ask if this is something that others might find
> useful, or if there are other better ways that more experienced
> SimpleTest users use for this kind of thing.

Not sure I could include it in the standard SimpleTest package.

If the one liner (sort of) above matches your need, then I'd rather not
add another assertion. It adds cognitive load to using the framework to
have a big assertion list. I've always tried to keep the function set small.

If you create your own project wide test cases...

class MyUnitTestCase extends UnitTestCase { ... }

...and you use these as a basis for your tests, then you can add your
own features there. Sorry, but I can only include the features that
would have a widespread use, even if the utility is very high in a
special case.

> 
> Thanks,
> Mac
> 

At least by posting this solution others may find it useful.

yours, Marcus

Re: [Simpletest-support] New user, idea for assertList() method

[Noel D. <ma...@mc...>]

Hi

> As I was setting up some test cases, I found myself craving a way to
> run a list of similar asserts all at once, rather than copy-paste
> duplicating all the assert calls.

I think that's always a signal to refactor by creating some kind of
custom test method. The tests - which are also documentation you'll
want to refer back to later on down the road - are much easier to read
if they are terse and to the point. This is something you'll want to do
quite often.

Naming is important, as well brevity. "AssertList" is quite a vague
label. That's fine for general-purpose methods (like assertIdentical
etc) but your tests might read better if you give it a more meaningful
name within your domain like "assertCustomerRecord" or whatever.

The general-purpose method might drop out after you've done several of
these and notice that you keep repeating similar lines of code. Or it
might not. I'd wait and see.

Custom methods are fine for something trivial otherwise you should
write a custom expectation class, extending SimpleExpectation:

class Something extends SimpleExpectation {

    var $test_message = 'oops %s';

    function __construct($value, $overlaid_message = '%s') {
        parent::__construct($overlaid_message);
        $this->_value = $value;
    } 
    function test($compare) {
        // whatever...
    }
    function testMessage($compare) {
        if ($this->test($compare)) {
            return 'hurrah! ' . 
                $this->dumper->describeValue($compare);
        } else {
            return sprintf(
                $this->test_message, 
                $this->dumper->describeDifference(
                    $this->_value, 
                    $compare));
        }
    }
}


This would be added to a test case with the assertSomething method,
below:


abstract class MyCustomtestCase extends UnitTestCase

    function assertSomething(
        $value, 
        $compare, 
        $message = '%s') {

        return $this->_test_case->assert(
            new Something($value), 
            $compare, 
            $message);
    }

...
...

(1) The expectation object is passed in parameter 1 of the assert()
call. The simpletest framework will automatically pass parameter 2 to
the expectation object test() and testMessage() methods. You can
also support customised messages if you like, but you don't have to.

(2) The simpletest dumper can be handy to describe exactly what went
wrong in a fail. That's optional though.

(3) You can add the assertSomething method to any class where you need
it but if it you find yourself using it a lot, you might find you're
better off writing an abstract test case class containing this (and
possibly some other) custom expectations. 

Have a read through the source code to see how the standard simpletest
expectations are implemented. 

Finally, I've written a lot of extensions for simpletest (for my own
use; they're not official) here: http://aperiplus.sourceforge.net/.
That might give you some ideas too. You can pinch & adapt anything you
like.


Noel

[Simpletest-support] New user, idea for assertList() method

[Mac N. <ma...@ma...>]

Hi all,

I started using SimpleTest last week, and I must say I'm thoroughly
impressed and extremely happy with what it's already doing for me.

As I was setting up some test cases, I found myself craving a way to
run a list of similar asserts all at once, rather than copy-paste
duplicating all the assert calls. I ended up with a method I added to
my class that extends UnitTestCase like so:

function assertList($callback, $list) {
	foreach ($list as $k => $v) {
		if (is_array($v)) {
			call_user_func_array($callback,$v);
		} else {
			call_user_func_array($callback,array($k => $v));
		}
	}
}

In short, it accepts a callback, and an list of argument sets, which
it then uses to call the function requested. For example:

$vals =
      array(array($t->table,'table'),
		array($t->prefix,''),
		array($t->id,'id'),
		array($t->parent,'parent'),
		array($t->sort,'sort'),
		array($t->depth,'depth'),
		array($t->left,'lft'),
		array($t->right,'rgt'),
	);
$this->assertList(array($this,'assertIdentical'), $vals);

This results in the same thing as calling assertItendical on each of
the records. One big advantage I see for this is that it is useful for
generating a list of tests/asserts and being able to run them all at
once. The other mode of operation it allows for is rather than a
regular array, where the values are the exact parameters to the
callback function, it will also accept associative arrays, where the
key is paired with the value that should be used as parameters to the
callback.

Being new, I wanted to ask if this is something that others might find
useful, or if there are other better ways that more experienced
SimpleTest users use for this kind of thing.

Thanks,
Mac

-- 
Mac Newbold
ma...@ma...
801-694-6334

[Simpletest-support] Scriptable Browser button tag behavior

[AOYAMA S. <sho...@be...>]

Hi,

When you submit a form with <button> tag like this:
    <form name="f1" method="get" action="button.php">
        <input type="text" name="t1" value="asd">
        <button name="sendemail" id="sendemail" type="submit">Send
Email</button>
    </form>
IE, Firefox, Safari and Opera send following values.
array(2) { ["t1"]=> string(3) "asd" ["sendemail"]=> string(0) "" }

On the other hand, the Scriptable Browser doesn't send "sendemail"
parameter.
$browser = new SimpleBrowser();
$browser->get('http://localhost/button.php');
$browser->setFieldByName('t1', 'asd');
echo $browser->clickSubmitById('sendemail');
===>
array(1) {  ["t1"]=>  string(3) "asd" }

I found out this workaround,
$browser->clickSubmitById('sendemail', array('sendemail' => ''));

but woundn't it be better if this is the default behavior?
clickSubmitById's second argument is not documented here.
http://www.simpletest.org/en/browser_documentation.html

BTW, I'm using the Scriptable Browser independently from SimpleTest
,and I feel that the documentation is not enough.
It lacks return value information and what you can pass as arguments
is not clear. I'd really appreciate if you have the documentation complete.


Regards,

-- 
AOYAMA Shotaro
E-Mail：sho...@be...

[Simpletest-support] testing file uploads

[<jo...@th...>]

Hi,

im having trouble web testing file uploads, during a multi page form.

im attempting the following:


    $this->setField('page_image1', RESOURCES_PATH . 'sample1.jpg');
    $this->setField('picture', 'own');
    $this->setField('MAX_FILE_SIZE', '188743680');
    $this->setField('UPLOAD_IDENTIFIER', '4dd3a60dee9d7');
    $this->clickSubmitByName('next');

    $this->assertResponse(200);
    // the below should be the page they appear at after upload
    $this->assertText('Create a thumbnail');

i have tried both the above and using the $this->post(array()) method, but
neither work. the page is not going through to the next stage correctly,
although all other stages of the form do work (ie, i can test each stage
up to this point)

any hint as to what is wrong?

Thanks,
J

[Simpletest-support] Export cookies to a file

[SmartGIG G. <sma...@gi...>]

Hello,

I am using simpletest scriptable browser to automate my tasks.
I need to export cookies to a file, in order to use them again when I call
the php script.
For example  , consider I need to login to a site which has a captcha ,
First I should receive the page with captcha and save the cookie, then ask
the client to enter the captcha and finally send the captcha to the server
while should set the saved cookie here.
Some sites create multiple cookies.
Is it any way to export all cookies created by simpletest browser to a file
and import them ?

Thanks

[Simpletest-support] French documentation back in synch / Italian version online

[Perrick Penet-A. <pe...@no...>]

Hi folks,

I took the time yesterday evening to finally get the french 
documentation back in synch with the last edits done by Marcus. In 
particular a lot of work went into the "Mock objects" parts. It means 
we're now looking for reviewers : I uploaded everything directly to the 
SimpleTest website, it should be easier for anyone wanting to give a hand !

You can start reading here :
http://simpletest.org/en/
http://simpletest.org/fr/

And proceed to the bug tracker for any comments :
http://sourceforge.net/tracker/?group_id=76550&atid=547455

Now for the italian version, it is also online :
http://simpletest.org/it/

I'm not sure how synchronized it is though. If anyone wants to have a 
detailed look, please go ahead... There's a little script in the SVN 
tree - simpltest/packages/simpletest.org/index.php - that can help you 
on the way. Here's how it works...

The script will compare the last version id (SVN commit number) of the 
orginal english version and the "synchronisation version" number 
available at the top of the translated file. And then the script will 
package the files and highlight the ones that are not in synch.

For the italian version, the numbers are all "0" even though some work 
has already been done. Is someone interested in stepping in to deal with 
this ?

Yours,
	Perrick

[Simpletest-support] Help Regarding Command Line testing

[sumit k. <sum...@gm...>]

Hi Guys,

I am new in using the testing framework and do not know much about them. I
however tried PHPUnit and Simpletest & they both look the same. Could you
tell me if there are any differences in them?

My basic requirement is to automate the build process using "*something*". I
am looking at Maven & Hudson but I want to have a testing framework running
to first test all the code and then build it. Could I use simpletest for it?

Also I couldn't find any link for using the simpletest through commandline.
When I am using the command line for running my tests, it shouts at every "*
require_once" *if the path is relative. I then have to hardcode the path at
every file that is being called. Is there any settings for it?

Could you please help me in this. I am not much familiar with any Testing
framework like these.

Thanks & Regards
Sumit Kumar

Re: [Simpletest-support] File missing: arguments.php

[Perrick Penet-A. <pe...@no...>]

I didn't realize that "fixed" meant a new version was out. The webiste 
now reflects all this...

The news section now says :

"[2011/05/23]  SimpleTest 1.1alpha3 is released. This maintenance 
release fixes a few bugs (especially in the release process). Having 
spent nearly 2 years in trunk, this version is considered pretty stable."

I'm now looking forward to the beta cyle ;-) By the way, the french 
documentation is slowly getting back in synch !

Yours,
	Perrick



On 15/05/11 21:54, Attila wrote:
> Thank you very much!
> On 2011-05-15 5:15 AM, "Marcus Baker"<ma...@la...>  wrote:
>> Hi...
>>
>> Attila wrote:
>>> I am new to SimpleTest and I just installed the package and ran the
> sample.
>>> However I get the following error:
>>
>> I've fixed this. Should be good now.
>>
>> yours, Marcus
>>
>>
> ------------------------------------------------------------------------------
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> Simpletest-support mailing list
>> Sim...@li...
>> https://lists.sourceforge.net/lists/listinfo/simpletest-support
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

[Simpletest-support] meta refresh redirect

[Richard W. <ri...@ro...>]

I have found that a response page I am testing specifies a meta refresh that is
not being followed by user_agent.php/fetchWhileRedirected.

Here is the meta element on the page:

<meta http-equiv="Refresh" content="1;URL=import.php?error=1" />

The problem is that the fetchWhileRedirected assumes that the refresh time will
always be zero - here is the pattern tested:

$pattern = '|<meta\shttp-equiv="Refresh"\scontent="0;\surl=(.*)">|';

On this particular page the creator wanted to show a little message and then
quickly forward to the redirect hence the 1 second delay.  Other pages in this
site have other delays for longer messages.

Should this be changed in simpletest to allow any refresh delay?

Richard

Re: [Simpletest-support] Get SimpleTest to recognize custom exception

[Mark R. <co...@gm...>]

Hi Kasper,

expectException is the method you want to use:

http://www.simpletest.org/api/SimpleTest/UnitTester/UnitTestCase.html#expectException

These examples show how it is used in real code:

https://github.com/maetl/floe/blob/master/tests/server.test.php#L166
http://code.google.com/p/blip-php/source/browse/trunk/+blip-php/Blip-PHP/test/upload_test_cases.php?r=9#57
https://gitorious.org/htmlpurifier/mainline/blobs/master/tests/HTMLPurifier/LexerTest.php#line45

Hope that helps,
Mark

[Simpletest-support] Get SimpleTest to recognize custom exception

[Kasper G. <ka...@gm...>]

Hi SimpleTest group,

I don't think I was subscribed before, so this message didn't appear, sorry
if it went through and I am spamming.

I am experiencing an issue with SimpleTest when using my own custom
exceptions, I am having a lot of these kind of exceptions:
<?php
class NoRefererException extends Exception
{
}
?>

They basically have no real functionality, they just extend, and then I can
listen on which type of exception i get.

However, I am having a hard time to get SimpleTest to test when these are
thrown, is it possible to check for it? And could you provide some
sourcecode for it? I couldn't find Exceptions used directly in the docs.

Thanks,
--
Kasper Grubbe

Phone: (+45) 42 42 42 74
Mail: kas...@gm...

Kettegårds Allè 70,1,6115
2650 Hvidovre
Denmark

Re: [Simpletest-support] File missing: arguments.php

[Attila <att...@gm...>]

Thank you very much!
On 2011-05-15 5:15 AM, "Marcus Baker" <ma...@la...> wrote:
> Hi...
>
> Attila wrote:
>> I am new to SimpleTest and I just installed the package and ran the
sample.
>> However I get the following error:
>
> I've fixed this. Should be good now.
>
> yours, Marcus
>
>
------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support

Re: [Simpletest-support] File missing: arguments.php

[Marcus B. <ma...@la...>]

Hi...

Attila wrote:
> I am new to SimpleTest and I just installed the package and ran the sample.
> However I get the following error:

I've fixed this. Should be good now.

yours, Marcus

Re: [Simpletest-support] 1.1alpha2 docs and usage

[Marcus B. <ma...@la...>]

Hi...

Mark Rickerby wrote:
> I'm looking into this issue currently.

Cool.

Both the JUnit reporter and the Selenium test case should really be
moved to the core assuming they are stable. Both are pretty fundamental
these days.

I've done some work for a client getting the Selenioum one to work more
out of the box (it properly fires up SeleniumRC, but not yet a custom
firefox profile). Most people will notice a seamless setup in this case,
as long as they don't use Firefox as their browser at the same time. The
custom profile should fix this. As there is obvious demand for this,
I'll move the code over when I next get a time slot. Real life is doing
a good job of squashing my spare PHP time.

> http://maetl.net/harnessing-simpletest

Cool.

> 
> Best regards,
> Mark

yours, Marcus

Re: [Simpletest-support] 1.1alpha2 docs and usage

[Mark R. <co...@gm...>]

Hi Mark,

Just to clarify, with respect to your question: the discrepancy you
noticed is because the API docs have been generated against a working
copy with all the extensions included, but the tarball on sourceforge
contains only the core SimpleTest library and doesn't include all the
extensions that are currently in the repo, which is why you can see
the full extension directory here:
http://simpletest.org/api/SimpleTest/Extensions/ ... but can't find
these files in the download.

Thanks,
Mark