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

Re: [Simpletest-support] Can simpletest print out the valuethatcauses failure?

[Sebastian S. <ssc...@ch...>]

>But the thing is when there's a failure, I won't know which line, hence 
> value, causes the failure.

Use the next parameter to write a text like 'Did not succeed for the name'

$this->assertTrue($oVM->isValidName('abcdefghijabcdefghij'), 'Sucessful NOT
for name ', 'abcdefghijabcdefghij');


That will help you ;) 




-----Ursprüngliche Nachricht-----
Von: Sebastian Schürmann [mailto:ssc...@ch...] 
Gesendet: Freitag, 17. Oktober 2008 16:50
An: 'Help, advice,bugs and workarounds'
Betreff: Re: [Simpletest-support] Can simpletest print out the
valuethatcauses failure?

Hi

In General the next Step will be putting this data into files. More easy to
extend and reusable via other tests (like delete user, add user). Do not
forget about url encoded, utf-8 and stuff like that. 
The file base will help you a lot.
If you put success and failure cases into one file its good to count the
numbers and assertEqual on the expected results. 

S.


-----Ursprüngliche Nachricht-----
Von: Jason Sweat [mailto:jsw...@ya...] 
Gesendet: Freitag, 17. Oktober 2008 14:51
An: Help, advice,bugs and workarounds
Betreff: Re: [Simpletest-support] Can simpletest print out the value
thatcauses failure?

----- Original Message ----

From: YC <te...@gm...>
To: sim...@li...
Sent: Friday, October 17, 2008 12:32:54 AM
Subject: [Simpletest-support] Can simpletest print out the value that causes
failure?

Hi all, I'm new to simple test.

I've a ValidationManager that has one function to validate names.

I've written testIsValidName to be:

    function testIsValidName(){
>
>         $oVM = new ValidationManager();
>
>         $this->assertTrue($oVM->isValidName('john'));
>         $this->assertTrue($oVM->isValidName('John'));
>         $this->assertTrue($oVM->isValidName("john'dina"));
>         $this->assertTrue($oVM->isValidName("john'Dina"));
>         $this->assertTrue($oVM->isValidName("'dina"));
>         $this->assertTrue($oVM->isValidName("dina'"));
>         $this->assertTrue($oVM->isValidName('abcdefghijabcdefghij'));
>
>         $this->assertFalse($oVM->isValidName('i'));
>         $this->assertFalse($oVM->isValidName('koio9'));
>
>
$this->assertFalse($oVM->isValidName('thisisaverylongnamemorethan20chars'));
>
>     }


Is this the right way to go about it?

I was thinking of creating an array of names and then using foreach() to run
through each name.
That will save me time from coding so many lines.
But the thing is when there's a failure, I won't know which line, hence
value, causes the failure.


Hello, welcome to SimpleTest.

I might do something like:

$good_names = array(...);
$bad_names = array(...);

foreach($good_names as $test_name) {
  $this->assertTrue($oVM->isValidName($test_name), $test_name.' should be
valid');
}
foreach($bad_names as $test_name) {
  $this->assertFalse($oVM->isValidName($test_name), $test_name.' should not
be valid');
}

Regards,
Jason


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Simpletest-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simpletest-support


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Simpletest-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simpletest-support

Re: [Simpletest-support] Can simpletest print out the value thatcauses failure?

[Sebastian S. <ssc...@ch...>]

Hi

In General the next Step will be putting this data into files. More easy to
extend and reusable via other tests (like delete user, add user). Do not
forget about url encoded, utf-8 and stuff like that. 
The file base will help you a lot.
If you put success and failure cases into one file its good to count the
numbers and assertEqual on the expected results. 

S.


-----Ursprüngliche Nachricht-----
Von: Jason Sweat [mailto:jsw...@ya...] 
Gesendet: Freitag, 17. Oktober 2008 14:51
An: Help, advice,bugs and workarounds
Betreff: Re: [Simpletest-support] Can simpletest print out the value
thatcauses failure?

----- Original Message ----

From: YC <te...@gm...>
To: sim...@li...
Sent: Friday, October 17, 2008 12:32:54 AM
Subject: [Simpletest-support] Can simpletest print out the value that causes
failure?

Hi all, I'm new to simple test.

I've a ValidationManager that has one function to validate names.

I've written testIsValidName to be:

    function testIsValidName(){
>
>         $oVM = new ValidationManager();
>
>         $this->assertTrue($oVM->isValidName('john'));
>         $this->assertTrue($oVM->isValidName('John'));
>         $this->assertTrue($oVM->isValidName("john'dina"));
>         $this->assertTrue($oVM->isValidName("john'Dina"));
>         $this->assertTrue($oVM->isValidName("'dina"));
>         $this->assertTrue($oVM->isValidName("dina'"));
>         $this->assertTrue($oVM->isValidName('abcdefghijabcdefghij'));
>
>         $this->assertFalse($oVM->isValidName('i'));
>         $this->assertFalse($oVM->isValidName('koio9'));
>
>
$this->assertFalse($oVM->isValidName('thisisaverylongnamemorethan20chars'));
>
>     }


Is this the right way to go about it?

I was thinking of creating an array of names and then using foreach() to run
through each name.
That will save me time from coding so many lines.
But the thing is when there's a failure, I won't know which line, hence
value, causes the failure.


Hello, welcome to SimpleTest.

I might do something like:

$good_names = array(...);
$bad_names = array(...);

foreach($good_names as $test_name) {
  $this->assertTrue($oVM->isValidName($test_name), $test_name.' should be
valid');
}
foreach($bad_names as $test_name) {
  $this->assertFalse($oVM->isValidName($test_name), $test_name.' should not
be valid');
}

Regards,
Jason


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Simpletest-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simpletest-support

Re: [Simpletest-support] Can simpletest print out the value that causes failure?

[Jason S. <jsw...@ya...>]

----- Original Message ----

From: YC <te...@gm...>
To: sim...@li...
Sent: Friday, October 17, 2008 12:32:54 AM
Subject: [Simpletest-support] Can simpletest print out the value that causes failure?

Hi all, I'm new to simple test.

I've a ValidationManager that has one function to validate names.

I've written testIsValidName to be:

    function testIsValidName(){
>
>         $oVM = new ValidationManager();
>
>         $this->assertTrue($oVM->isValidName('john'));
>         $this->assertTrue($oVM->isValidName('John'));
>         $this->assertTrue($oVM->isValidName("john'dina"));
>         $this->assertTrue($oVM->isValidName("john'Dina"));
>         $this->assertTrue($oVM->isValidName("'dina"));
>         $this->assertTrue($oVM->isValidName("dina'"));
>         $this->assertTrue($oVM->isValidName('abcdefghijabcdefghij'));
>
>         $this->assertFalse($oVM->isValidName('i'));
>         $this->assertFalse($oVM->isValidName('koio9'));
>
> $this->assertFalse($oVM->isValidName('thisisaverylongnamemorethan20chars'));
>
>     }


Is this the right way to go about it?

I was thinking of creating an array of names and then using foreach() to run
through each name.
That will save me time from coding so many lines.
But the thing is when there's a failure, I won't know which line, hence
value, causes the failure.


Hello, welcome to SimpleTest.

I might do something like:

$good_names = array(...);
$bad_names = array(...);

foreach($good_names as $test_name) {
  $this->assertTrue($oVM->isValidName($test_name), $test_name.' should be valid');
}
foreach($bad_names as $test_name) {
  $this->assertFalse($oVM->isValidName($test_name), $test_name.' should not be valid');
}

Regards,
Jason


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Simpletest-support] Can simpletest print out the value that causes failure?

[YC <te...@gm...>]

Hi all, I'm new to simple test.

I've a ValidationManager that has one function to validate names.

I've written testIsValidName to be:

    function testIsValidName(){
>
>         $oVM = new ValidationManager();
>
>         $this->assertTrue($oVM->isValidName('john'));
>         $this->assertTrue($oVM->isValidName('John'));
>         $this->assertTrue($oVM->isValidName("john'dina"));
>         $this->assertTrue($oVM->isValidName("john'Dina"));
>         $this->assertTrue($oVM->isValidName("'dina"));
>         $this->assertTrue($oVM->isValidName("dina'"));
>         $this->assertTrue($oVM->isValidName('abcdefghijabcdefghij'));
>
>         $this->assertFalse($oVM->isValidName('i'));
>         $this->assertFalse($oVM->isValidName('koio9'));
>
> $this->assertFalse($oVM->isValidName('thisisaverylongnamemorethan20chars'));
>
>     }


Is this the right way to go about it?

I was thinking of creating an array of names and then using foreach() to run
through each name.
That will save me time from coding so many lines.
But the thing is when there's a failure, I won't know which line, hence
value, causes the failure.

Thanks.

Re: [Simpletest-support] Code coverage

[Douglas H. <dh...@gm...>]

Marcus Baker <marcus@...> writes:
> 
> Hi...
> 
> tarjei wrote:
> > Would it be possible to merge the patch to a branch of 1.1 ?
> > 
> > I'm just thinking that would help with regard to testing and fixing errors.
> 
> If Douglas is happy to do that, but you'll have to ask him. Let's try it
> out first.

I'd be happy to merge it, because the single 1-line change i made to existing
code was because I need advice on how to solve it (calling exit on shutdown hook)

Reason it is so independent of simpletest is because I had to design it so web
processes produce coverage.  So the flow goes

1.) init coverage
2.) run all your code/tests/etc with hook to autocoverage.php in as many
processes commands as you need to.
3.) close coverage
4.) run report

One comment I had, I now think coverage reporter should be in separate php file
so autocoverage.php doesn't load more than it has to.

Re: [Simpletest-support] Code coverage

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

Hi...

tarjei wrote:
> Would it be possible to merge the patch to a branch of 1.1 ?
> 
> I'm just thinking that would help with regard to testing and fixing errors.

If Douglas is happy to do that, but you'll have to ask him. Let's try it
out first.

> 
> regards,
> Tarjei

yours, Marcus

Re: [Simpletest-support] Code coverage

[tarjei <ta...@nu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Would it be possible to merge the patch to a branch of 1.1 ?

I'm just thinking that would help with regard to testing and fixing errors.

regards,
Tarjei
Marcus Baker wrote:
> Hi...
> 
> Douglas Hubler wrote:
>> Douglas Hubler <dhubler@...> writes:
>> As promised:
>>
>> http://sourceforge.net/tracker/index.php?func=detail&aid=2170375&group_id=76550&atid=547457
> 
> Cheers!
> 
> I am not yet sure what we will be able to do for the upcoming 1.1
> release, as I don't want to derail this. It really needs a few people to
> try it out first.
> 
> yours, Marcus
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI91m3YVRKCnSvzfIRAh+uAJ0V584c4A3Scswx1JgdYasbwd2D5gCfc870
rCUoXzB7MYTUCpdSdIPUcmM=
=c3rL
-----END PGP SIGNATURE-----

Re: [Simpletest-support] Code coverage

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

Hi...

Mark Rickerby wrote:
> Cool, I'll take a look at it and give you some feedback.

Thanks Mark.

> 
> Thanks!
> Mark

yours, Marcus

Re: [Simpletest-support] Code coverage

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

Hi...

Douglas Hubler wrote:
> Douglas Hubler <dhubler@...> writes:
> As promised:
> 
> http://sourceforge.net/tracker/index.php?func=detail&aid=2170375&group_id=76550&atid=547457

Cheers!

I am not yet sure what we will be able to do for the upcoming 1.1
release, as I don't want to derail this. It really needs a few people to
try it out first.

yours, Marcus

Re: [Simpletest-support] Code coverage

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

Cool, I'll take a look at it and give you some feedback.

Thanks!
Mark

Re: [Simpletest-support] Code coverage

[Douglas H. <dh...@gm...>]

Douglas Hubler <dhubler@...> writes:

> I would consider it in the category, "it just works" and I would very much like
> to add it to simpletest.  I will submit a patch to trunk for review as it's
> probably the best way to get this started.

As promised:

http://sourceforge.net/tracker/index.php?func=detail&aid=2170375&group_id=76550&atid=547457

Re: [Simpletest-support] Code coverage

[Douglas H. <dh...@gm...>]

Marcus Baker <marcus@...> writes:

> 
> Hi...
> 
> Douglas Hubler wrote:
> > tarjei <tarjei@...> writes:
> > I would like to create an official project somewhere and link to it from
> > simpletest's website as a part of a php test solution.  
> 
> We can easily link to it from simpletest.org. What state is the project
> in right now? I am looking to bundle a code coverage solution as long as
> it passes the "it just works" test. 

So sorry I'm so late on this post!!!

I would consider it in the category, "it just works" and I would very much like
to add it to simpletest.  I will submit a patch to trunk for review as it's
probably the best way to get this started.

Re: [Simpletest-support] Code coverage

[Sebastian S. <ssc...@ch...>]

<3 Code coverage in Simpletest

-----Ursprüngliche Nachricht-----
Von: Douglas Hubler [mailto:dh...@gm...] 
Gesendet: Sonntag, 5. Oktober 2008 03:42
An: sim...@li...
Betreff: Re: [Simpletest-support] Code coverage

tarjei <tarjei@...> writes:

> 
> 
> Hi, does anyone have any tips on how to get coverage data out of
simpletest?
> Tarjei
> 

I had some luck with this
 http://developer.spikesource.com/projects/phpcoverage/

The xmlrpc solution to combine coverage results did not perform well on the
scale of tests I needed so a colleague of mine started a rewrite and I
finished
it.
 http://acquia.com/blog/drupal-cli-utils

Sample results
 http://acquia.com/files/test-results/index.html

Don't worry, it's not only for drupal.  

I would like to create an official project somewhere and link to it from
simpletest's website as a part of a php test solution.  


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Simpletest-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simpletest-support

Re: [Simpletest-support] Code coverage

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

Hi...

Douglas Hubler wrote:
> tarjei <tarjei@...> writes:
> I would like to create an official project somewhere and link to it from
> simpletest's website as a part of a php test solution.  

We can easily link to it from simpletest.org. What state is the project
in right now? I am looking to bundle a code coverage solution as long as
it passes the "it just works" test. I am happy to modify the SimpleTest
core to accommodate it.

yours, Marcus

Re: [Simpletest-support] Code coverage

[Douglas H. <dh...@gm...>]

tarjei <tarjei@...> writes:

> 
> 
> Hi, does anyone have any tips on how to get coverage data out of simpletest?
> Tarjei
> 

I had some luck with this
 http://developer.spikesource.com/projects/phpcoverage/

The xmlrpc solution to combine coverage results did not perform well on the
scale of tests I needed so a colleague of mine started a rewrite and I finished
it.
 http://acquia.com/blog/drupal-cli-utils

Sample results
 http://acquia.com/files/test-results/index.html

Don't worry, it's not only for drupal.  

I would like to create an official project somewhere and link to it from
simpletest's website as a part of a php test solution.  

Re: [Simpletest-support] Code coverage

[Elijah I. <tm...@gm...>]

I'm pretty certain there is no coverage data being collected.

-- Elijah

On Fri, Oct 3, 2008 at 1:35 AM, tarjei <ta...@nu...> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, does anyone have any tips on how to get coverage data out of
> simpletest?
> Tarjei
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFI5dlmYVRKCnSvzfIRAqKQAJ4knchkPUS69GSzPOoStNbScKUwUwCgsv0G
> bH5HR337pS963RzkzmeAzMQ=
> =n6sh
> -----END PGP SIGNATURE-----
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

[Simpletest-support] simpletest.org vs. htmlspecialchars

[troels knak-n. <tro...@gm...>]

Hi,

Currently, all documentation on simpletest.org is double-encoded, so
-> becomes -> thereby making the code samples rather unreadable.

--
troels

Re: [Simpletest-support] MultipleExpectation

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

Hi...

Travis Swicegood wrote:
> 	AnyExpectationDecorator <-- any pass, this passes
> 	AllExpectationDecorator <-- all must pass

I thought that might be what you want.

How about these names...?

new AnyExpectationOf($expectation, ...)
new AllExpectationsOf($expectation, ...)

They are not really decorators, and not really composites either.

> 
> That said, I could probably write a custom expectation that could  
> handle this case just as easily.

That's a good argument for not adding them, although I have no 
objection other than a desire to keep the code base small. Can you 
wait for a second request for this feature?

> 
> -T

yours, Marcus

Re: [Simpletest-support] MultipleExpectation

[Travis S. <dev...@do...>]

Howdy all...

On Oct 2, 2008, at 8:08 PM, Marcus Baker wrote:

> Curious. What do you want it for?

Writing custom assertions with complex logic while still re-using  
existing expectation classes.  There's actually two here I think:

	AnyExpectationDecorator <-- any pass, this passes
	AllExpectationDecorator <-- all must pass

That said, I could probably write a custom expectation that could  
handle this case just as easily.

-T

[Simpletest-support] Code coverage

[tarjei <ta...@nu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, does anyone have any tips on how to get coverage data out of simpletest?
Tarjei
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI5dlmYVRKCnSvzfIRAqKQAJ4knchkPUS69GSzPOoStNbScKUwUwCgsv0G
bH5HR337pS963RzkzmeAzMQ=
=n6sh
-----END PGP SIGNATURE-----

Re: [Simpletest-support] MultipleExpectation

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

Hi...

Travis Swicegood wrote:
> Is there a reason we don't ship with a MultipleException decorator  
> that takes N expectations and passes if they all pass?

Curious. What do you want it for?

> 
> -T

yours, Marcus

[Simpletest-support] MultipleExpectation

[Travis S. <dev...@do...>]

Hey all...

Is there a reason we don't ship with a MultipleException decorator  
that takes N expectations and passes if they all pass?

-T

Re: [Simpletest-support] twist testing

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

Hi...

Mark Rickerby wrote:
> http://studios.thoughtworks.com/twist-agile-test-automation/writing-tests
> 
> *cough*... arbiter ...

:)

If it wasn't for those damn kids. Of all the projects put on hold,
arbiter was my favourite.

yours, Marcus

[Simpletest-support] twist testing

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

http://studios.thoughtworks.com/twist-agile-test-automation/writing-tests

*cough*... arbiter ...

Re: [Simpletest-support] Web form submitting

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

Hi...

Claude Paroz wrote:
> It might by something to add by default in all submit requests in
> SimpleTest.

It absolutely should be. It's been a long standing omission. Once we get
past a current run of drudge getting the 1.1 version ship shape, we can
get back to ading features.

>
> Many thanks for the support.

No problem.

>
> Claude

yours, Marcus
-- 
Marcus Baker
ma...@la...