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

[Simpletest-support] Problems with Ubuntu

[Phauxe K. <pha...@gm...>]

Hi all,

I've started using SimpleTest to test php code for a new project that I'm
working on.  I managed to install the plug-in for eclipse under Vista and XP
with ease.  However, Ubuntu has been another story altogether.  Whenever I
try to run a php class as a SimpleTest, nothing happens.  I don't receive
the Results view, and I don't receive any errors in the console or
otherwise; absolutely nothing happens.  I've spent the day googling for a
solution to no avail, and am hoping that someone on this list can help me
out.  Are there extra steps that need to be taken to get SimpleTest to work
under Ubuntu?

Any help would be much appreciated.

-Phauxe

[Simpletest-support] Follow Up to New User Question

[<cho...@gm...>]

I have included a fairly simple selection of files here as I think I  
followed Marcus's suggestion to get running, without anything actually  
running. I have stripped everything to try to make this simple to follow.

My directories:
Q:\Simpletest\
Q:\Application\
test.php
Q:\Application\DB\
a.class.php
a.class.test.php
Q:\Application\UTIL\
b.class.php
b.class.test.php

The Code
A.class
<?php
class A_CLASS
{
public $Var1;
function __construct($Var = NULL)
{ $Var1 = $Var; }
}
?>

A.class.test
<?php
require_once('/simpletest/autorun.php');
class UnitTest extends UnitTestCase {
function setUp() {
if(! class_exists(substr(__FILE__, 0 , -11)))
require_once(substr(__FILE__, 0 , -5));
}

function tearDown() { }

function testConstructor() {
$AClass = new A_CLASS('A-Test');
$this->assertTrue($AClass->Var1 == 'A-Test');
}
}
?>

B.class
<?php
class B_CLASS
{
public $Var1;
function __construct($Var = NULL) {
$Var1 = $Var;
}
}
?>

B.class.test
<?php
require_once('/simpletest/autorun.php');
class UnitTest extends UnitTestCase {
function setUp() {
if(! class_exists(substr(__FILE__, 0 , -11)))
require_once(substr(__FILE__, 0 , -5));
}

function tearDown() { }

function testConstructor() {
$BClass = new B_CLASS('B-Test');
$this->assertTrue($BClass->Var1 == 'B-Test');
}
}
?>

test.php
<?php
require_once(dirname(__FILE__) . '/../simpletest/autorun.php');
require_once(dirname(__FILE__) . '/../simpletest/collector.php');
class UnitTests extends TestSuite {
function __construct() {
parent::__construct();
$this->collect(dirname(__FILE__) . '/DB/', new  
SimplePatternCollector('/.test$/'));
$this->collect(dirname(__FILE__) . '/UTIL/', new  
SimplePatternCollector('/.test$/'));
}
}
$Testing = new UnitTests();
?>

This returns the error:
PHP Fatal error: Only variables can be passed by reference in  
Q:\simpletest\autorun.php on line 57

I think I am just missing something simple. Thanks in advance for the help.

Re: [Simpletest-support] SimpleTest & Phing & Pear

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

On Thu, Jan 22, 2009 at 1:10 PM, Marcus Baker <ma...@wo...> wrote:
>> PS: I've also looked for simpletest ant task but didn't find anything :(
>
> A couple have been written, but bundled into other packages. We
> should have links to this stuff in our web site. When I get some
> time... :(
>

Well. My phing investigation is over. Classpath issues (more or less
fixed) and... namespace issues : my project use classes like Project,
Reference, ... And so does phing. "Cannot redeclare class Project." :(

I'm definitively looking for an ant task. I hope there will be less issues :-\

Thanks,
Nicolas Terray

Re: [Simpletest-support] SimpleTest & Phing & Pear

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

On Thu, Jan 22, 2009 at 2:39 PM, tarjei <ta...@nu...> wrote:
>> Nicolas Terray wrote:
>>> if (!class_exists('SimpleReporter')) {
>>>    throw new BuildException("SimpleTestTask depends on SimpleTest
>>> package being installed.
>>>
>>>
>>> How can I do that?
> I've been using simpletest + phing for quite some time. All I have done
> earlier has been to install simpletest into my PEAR directory.
>

cp -r simpletest /opt/tools/FC8/php-5.1.6/lib/php/PEAR/
doesn't work

The include_path is the following:
.:/opt/tools/FC8/php-5.1.6/lib/php

cp -r simpletest /opt/tools/FC8/php-5.1.6/lib/php/
works

I should be happy. However I don't like putting things by hand in php
directories. :(
I would like to keep my simpletest directory in my workspace.
Is there a way to set the include path when calling the command "phing" ?

The answer is yes. :)
Use PHP_CLASSPATH environment variable...

I do love those issues which require me to parse library scripts to
find what to do :-\

Now I am happy :)

Thanks for your help!
Nicolas Terray

Re: [Simpletest-support] SimpleTest & Phing & Pear

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

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

Hi,
Marcus Baker wrote:
> Hi...
> 
> Nicolas Terray wrote:
>> if (!class_exists('SimpleReporter')) {
>>    throw new BuildException("SimpleTestTask depends on SimpleTest
>> package being installed.
>>
>>
>> How can I do that?
I've been using simpletest + phing for quite some time. All I have done
earlier has been to install simpletest into my PEAR directory.

Did you try that?

> Maybe it's enough for the simpletest folder to be in the path. Your 
> best bet is to ask the Phing guys. We don't have a PEAR package and 
> I'd love a volunteer to build one.
Wish I had the time, maybe soon :)

mvh
Tarjei

>> PS: I've also looked for simpletest ant task but didn't find anything :(
> 
> A couple have been written, but bundled into other packages. We 
> should have links to this stuff in our web site. When I get some 
> time... :(
> 
> yours, Marcus
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> 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

iD8DBQFJeHchYVRKCnSvzfIRAqKdAJ9NGyxPU+4yTQbFfWqZXwZZgEYioACghehT
HNqig8Fj+a+goRv0tC1ClpU=
=qpug
-----END PGP SIGNATURE-----

Re: [Simpletest-support] New User Question

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

Hi...

Sorry about the delay in replying to this. Getting ready to move house.

Steven Scott wrote:
> I have been reading the limited tutorials, I am having some trouble using
> some generic attempts to run.  I am trying to not hard code my tests with
> the basic test from the sample.

The tutorial is a little behind the code base. I'm trying to correct 
this now.

> 
> I have a number of classes, that I am building a TEST class for.  I am
> looking to loop through them all and run them, but simple looping gives me
> an error in the dummy.php file from the autorn.php routine.

It might have found a file that does not have any tests in. Probably 
the "." directory. Anyway, there is a better way...

Build your test files using this...

require_once('simpletest/autorun.php');

You'll need to get the paths right for your setup. Don't place any 
runner code at the bottom of the script, just have this at the top 
and your test cases.

Now invoking the file on the command line or in the browser should 
run the test. Here is the simplest version I could come up with...

<?php
require_once('simpletest/autorun.php');

class PassingTests extends UnitTestCase {
     function testNothingReally() { $this->assertEqual(1, 1); }
}
?>

That should just run. Now your test suites and groupings come in 
other files. Say the file above is in a folder called "unit", the 
"unit_tests.php" runner can be...

<?php
require_once(dirname(__FILE__) . '/../external/test_autorun.php');
require_once(dirname(__FILE__) . '/simpletest/collector.php');

class UnitTests extends TestSuite {
     function __construct() {
         parent::__construct();
         $this->collect(
                 dirname(__FILE__) . '/unit/',
                 new SimplePatternCollector('/_test(s?).php$/'));
     }
}
?>

This scoops up any files ending in "...test.php" and runs them. 
Works for nested groups too.

> I am trying to do this generically so after I add
> a new class and test file I do not have to change anything for it to be
> picked up.  I have used the run() successfully on a single file, but I am
> trying for something more generic.

The code above will do the trick.

> Steven Scott

yours, Marcus

Re: [Simpletest-support] SimpleTest & Phing & Pear

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

Hi...

Nicolas Terray wrote:
> 
> if (!class_exists('SimpleReporter')) {
>    throw new BuildException("SimpleTestTask depends on SimpleTest
> package being installed.
> 
> 
> How can I do that?

Maybe it's enough for the simpletest folder to be in the path. Your 
best bet is to ask the Phing guys. We don't have a PEAR package and 
I'd love a volunteer to build one.

> PS: I've also looked for simpletest ant task but didn't find anything :(

A couple have been written, but bundled into other packages. We 
should have links to this stuff in our web site. When I get some 
time... :(

yours, Marcus

[Simpletest-support] SimpleTest & Phing & Pear

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

Hi all :)

I've just discovered that there is a simpletest task in the latest
release of phing.
As I am configuring a Continuous Integration server for my project
based on Hudson,  I think this task will be helpfull.

But this task isn't documented. Not yet:

http://phing.info/trac/ticket/303



If we look at the constructor of the task

http://phing.info/trac/browser/branches/2.3/classes/phing/tasks/ext/simpletest/SimpleTestTask.php

we can see that it requires that simpletest is loaded:

if (!class_exists('SimpleReporter')) {
   throw new BuildException("SimpleTestTask depends on SimpleTest
package being installed.


How can I do that?


I've tried to do a

pear install http://ovh.dl.sourceforge.net/sourceforge/simpletest/simpletest_1.0.1.tar.gz

However it doesn't work: "[...]but it is not a valid package archive"



My build.xml file is the following:

<?xml version="1.0"?>
<project default="tests" basedir=".">
        <target name="tests">
                <echo msg="Tests..." />
                <simpletest>
                        <fileset dir=".">
                                <include name="**/*Test.php">
                        </fileset>
                </simpletest>
        </target>
</project>


As I don't kown well pear neither phing, I'm pretty lost. Any help to
run my tests with phing is welcome :)

Thanks,
Nicolas Terray

PS: I've also looked for simpletest ant task but didn't find anything :(

[Simpletest-support] New User Question

[Steven S. <cho...@gm...>]

I have been reading the limited tutorials, I am having some trouble using
some generic attempts to run.  I am trying to not hard code my tests with
the basic test from the sample.

I have a number of classes, that I am building a TEST class for.  I am
looking to loop through them all and run them, but simple looping gives me
an error in the dummy.php file from the autorn.php routine.

My structure:
DB/TABLE1.class.php
DB/TABLE1.class.test.php
SYS/TABLE2.class.php
SYS/TABLE2.class.test.php
...

My *.test.php does something like:
<?php

if (!class_exists('DB_TABLE1'))           // Actually build from DIRECTORY _
FILENAME
    require_once(substr(__FILE__, 0, -9) . '.php');  // strip '.test'
extension

class TEST_TABLE1 extends UnitTestCase {

     function TestCreate()
     {
          $Table = new DB_TABLE1();
          $this->assertIsA($Table, 'DB_TABLE1');
     }

   function TestConstructor()
   ...
   function TestFunction()
   ....
}
?>

The error with the dummy.php is causing me a problem.  Is there a better
document or another sample to help me implement these tests?  I am trying to
configure these to run a couple times a day to ensure that nothing in my
source code gets broken.  I am trying to do this generically so after I add
a new class and test file I do not have to change anything for it to be
picked up.  I have used the run() successfully on a single file, but I am
trying for something more generic.

Any help will be appreciated.

Thanks in advance...

Steven Scott

Re: [Simpletest-support] Show stacktraces

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

Hi...

tarjei wrote:
> Hi, here's a quick patch to add the ability for TextReporter to print
> out a stacktrace of an exception in one of the tests.

Cool.

> 
> I didn't find ut where to write the test (didn't look to closely), but
> would appreciate it if someone could advise me on that point.

There aren't really any for the reporters. There is a deliberately
failing visual test that displays every kind of message. Unfortunately
it hasn't been converted to E_STRICT compliance yet. A trivial detail
that we forgot. I'll add it to the TODO.

> Usage:
> The printStackTrace variable can be set if you want simpletest to print
> stacktraces as well as the normal message.

Where does this happen? I think we'll probably make it always do the
trace. Means we have to get the XML version working too, and the HTML one.

Suddenly it's a lot more work, isn't it? :)

Instead of a patch, do you mind if we consider it a feature request?

> kind regards,
> Tarjei

yours, Marcus
yours, Marcus

[Simpletest-support] Show stacktraces

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

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

Hi, here's a quick patch to add the ability for TextReporter to print
out a stacktrace of an exception in one of the tests.

I didn't find ut where to write the test (didn't look to closely), but
would appreciate it if someone could advise me on that point.

Usage:
The printStackTrace variable can be set if you want simpletest to print
stacktraces as well as the normal message.



kind regards,
Tarjei

Index: reporter.php
===================================================================
- --- reporter.php	(revision 3994)
+++ reporter.php	(working copy)
@@ -203,6 +203,9 @@
         $this->SimpleReporter();
     }

+    public $printStackTrace = false;
+
+
     /**
      *    Paints the title only.
      *    @param string $test_name        Name class of test.
@@ -278,6 +281,9 @@
                 '] in ['. $exception->getFile() .
                 ' line ' . $exception->getLine() . ']';
         print "Exception " . $this->getExceptionCount() . "!\n$message\n";
+        if ($this->printStackTrace ){
+            print $exception->getTraceAsString() . "\n";
+        }
         $breadcrumb = $this->getTestList();
         array_shift($breadcrumb);
         print "\tin " . implode("\n\tin ", array_reverse($breadcrumb));
@@ -444,4 +450,4 @@
      */
     function paintSkip($message) { }
 }
- -?>
\ No newline at end of file
+?>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJa2gJYVRKCnSvzfIRAgKgAKCqNDY50QI/nnDJQRlpmnRyKYOIEgCgtS/K
QM36pwCNGVpYSjoB6QAvfvk=
=mX5d
-----END PGP SIGNATURE-----

Re: [Simpletest-support] SimpleTest 1.1beta

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

I committed code_coverage branch into trunk, autorun.php change slightly, and
there was a couple changes to documentation pp11 made, but otherwise everything
was just new files in extensions/coverage

Re: [Simpletest-support] Bug report/fix

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

Hi...

T.J.Hunt wrote:
> The attached patch cleans it up. Not sure if you want it in the official simpletest distro, but I offer it anyway. We are using Simpletest 1.0.1.

Marvellous. We like patches :).

We'll try to test the patch (and add a unit test to enforce the
bahaviour) before the next release.

> Thank you for making simpletest available.

Thank you for using it :).

> 
> Tim.

yours, Marcus

Re: [Simpletest-support] SimpleTest 1.1beta

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

Hi...

Perrick Penet wrote:
> 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.

I think the Selenium stuff should probably go in too, and the TestDox
reporter if it isn't already (all unannounced).

Also, I think Recorder can come out of extensions and be moved to core.

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?).

> 
> Yours,
> 	Perrick

yours, Marcus

Re: [Simpletest-support] SimpleTest 1.1beta

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

Hi Douglas,

Douglas Hubler wrote:
> Marcus Baker <marcus@...> writes:
>> Douglas Hubler wrote:
>>> Please let's put code coverage in.
>> It probably will be (in the extensions folder).
> y, that's where it is now based on previous feedback.

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

Yours,
	Perrick

Re: [Simpletest-support] SimpleTest 1.1beta

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

Marcus Baker <marcus@...> writes:
> Douglas Hubler wrote:
> > Please let's put code coverage in.
> It probably will be (in the extensions folder).
y, that's where it is now based on previous feedback.

[Simpletest-support] Bug report/fix

[T.J.Hunt <T.J...@op...>]

Apologies for just dumping this on the mailing list, rather than discovering the best way to submit patches to this project, but I have just spend a grim couple of hours fighting this bug, and I just want to get it out of the way and move on.


OK, so the problem we hit was that we were relying on the destructor of our test class being called immediately after a test was run, before the next one was constructed.

I know, that is probably stupid, but still.

And the problem we had was that SimpleTestContext was keeping a reference to the last test run, even after it had finished running.


The attached patch cleans it up. Not sure if you want it in the official simpletest distro, but I offer it anyway. We are using Simpletest 1.0.1.

I am happy to discuss this further if you like.


Thank you for making simpletest available.

Tim.

---------------------------------
The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).

Re: [Simpletest-support] 302 Redirect with usePoxy

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

Hi...

popescu gabriel wrote:
> Bottom Line : I can't get it to follow a redirect when i use a proxy.

Can you phrase it as a failing test? I can then look into it more 
easily. Actually two tests. A passing one without the proxy and the 
failing one with. When I get the test passing, I'll notify you.

Also, can you add this to the Sourceforge bug tracker. We are 
working on a release right now, so work on your bug may be a bit 
stop and start.

yours, Marcus

[Simpletest-support] 302 Redirect with usePoxy

[popescu g. <pop...@ya...>]

Hello !
When i get the http://www.google.com the simple test follows the redirect and gives me the http://wwww.google.ro.
The situation changes when i try the same thing using a proxy.<?php
require_once('simpletest/browser.php');
    
$browser = &new SimpleBrowser();$browser->useProxy('http://91.122.205.235:37330','','');
$page = $browser->get('http://www.google.com');
print $page;
?>[Donno if the proxy will still work till u get the change to look over it]Bottom Line : I can't get it to follow a redirect when i use a proxy.



      

Re: [Simpletest-support] class WebTestCase extends SimpleTestCase

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

Hi...

troels knak-nielsen wrote:
> A lot of basic assertions (Such as assertNull), are defined in
> UnitTestCase, so these aren't currently available inside of a
> WebTestCase.

Just that they wee two very different things and OO purity
(implementations not extending implementations) got the better of me.

Once I get everything transitioned to PHP5 only, I'll do a
plug-in/aggregation system.

> 
> --
> troels

yours, Marcus

[Simpletest-support] class WebTestCase extends SimpleTestCase

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

What is the reason behind class WebTestCase extends SimpleTestCase,
rather than UnitTestCase?

A lot of basic assertions (Such as assertNull), are defined in
UnitTestCase, so these aren't currently available inside of a
WebTestCase.

--
troels

Re: [Simpletest-support] SimpleTest 1.1beta

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

Perrick Penet wrote:
> I noticed the SVN URL did change along the way : I always thought "cool 
> URI didn't change". It broke our SVN externals link. I know the new URL 
> is better but still... I would have prefered a copy instead of a 
> straight rename. Thankfully the holiday season is very quiet !

Eek! Sorry about that. I'll be sure to copy in the future.

Edward

Re: [Simpletest-support] SimpleTest 1.1beta

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

Hi Edward,

> I'm going to branch the 1.0.1 tag into a 1.0 branch, and then add the
> appropriate methods. However, since 1.1 breaks a lot of
> "not-supposed-to-be-used" flex points, I expect people are going to have
> to fix things on 1.1 sans E_STRICT anyway.

I noticed the SVN URL did change along the way : I always thought "cool 
URI didn't change". It broke our SVN externals link. I know the new URL 
is better but still... I would have prefered a copy instead of a 
straight rename. Thankfully the holiday season is very quiet !

Yours,
	Perrick

Re: [Simpletest-support] SimpleTest 1.1beta

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

Hi...

Perrick Penet wrote:
> And if I can have 2/3 days for the French version afterwards, I'd be 
> really happy ;-) Otherwise I'll play catch up just after.

I'm sure I can manage plenty of warning this time :). It's just so easy
to jump the gun when the release is ready to go...

> 
> Yours,
> 	Perrick

yours, Marcus

Re: [Simpletest-support] SimpleTest 1.1beta

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

And if I can have 2/3 days for the French version afterwards, I'd be 
really happy ;-) Otherwise I'll play catch up just after.

Yours,
	Perrick



Marcus Baker wrote:
> Hi...
> 
> Douglas Hubler wrote:
>> Please let's put code coverage in.
> 
> It probably will be (in the extensions folder). The main thing is for me
> to finish the current round of doc updates. The docs are in a bit of a
> half and half state right now.
> 
> yours, Marcus