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

Re: [Simpletest-support] Bug Report: Incompatibility with MediaWiki

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

Hi...

Lambert Lum wrote:
> <input type='hidden' value="99b0c5b089d852f6c490d9ac17ae4c3a+\" 
> name="wpEditToken" />
> 
> My guess is that the SimpleTest parser interprets the '\' as a special 
> character and thus renders the value attribute unreadable.

I think you are right. I'll add a test into the test suite for this 
case.

yours, Marcus

Re: [Simpletest-support] Problems with Eclipse Ganymede / PDT 2.0 under Windows

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

Hi...

Hans Krentel wrote:
> i solved most of my issues,

I am very glad of this. I didn't write the Eclipse plug-in and I wasn't
looking forward to resolving this one :(.

> and then simpletest was able to run. i will answer my own questions now, but no guarantee that those answers are really correct:

Cool. As the next build cycle comes together, I'll integerate the
Eclipse stuff more closely. A FAQ is a long standing need as well, and
your answers will help.

> -- hakre

yours, Marcus

Re: [Simpletest-support] phpUnderControl, static analysis and codecoverage

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

Hi...

Lars Olesen wrote:
> - Has anyone had simpletest output the test results as an xml-file
> phpundercontrol can use?

It does have XML output already, but it's own format. It's pretty easy
to write a Reporter class that outputs the content you want. I don't use
PHPUnderControl, but you are the second person to ask for it. It's time
this issue was addressed.

> - Has anyone implemented codecoverage and a report on the codecoverage
> using xdebug and simpletest - and an xml-file?

Code coverage is only now becoming a standard feature of SimpleTest.

> - Has anyone implemented metric analysis as pmd analysis etc?

No.

yours, Marcus

Re: [Simpletest-support] Simpletest-support - Code Coverage in NetBeans

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

Hi...

Stephen S. Musoke wrote:
> Any idea when 1.1 will be released

My next job now the PHP UK conference is over.

> 
> Stephen 


yours, Marcus

Re: [Simpletest-support] phpUnderControl, static analysis and codecoverage

[Jakob K. <jke...@ch...>]

On Sunday 01 March 2009 16:01:08 Lars Olesen wrote:
> I have a library, which has tests in simpletest. I want to build it
> using phpUnderControl and CruiseControl. However, I want to utitlize
> all the good parts of phpUnderControl, so I want to ask whether anyone
> is working on some kind of integration.
>
> - Has anyone had simpletest output the test results as an xml-file
> phpundercontrol can use?
> - Has anyone implemented codecoverage and a report on the codecoverage
> using xdebug and simpletest - and an xml-file?
> - Has anyone implemented metric analysis as pmd analysis etc?

yes, yes, and no... that's how far i am ;)

for the xml output: you might wanna try the extensions/junit_xml_reporter.php that's bundled with simpletest. i haven't tried it yet - i found it after i had written my own reporter that does the same task.

for code coverage: as far as i see it, that is a pretty new feature coming with the next release. it does work, but it's not that easy to integrate. if you want to set it up you will need to have a deeper look into it. i'm not aware of any documentation (at the moment) except for what was written on this mailing list.

pmd: i haven't seen it in effect yet, it's a feature of phpunit - but if i remember correct, it's deprecated there...

Re: [Simpletest-support] Problems with Eclipse Ganymede / PDT 2.0 under Windows

[Hans K. <han...@ya...>]

i solved most of my issues,

i set up xdebug as describben here:
http://www.eclipse.org/pdt/docs.php
http://www.eclipse.org/pdt/documents/XDebugGuideForPDT2.0.pdf

(needed to reade the first 13 pages at least)

and then simpletest was able to run. i will answer my own questions now, but no guarantee that those answers are really correct:

--- Hans Krentel <han...@ya...> schrieb am So, 1.3.2009:

> Q1) Where does the simpletest eclipse plugin place it
> logfile with info,  warning and error messages?
No Idea.


> Q2) Does the Eclipse Plugin work with Eclipse Version
> 3.4.1?
Yes, it does.

> Q3) Does the Eclipse Plugin work with JavaVM Version 1.6.x?
Yes, it does.

> Q4) Does the Eclipse Plugin work with PHP 5.2.x ?
Yes, it does.

> Q4.1) Does it work with the bare MSI Setup under win32?
Yes, it does.

> Q4.2) Is a Debugger (like XDebug or Zend_Debugger) needed?
Yes, you need it. At least you need XDebug.

> Q5) Does the Eclipse Plugin work even if there is no PHP
> Configuration properly set up within Eclipse PDT 1.0 / PDT
> 2.0?
No it does not. You must have at least a propper PHP Exceuteable setup so that the Eclipse Run Function does work. Therefore you need a properly set up debugger as well.


My 2 cents, might not be the full truth but this did the job for me.

-- hakre



      

Re: [Simpletest-support] Problems with Eclipse Ganymede / PDT 2.0 under Windows

[Hans K. <han...@ya...>]

after setting up xdebug under php 5.2.9 and setting the php executeable within eclipse i was able to run simpletest now. solved.


      

[Simpletest-support] phpUnderControl, static analysis and codecoverage

[Lars O. <lso...@gm...>]

I have a library, which has tests in simpletest. I want to build it
using phpUnderControl and CruiseControl. However, I want to utitlize
all the good parts of phpUnderControl, so I want to ask whether anyone
is working on some kind of integration.

- Has anyone had simpletest output the test results as an xml-file
phpundercontrol can use?
- Has anyone implemented codecoverage and a report on the codecoverage
using xdebug and simpletest - and an xml-file?
- Has anyone implemented metric analysis as pmd analysis etc?

-- 
Lars Olesen

Re: [Simpletest-support] Problems with Eclipse Ganymede / PDT 2.0 under Windows

[Hans K. <han...@ya...>]

If checked out some more boundaries over the last hours to find out more - with no luck.

Can I find a FAQ of the simpletest eclipse plugin somewhere?

Here are my Questions so far:

Q1) Where does the simpletest eclipse plugin place it logfile with info,  warning and error messages?

Q2) Does the Eclipse Plugin work with Eclipse Version 3.4.1?

Q3) Does the Eclipse Plugin work with JavaVM Version 1.6.x?

Q4) Does the Eclipse Plugin work with PHP 5.2.x ?

Q4.1) Does it work with the bare MSI Setup under win32?

Q4.2) Is a Debugger (like XDebug or Zend_Debugger) needed?

Q5) Does the Eclipse Plugin work even if there is no PHP Configuration properly set up within Eclipse PDT 1.0 / PDT 2.0?


Getting answers to these question will help me to drill down my problems. Thanks again for any feedback.





      

[Simpletest-support] Problems with Eclipse Ganymede / PDT 2.0 under Windows

[Hans K. <han...@ya...>]

i installed simpletest as documented, checked my local php configuration that it is executeable (running php.exe on commandline) and even used procmon to take a peek wether or not eclipse.exe is creating a php thread when running the "run as simpletest" command. it does not(!).

anyone can confirm a working install under windows (xp sp3), eclipse ganymede latest, pdt 2.0 (latest) and the simpletest 0.2.5 plugin?

thanks for any kind of feedback i'm just stuck.

hans




      

Re: [Simpletest-support] Simpletest-support - Code Coverage in NetBeans

[Stephen S. M. <ssm...@gm...>]

Hello,

Netbeans has code coverage for PHP at
http://blogs.sun.com/netbeansphp/entry/code_coverage_for_php_why but no
support for SimpleTest yet

Any idea when 1.1 will be released

Stephen 

-----Original Message-----
From: sim...@li...
[mailto:sim...@li...] 
Sent: Tuesday, November 18, 2008 7:19 PM
To: sim...@li...
Subject: Simpletest-support Digest, Vol 30, Issue 3

Send Simpletest-support mailing list submissions to
	sim...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/simpletest-support
or, via email, send a message with subject or body 'help' to
	sim...@li...

You can reach the person managing the list at
	sim...@li...

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Simpletest-support digest..."


Today's Topics:

   1. Re: Code coverage (Jakob Ketterl)
   2. Re: Code coverage (Jakob Ketterl)
   3. Re: Code coverage (Douglas Hubler)
   4. Re: Code coverage (Jakob Ketterl)
   5. Re: Code coverage (Marcus Baker)
   6. Re: Code coverage (Marcus Baker)
   7. Re: Code coverage (Douglas Hubler)


----------------------------------------------------------------------

Message: 1
Date: Tue, 11 Nov 2008 08:14:26 +0100
From: Jakob Ketterl <jke...@ch...>
Subject: Re: [Simpletest-support] Code coverage
To: "Help, advice,	bugs and workarounds"
	<sim...@li...>
Message-ID: <200...@ch...>
Content-Type: text/plain;  charset="iso-8859-1"


On Tuesday 11 November 2008 02:32:59 Douglas Hubler wrote:
> Douglas Hubler <dhubler@...> writes:
> > On ubuntu i installed this package
> >  php-sqlite3
>
> my mistake,
>   php5-sqlite
>
> is the one that i believe i'm using

actually, you didn't make a mistake there. i had already installed
php5-sqlite in a guess before, but that didn't work out. i've now
additionally (yes you will need both packages) installed php-sqlite3 (how
big a difference a few digits can cause ;-) ) and at least i got that
dependency resolved. now i'll have to move to our dev server, where xdebug
is available.

i also tried to install the DB_Sqlite_Tools from pear (from
channel://pear.php.net/DB_Sqlite_Tools-0.1.6) but at least it didn't work
out of the box. Maybe I'll have the time to get another look...

I'm running Ubuntu 8.04.01 Hardy.

Thank you :-)

------------------------------

Message: 2
Date: Wed, 12 Nov 2008 13:25:43 +0100
From: Jakob Ketterl <jke...@ch...>
Subject: Re: [Simpletest-support] Code coverage
To: "Help, advice,	bugs and workarounds"
	<sim...@li...>
Message-ID: <200...@ch...>
Content-Type: text/plain; charset="iso-8859-1"

I found two little bugs in the reporting templates (it's just missing echo
statements). i'm including a patch :-)
-------------- next part --------------
Index:
/home/jketterl/workspace/SimpleTest/extensions/coverage/CoverageTemplates/fi
le.php
===================================================================
---
/home/jketterl/workspace/SimpleTest/extensions/coverage/CoverageTemplates/fi
le.php	(revision 1826)
+++
/home/jketterl/workspace/SimpleTest/extensions/coverage/CoverageTemplates/fi
le.php	(working copy)
@@ -1,6 +1,6 @@
 <html>
 <head>
-<title><?php $title ?></title>
+<title><?php echo $title ?></title>
 </head>
 <style type="text/css">
 body {
Index:
/home/jketterl/workspace/SimpleTest/extensions/coverage/CoverageTemplates/in
dex.php
===================================================================
---
/home/jketterl/workspace/SimpleTest/extensions/coverage/CoverageTemplates/in
dex.php	(revision 1826)
+++
/home/jketterl/workspace/SimpleTest/extensions/coverage/CoverageTemplates/in
dex.php	(working copy)
@@ -30,7 +30,7 @@
 }
 </style>
 <body>
-<h1 id="title"><?php $title ?></h1>
+<h1 id="title"><?php echo $title ?></h1>
 <table>
 	<caption>Summary</caption>
 	<tbody>

------------------------------

Message: 3
Date: Tue, 18 Nov 2008 05:13:16 +0000 (UTC)
From: Douglas Hubler <dh...@gm...>
Subject: Re: [Simpletest-support] Code coverage
To: sim...@li...
Message-ID: <loo...@po...>
Content-Type: text/plain; charset=us-ascii

Jakob Ketterl <jketterl@...> writes:
> I found two little bugs in the reporting templates (it's just missing 
> echo statements). i'm including a patch
thanks, i committed these

Any progress on general review?




------------------------------

Message: 4
Date: Tue, 18 Nov 2008 08:26:08 +0100
From: Jakob Ketterl <jke...@ch...>
Subject: Re: [Simpletest-support] Code coverage
To: "Help, advice,	bugs and workarounds"
	<sim...@li...>
Message-ID: <200...@ch...>
Content-Type: text/plain;  charset="iso-8859-1"

On Tuesday 18 November 2008 06:13:16 Douglas Hubler wrote:
> Jakob Ketterl <jketterl@...> writes:
> > I found two little bugs in the reporting templates (it's just missing
> > echo statements). i'm including a patch
>
> thanks, i committed these
>
> Any progress on general review?

yes, i've even managed to integrate it with phpundercontrol (using a special

reporter class i've hacked up myself).

however, i didn't use the concept of an external shell script to separate 
coverage setup/collection from the actual test run, and i didn't use 
autocoverage.php. this is because our code is separated from its tests, and 
simpletest itself also resides outside of the source tree. that way i can 
simply use a whitelist approach to tell cc what parts of the code it should 
generate statistics upon.

the only thing that doesn't work in that approach is the collection of 
uncovered files, so i've written a recursive function that will 
require_once() everything inside my source directories. not the best 
solution, i must admit (especially if there's executable code inside your
php 
files) but it works for me atm.

i've read in the source that uncovered files are scanned for from getcwd() 
downwards (iirc) - so maybe there's a way to make that configurable?

i've also had a look into what's inside the sqlite file, and from my point
of 
view the structure doesn't look that complicated, imho that's nothing a 
serialized array couldn't handle (if it really needs to be stored to disk - 
for my case it's not even necessary).

i think it would be better to integrate this deeper into the simpletest main

code, but that's beyond the scope of "extension", if i'm correct...




------------------------------

Message: 5
Date: Tue, 18 Nov 2008 10:56:33 +0000
From: Marcus Baker <ma...@wo...>
Subject: Re: [Simpletest-support] Code coverage
To: "Help, advice,	bugs and workarounds"
	<sim...@li...>
Message-ID: <492...@wo...>
Content-Type: text/plain; charset=ISO-8859-1

Hi...

Douglas Hubler wrote:
> Any progress on general review?

Sorry, been my birthday. I'm working on it as time allows.

yours, Marcus



------------------------------

Message: 6
Date: Tue, 18 Nov 2008 10:59:59 +0000
From: Marcus Baker <ma...@wo...>
Subject: Re: [Simpletest-support] Code coverage
To: "Help, advice,	bugs and workarounds"
	<sim...@li...>
Message-ID: <492...@wo...>
Content-Type: text/plain; charset=ISO-8859-1

Hi...

Jakob Ketterl wrote:
> i think it would be better to integrate this deeper into the simpletest
main 
> code, but that's beyond the scope of "extension", if i'm correct...

Your instincts are probably right. Certainly the core will probably have
to add the appropriate hooks.

Any dependence on SQL lite would have to go for it to end up in the
core, and preferably even the file system as we cannot assume write
permissions (e.g. in cruise environments).

yours, Marcus



------------------------------

Message: 7
Date: Tue, 18 Nov 2008 16:18:18 +0000 (UTC)
From: Douglas Hubler <dh...@gm...>
Subject: Re: [Simpletest-support] Code coverage
To: sim...@li...
Message-ID: <loo...@po...>
Content-Type: text/plain; charset=us-ascii

Jakob Ketterl <jketterl@...> writes:
> On Tuesday 18 November 2008 06:13:16 Douglas Hubler wrote:
> > Jakob Ketterl <jketterl@...> writes:
> > > I found two little bugs in the reporting templates (it's just missing
> > > echo statements). i'm including a patch
> >
> > thanks, i committed these
> >
> > Any progress on general review?
> 
> yes, i've even managed to integrate it with phpundercontrol (using a
special 
> reporter class i've hacked up myself).
> 
> however, i didn't use the concept of an external shell script to separate 
> coverage setup/collection from the actual test run

that's great, my goal was to give folks APIs for custom setups, i almost
didn't
create shell script to encourage folks to do just what you did, but then i
thought we'd loose the folks that just wanted to follow a simple pattern.

> i've read in the source that uncovered files are scanned for from getcwd()

> downwards (iirc) - so maybe there's a way to make that configurable?

yes, that directory really should be made configurable


> i've also had a look into what's inside the sqlite file, and from my point
of 
> view the structure doesn't look that complicated, imho that's nothing a 
> serialized array couldn't handle (if it really needs to be stored to disk
- 
> for my case it's not even necessary).

the tests i run take about 2+ hours and sqlite helps me perform data
selection
without loading the entire coverage into memory.  Having said this, all this
is
handled by CoverageDataHandler and so this could have alternate
implementations


> i think it would be better to integrate this deeper into the simpletest
main 
> code, but that's beyond the scope of "extension", if i'm correct...

For reporting, I see someone developing some unit test reports that
integrate
the coverage data, i think someone even suggested that.  I like the fact
that
they can run independently, but i think there are a lot of ways folks can
create
optional ways to make them work together.  

For data collection, in my situation, i run simple tests from CLI, that in
turn
make http requests to a local apache server, that i need to accumulate
coverage
data for.  This request knows nothing about simpletest.


On another note

I'm starting the process of using this branch for generating
 http://acquia.com/files/test-results/index.html
This is a report that is generated on a nightly basis.






------------------------------

-------------------------------------------------------------------------
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


End of Simpletest-support Digest, Vol 30, Issue 3
*************************************************

Re: [Simpletest-support] Full stacktrace on errors

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

Hi...

Edward Z. Yang wrote:
> Is there any way to make SimpleTest print the full stacktrace when it
> traps an error?

There will be. We just have to sort out the visual aspect of this. In
the meantime you can override paintException() in the reporter. Contrary
to the docs (a doc bug), it receives the whole exception as a parameter.

> 
> Cheers,
> Edward

yours, Marcus

[Simpletest-support] Full stacktrace on errors

[Edward Z. Y. <edw...@th...>]

Is there any way to make SimpleTest print the full stacktrace when it
traps an error?

Cheers,
Edward

Re: [Simpletest-support] Bug Report: Incompatibility with MediaWiki

[Perrick P. <pe...@no...>]

Bugs posted on this mailing-list tend to be discussed only and forgotten 
later on. You may want to add to the bug-tracker to make sure someone 
picks it up at a later date :

http://sourceforge.net/tracker/?atid=547455&group_id=76550&func=browse

Yours,
	Perrick



Lambert Lum wrote:
> I hope this is the right place to report a bug.
> 
> I am using SimpleTest with MediaWiki. During the course of writing test 
> scripts I noticed that anything that dealt with editing wiki pages was 
> failing. Upon closer inspection, I noticed that Simple Test was choking on a 
> hidden form element, named wpEditToken. This wpEditToken's value is a string 
> that ends in '\'.
> 
> <input type='hidden' value="99b0c5b089d852f6c490d9ac17ae4c3a+\" 
> name="wpEditToken" />
> 
> My guess is that the SimpleTest parser interprets the '\' as a special 
> character and thus renders the value attribute unreadable.
> 
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code to
> build responsive, highly engaging applications that combine the power of local
> resources and data with the reach of the web. Download the Adobe AIR SDK and
> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
> 
> 

Re: [Simpletest-support] Simpletest Code Coverage fails on eval'd code

[Jakob K. <jke...@ch...>]

of course. here it is: 
http://sourceforge.net/tracker/index.php?func=detail&aid=2592015&group_id=76550&atid=547457

thank you :)
jakob

On Wednesday 11 February 2009 16:59:21 Perrick Penet wrote:
> Thank you for the patch !
> Could you please add it to the "patch tracker" ? It's easier for me to
> pick it up from there.
>
> http://sourceforge.net/tracker/?group_id=76550&atid=547457
>
> Yours,
> 	Perrick
>
> Jakob Ketterl wrote:
> > here's the patch i spoke of. this fixes the problem for me, however i
> > don't know whether it's not a little too rigorous to exclude all
> > non-existing files. maybe someone could have a look at it.
> >
> > also, this patch does not fix the problem of the errorhandling going
> > wild...
> >
> > On Tuesday 10 February 2009 10:42:14 Jakob Ketterl wrote:
> >> hi list,
> >>
> >> i've just checked out the current trunk and am trying to get the code
> >> coverage feature to work. unfortunately it seems that using the eval()
> >> function seems to break it completely. what i'm getting is this:
> >>
> >> Test cases run: 49/51, Passes: 777, Failures: 60, Exceptions: 37
> >>
> >> Fatal error: Maximum function nesting level of '100' reached, aborting!
> >> in /home/jketterl/workspace/SimpleTest/errors.php on line 274
> >>
> >> Call Stack:
> >>     0.0015     115276   1. {main}
> >> () /home/jketterl/workspace/me/tests/index.php:0
> >>    30.4381   20075780   2.
> >> CodeCoverage->stopCoverage()
> >> /home/jketterl/workspace/me/tests/index.php:152 30.5230   21371992   3.
> >> CoverageDataHandler->write()
> >> /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage.php:91
> >> 31.9787   21403664   4.
> >> SQLiteDatabase->queryExec()
> >> /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage_data_ha
> >>ndl er.php:44 31.9788   21404320   5.
> >> SimpleTestErrorHandler()
> >> /home/jketterl/workspace/SimpleTest/errors.php:0 31.9802   21404516   6.
> >> SimpleErrorQueue->add()
> >> /home/jketterl/workspace/SimpleTest/errors.php:241 31.9806   21404580  
> >> 7.
> >> SimpleErrorQueue->testLatestError()
> >> /home/jketterl/workspace/SimpleTest/errors.php:121 31.9809   21404644  
> >> 8. SimpleTestCase->error()
> >> /home/jketterl/workspace/SimpleTest/errors.php:157 31.9810   21404772  
> >> 9.
> >> trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
> >>    31.9810   21405140  10.
> >> SimpleTestErrorHandler()
> >> /home/jketterl/workspace/SimpleTest/errors.php:0 31.9816   21405312  11.
> >> SimpleErrorQueue->add()
> >> /home/jketterl/workspace/SimpleTest/errors.php:241 31.9817   21405520 
> >> 12.
> >> SimpleErrorQueue->testLatestError()
> >> /home/jketterl/workspace/SimpleTest/errors.php:121 31.9820   21405584 
> >> 13. SimpleTestCase->error()
> >> /home/jketterl/workspace/SimpleTest/errors.php:157 31.9821   21405784 
> >> 14.
> >> trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
> >>    31.9821   21406344  15.
> >> SimpleTestErrorHandler()
> >> /home/jketterl/workspace/SimpleTest/errors.php:0 31.9827   21406592  16.
> >> SimpleErrorQueue->add()
> >> /home/jketterl/workspace/SimpleTest/errors.php:241 31.9829   21406812 
> >> 17.
> >> SimpleErrorQueue->testLatestError()
> >> /home/jketterl/workspace/SimpleTest/errors.php:121
> >>
> >> [snip]
> >>
> >> it just keeps repeating from there on.
> >>
> >> i've inserted an echo statement just for debugging and it seems as if
> >> the code trips on this sqlite statement:
> >>
> >> insert into coverage (name, coverage) values
> >> ('/home/jketterl/workspace/me/library/Cxo/Filter/Element.php(212) :
> >> eval()'d code', 'a:3:{i:1;i:1;i:2;i:1;i:3;i:1;}')
> >>
> >> seems reasonable, since there's an unmatched quote in there, which
> >> should raise an error (i'm having a different system though where this
> >> results in a segfault, but that's a different story...)
> >>
> >> i'm trying to get a patch that would block invalid sql statements, but
> >> the stack trace above looks like there's some kind of error handling
> >> active that should only trip on tests, but not on simpletests own code.
> >>
> >> any advice how to handle this?
> >>
> >> ------------------------------------------------------------------------
> >>--- --- Create and Deploy Rich Internet Apps outside the browser with
> >> Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use
> >> existing skills and code to build responsive, highly engaging
> >> applications that combine the power of local resources and data with the
> >> reach of the web. Download the Adobe AIR SDK and Ajax docs to start
> >> building applications today-http://p.sf.net/sfu/adobe-com
> >> _______________________________________________
> >> Simpletest-support mailing list
> >> Sim...@li...
> >> https://lists.sourceforge.net/lists/listinfo/simpletest-support
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> >----- Create and Deploy Rich Internet Apps outside the browser with
> > Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use
> > existing skills and code to build responsive, highly engaging
> > applications that combine the power of local resources and data with the
> > reach of the web. Download the Adobe AIR SDK and Ajax docs to start
> > building applications today-http://p.sf.net/sfu/adobe-com
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Simpletest-support mailing list
> > Sim...@li...
> > https://lists.sourceforge.net/lists/listinfo/simpletest-support
>
> ---------------------------------------------------------------------------
>--- Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing
> skills and code to build responsive, highly engaging applications that
> combine the power of local resources and data with the reach of the web.
> Download the Adobe AIR SDK and Ajax docs to start building applications
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support

[Simpletest-support] Bug Report: Incompatibility with MediaWiki

[Lambert L. <la...@bl...>]

I hope this is the right place to report a bug.

I am using SimpleTest with MediaWiki. During the course of writing test 
scripts I noticed that anything that dealt with editing wiki pages was 
failing. Upon closer inspection, I noticed that Simple Test was choking on a 
hidden form element, named wpEditToken. This wpEditToken's value is a string 
that ends in '\'.

<input type='hidden' value="99b0c5b089d852f6c490d9ac17ae4c3a+\" 
name="wpEditToken" />

My guess is that the SimpleTest parser interprets the '\' as a special 
character and thus renders the value attribute unreadable.

Re: [Simpletest-support] Simpletest Code Coverage fails on eval'd code

[Perrick P. <pe...@no...>]

Thank you for the patch !
Could you please add it to the "patch tracker" ? It's easier for me to 
pick it up from there.

http://sourceforge.net/tracker/?group_id=76550&atid=547457

Yours,
	Perrick



Jakob Ketterl wrote:
> here's the patch i spoke of. this fixes the problem for me, however i don't 
> know whether it's not a little too rigorous to exclude all non-existing 
> files. maybe someone could have a look at it.
> 
> also, this patch does not fix the problem of the errorhandling going wild...
> 
> On Tuesday 10 February 2009 10:42:14 Jakob Ketterl wrote:
>> hi list,
>>
>> i've just checked out the current trunk and am trying to get the code
>> coverage feature to work. unfortunately it seems that using the eval()
>> function seems to break it completely. what i'm getting is this:
>>
>> Test cases run: 49/51, Passes: 777, Failures: 60, Exceptions: 37
>>
>> Fatal error: Maximum function nesting level of '100' reached, aborting!
>> in /home/jketterl/workspace/SimpleTest/errors.php on line 274
>>
>> Call Stack:
>>     0.0015     115276   1. {main}
>> () /home/jketterl/workspace/me/tests/index.php:0
>>    30.4381   20075780   2.
>> CodeCoverage->stopCoverage()
>> /home/jketterl/workspace/me/tests/index.php:152 30.5230   21371992   3.
>> CoverageDataHandler->write()
>> /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage.php:91
>> 31.9787   21403664   4.
>> SQLiteDatabase->queryExec()
>> /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage_data_handl
>> er.php:44 31.9788   21404320   5.
>> SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
>>    31.9802   21404516   6.
>> SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
>>    31.9806   21404580   7.
>> SimpleErrorQueue->testLatestError()
>> /home/jketterl/workspace/SimpleTest/errors.php:121 31.9809   21404644   8.
>> SimpleTestCase->error() /home/jketterl/workspace/SimpleTest/errors.php:157
>>    31.9810   21404772   9.
>> trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
>>    31.9810   21405140  10.
>> SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
>>    31.9816   21405312  11.
>> SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
>>    31.9817   21405520  12.
>> SimpleErrorQueue->testLatestError()
>> /home/jketterl/workspace/SimpleTest/errors.php:121 31.9820   21405584  13.
>> SimpleTestCase->error() /home/jketterl/workspace/SimpleTest/errors.php:157
>>    31.9821   21405784  14.
>> trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
>>    31.9821   21406344  15.
>> SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
>>    31.9827   21406592  16.
>> SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
>>    31.9829   21406812  17.
>> SimpleErrorQueue->testLatestError()
>> /home/jketterl/workspace/SimpleTest/errors.php:121
>>
>> [snip]
>>
>> it just keeps repeating from there on.
>>
>> i've inserted an echo statement just for debugging and it seems as if the
>> code trips on this sqlite statement:
>>
>> insert into coverage (name, coverage) values
>> ('/home/jketterl/workspace/me/library/Cxo/Filter/Element.php(212) :
>> eval()'d code', 'a:3:{i:1;i:1;i:2;i:1;i:3;i:1;}')
>>
>> seems reasonable, since there's an unmatched quote in there, which should
>> raise an error (i'm having a different system though where this results in
>> a segfault, but that's a different story...)
>>
>> i'm trying to get a patch that would block invalid sql statements, but the
>> stack trace above looks like there's some kind of error handling active
>> that should only trip on tests, but not on simpletests own code.
>>
>> any advice how to handle this?
>>
>> ---------------------------------------------------------------------------
>> --- Create and Deploy Rich Internet Apps outside the browser with
>> Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing
>> skills and code to build responsive, highly engaging applications that
>> combine the power of local resources and data with the reach of the web.
>> Download the Adobe AIR SDK and Ajax docs to start building applications
>> today-http://p.sf.net/sfu/adobe-com
>> _______________________________________________
>> Simpletest-support mailing list
>> Sim...@li...
>> https://lists.sourceforge.net/lists/listinfo/simpletest-support
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code to
> build responsive, highly engaging applications that combine the power of local
> resources and data with the reach of the web. Download the Adobe AIR SDK and
> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support

Re: [Simpletest-support] Simpletest Code Coverage fails on eval'd code

[Jakob K. <jke...@ch...>]

here's the patch i spoke of. this fixes the problem for me, however i don't 
know whether it's not a little too rigorous to exclude all non-existing 
files. maybe someone could have a look at it.

also, this patch does not fix the problem of the errorhandling going wild...

On Tuesday 10 February 2009 10:42:14 Jakob Ketterl wrote:
> hi list,
>
> i've just checked out the current trunk and am trying to get the code
> coverage feature to work. unfortunately it seems that using the eval()
> function seems to break it completely. what i'm getting is this:
>
> Test cases run: 49/51, Passes: 777, Failures: 60, Exceptions: 37
>
> Fatal error: Maximum function nesting level of '100' reached, aborting!
> in /home/jketterl/workspace/SimpleTest/errors.php on line 274
>
> Call Stack:
>     0.0015     115276   1. {main}
> () /home/jketterl/workspace/me/tests/index.php:0
>    30.4381   20075780   2.
> CodeCoverage->stopCoverage()
> /home/jketterl/workspace/me/tests/index.php:152 30.5230   21371992   3.
> CoverageDataHandler->write()
> /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage.php:91
> 31.9787   21403664   4.
> SQLiteDatabase->queryExec()
> /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage_data_handl
>er.php:44 31.9788   21404320   5.
> SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
>    31.9802   21404516   6.
> SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
>    31.9806   21404580   7.
> SimpleErrorQueue->testLatestError()
> /home/jketterl/workspace/SimpleTest/errors.php:121 31.9809   21404644   8.
> SimpleTestCase->error() /home/jketterl/workspace/SimpleTest/errors.php:157
>    31.9810   21404772   9.
> trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
>    31.9810   21405140  10.
> SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
>    31.9816   21405312  11.
> SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
>    31.9817   21405520  12.
> SimpleErrorQueue->testLatestError()
> /home/jketterl/workspace/SimpleTest/errors.php:121 31.9820   21405584  13.
> SimpleTestCase->error() /home/jketterl/workspace/SimpleTest/errors.php:157
>    31.9821   21405784  14.
> trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
>    31.9821   21406344  15.
> SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
>    31.9827   21406592  16.
> SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
>    31.9829   21406812  17.
> SimpleErrorQueue->testLatestError()
> /home/jketterl/workspace/SimpleTest/errors.php:121
>
> [snip]
>
> it just keeps repeating from there on.
>
> i've inserted an echo statement just for debugging and it seems as if the
> code trips on this sqlite statement:
>
> insert into coverage (name, coverage) values
> ('/home/jketterl/workspace/me/library/Cxo/Filter/Element.php(212) :
> eval()'d code', 'a:3:{i:1;i:1;i:2;i:1;i:3;i:1;}')
>
> seems reasonable, since there's an unmatched quote in there, which should
> raise an error (i'm having a different system though where this results in
> a segfault, but that's a different story...)
>
> i'm trying to get a patch that would block invalid sql statements, but the
> stack trace above looks like there's some kind of error handling active
> that should only trip on tests, but not on simpletests own code.
>
> any advice how to handle this?
>
> ---------------------------------------------------------------------------
>--- Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing
> skills and code to build responsive, highly engaging applications that
> combine the power of local resources and data with the reach of the web.
> Download the Adobe AIR SDK and Ajax docs to start building applications
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support

Re: [Simpletest-support] SimpleTest 1.1beta

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

Hi...

Perrick Penet wrote:
> It means we can now roll out ST 1.1beta ! Marcus, you have my green light.

I have to beg internet connections at the moment until I get broadband
hooked up. I'll wade into the docs offline, and then do a release.

> 
> 	Perrick

yours, Marcus

p.s. You coming to the conference on the 27th? http://phpconference.co.uk

yours, Marcus

[Simpletest-support] Simpletest Code Coverage fails on eval'd code

[Jakob K. <jke...@ch...>]

hi list,

i've just checked out the current trunk and am trying to get the code coverage 
feature to work. unfortunately it seems that using the eval() function seems 
to break it completely. what i'm getting is this:

Test cases run: 49/51, Passes: 777, Failures: 60, Exceptions: 37

Fatal error: Maximum function nesting level of '100' reached, aborting! 
in /home/jketterl/workspace/SimpleTest/errors.php on line 274

Call Stack:
    0.0015     115276   1. {main}
() /home/jketterl/workspace/me/tests/index.php:0
   30.4381   20075780   2. 
CodeCoverage->stopCoverage() /home/jketterl/workspace/me/tests/index.php:152
   30.5230   21371992   3. 
CoverageDataHandler->write() /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage.php:91
   31.9787   21403664   4. 
SQLiteDatabase->queryExec() /home/jketterl/workspace/SimpleTest/extensions/coverage/coverage_data_handler.php:44
   31.9788   21404320   5. 
SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
   31.9802   21404516   6. 
SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
   31.9806   21404580   7. 
SimpleErrorQueue->testLatestError() /home/jketterl/workspace/SimpleTest/errors.php:121
   31.9809   21404644   8. 
SimpleTestCase->error() /home/jketterl/workspace/SimpleTest/errors.php:157
   31.9810   21404772   9. 
trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
   31.9810   21405140  10. 
SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
   31.9816   21405312  11. 
SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
   31.9817   21405520  12. 
SimpleErrorQueue->testLatestError() /home/jketterl/workspace/SimpleTest/errors.php:121
   31.9820   21405584  13. 
SimpleTestCase->error() /home/jketterl/workspace/SimpleTest/errors.php:157
   31.9821   21405784  14. 
trigger_error() /home/jketterl/workspace/SimpleTest/test_case.php:274
   31.9821   21406344  15. 
SimpleTestErrorHandler() /home/jketterl/workspace/SimpleTest/errors.php:0
   31.9827   21406592  16. 
SimpleErrorQueue->add() /home/jketterl/workspace/SimpleTest/errors.php:241
   31.9829   21406812  17. 
SimpleErrorQueue->testLatestError() /home/jketterl/workspace/SimpleTest/errors.php:121

[snip]

it just keeps repeating from there on.

i've inserted an echo statement just for debugging and it seems as if the code 
trips on this sqlite statement:

insert into coverage (name, coverage) values 
('/home/jketterl/workspace/me/library/Cxo/Filter/Element.php(212) : eval()'d 
code', 'a:3:{i:1;i:1;i:2;i:1;i:3;i:1;}')

seems reasonable, since there's an unmatched quote in there, which should 
raise an error (i'm having a different system though where this results in a 
segfault, but that's a different story...)

i'm trying to get a patch that would block invalid sql statements, but the 
stack trace above looks like there's some kind of error handling active that 
should only trip on tests, but not on simpletests own code.

any advice how to handle this?

Re: [Simpletest-support] SimpleTest 1.1beta

[Perrick P. <pe...@no...>]

Hi,

> OK. Can we grep for a $_reporter just in case?

Done in core.

>> For item 2/, we still need someone to pick up the task. If noboby is up 
>> for it, I feel we can postpone this feature. I feel that getting some 
>> feedback on the code coverage stuff is a lot more crucial.
> 
> Agreed.

It means we can now roll out ST 1.1beta ! Marcus, you have my green light.

	Perrick

Re: [Simpletest-support] Simpletest Eclipse plugin update site

[Perrick P. <pe...@no...>]

If you need to have an account on the webserver, you need to talk to 
Jeff Moore <je...@pr...>.

If you have some content ready for deployment, you can just send me a 
mail and since I already have an account, I can sftp the files for you.

Yours,
	Perrick



Steven Balthazor wrote:
> Who should I speak with to get the Eclipse plugin update site updated
> with the most current plugin?
> 
> The update site is located at:
> 
> http://simpletest.org/eclipse/
> 
> The last plugin installed there is the 0.2.1 version; the most current
> version is 0.2.5 .
> 
> Previously I was able to make the changes by updating an appropriate
> directory in the Sourceforge system; however it appears that this is
> no longer the case (and it probably has been this way for well over a
> year).
> 
> Thanks for any help.
> 
> Regards,
> Steven Balthazor
> 
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code to
> build responsive, highly engaging applications that combine the power of local
> resources and data with the reach of the web. Download the Adobe AIR SDK and
> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
> 
> 

[Simpletest-support] Simpletest Eclipse plugin update site

[Steven B. <ste...@gm...>]

Who should I speak with to get the Eclipse plugin update site updated
with the most current plugin?

The update site is located at:

http://simpletest.org/eclipse/

The last plugin installed there is the 0.2.1 version; the most current
version is 0.2.5 .

Previously I was able to make the changes by updating an appropriate
directory in the Sourceforge system; however it appears that this is
no longer the case (and it probably has been this way for well over a
year).

Thanks for any help.

Regards,
Steven Balthazor

Re: [Simpletest-support] SimpleTest 1.1beta

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

Hi...

Perrick Penet wrote:
> For item 1/, I think the author solved it in his code ("Figured it 
> out."). So I feel we can drop the report now ;-)

OK. Can we grep for a $_reporter just in case?

> 
> For item 2/, we still need someone to pick up the task. If noboby is up 
> for it, I feel we can postpone this feature. I feel that getting some 
> feedback on the code coverage stuff is a lot more crucial.

Agreed.

> Yours,
> 	Perrick

yours, Marcus

Re: [Simpletest-support] SimpleTest 1.1beta

[Perrick P. <pe...@no...>]

Hi,


>> I haven't seen it in /trunk yet. I think it's still in its own branch. 
>> Maybe we can port it to trunk now ? What do you think ??
> 
> If it's easy to use and works, then it should go in. We won't announce
> it, but it should be in there.

It's in now (the code coverage stuff).

> I'll leave the final choices up to you though. My main job (once I've
> moved house in two weeks) is to finish the core documentation. It makes
> sense for you to take on the role of buildmeister for a little bit (if
> you are willing?).

And I finally have some time. We moved house in december as well ;-) And 
No Parking (my company) will change offices soon as well.

On our TODO master plan, there are 2 items left before we can release :

1/ an old bug [ 1896582 ] Undefined property $_reporter + fatal error
http://sourceforge.net/tracker/index.php?func=detail&group_id=76550&atid=547455&aid=1896582

2/ Update PEAR package task to be compatible with latest PEAR installer.

For item 1/, I think the author solved it in his code ("Figured it 
out."). So I feel we can drop the report now ;-)

For item 2/, we still need someone to pick up the task. If noboby is up 
for it, I feel we can postpone this feature. I feel that getting some 
feedback on the code coverage stuff is a lot more crucial.

By the way, I'd love to have some documentation on "how to code-coverage 
my code". Douglas : would you be kind enough to add something in the 
docs/source/en directory ? The XML format we use should be trivial 
enough to figure out and use.

Anyway, I hope we can release 1.1beta by the end of this month (that's 
my target anyway).

Yours,
	Perrick