simpletest-support Mailing List for SimpleTest (Page 14)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Zack Wickes

h: 604-469-2912

c: 604-789-9817

On Mon, Sep 7, 2009 at 11:53 PM, Richard Archer<rh...@ju...> wrote:
> Greetings,
>
> I'm trying to install simpletest_1.0.1.eclipse_0.2.5 into Eclipse.
>
> My Eclipse installation details window says in summary:
>
> Eclipse IDE for PHP Developers 1.2.0.20090618-0925
> Eclipse Platform               3.5.0.I20090611-1540
> Eclipse Platform               3.5.0.v20090611a
> PHP Development Tools (PDT)    2.1.0.v20090611-0930
> Simpletest plug-in             0.2.5
>
> Is the plugin just not compatible with this version of Eclipse?
> Or have I missed something?
>
>  ...Richard.

Hello,

I just tried installing the Simpletest plugin into Eclipse 3.5 and
something is not right (if you go to the Simpletest preference page it
fails to load -- or at least in my current configuration -- I suspect
there is some missing dependency not being loaded or missing)

All that being said, there is a much simpler (and more productive --
because it allows you to debug) way to run Simpletest in Eclipse.

I wrote the plugin and have maintained compatibility with Eclipse
through many iterations; however I think the plugin has outlived it
usefulness (or rather the toolset can now more easily provide the
functionality).

To easily run Simpletest in Eclipse:
Download the latest tgz from the website (1.0.1) and extract somewhere

In Eclipse create a new project:
File -> New -> Project...
Expand "General" and select "Project"
enter a name for the project ("Test"?) and press "Finish"
Right click on the project created and select "New File"
enter a file name ("simple_test.php"?)
copy the folder ("simpletest") you extracted above into the project you created

The project tree should look like:

Test
  + simpletest
  simple_test.php

If you expand the simpletest folder you should have three folders
underneath it (docs, extensions, test - the folders are not important,
I mention them to make sure that you have not unnecessarily included
too many folders above the simpletest folder) and all the simpletest
php files.

now you need to setup php in Eclipse:
Window -> Preferences
Expand "PHP"
Select "PHP Executables"
Add a valid PHP executable [I won't go into details here because it varies]
Press the "OK" button to close the preferences window

Create a basic test:
Open the "simple_test.php" file we created earlier in a text editor
<?php
require_once dirname(__FILE__).'/simpletest/autorun.php';
class simple_test extends UnitTestCase{

function testFirst(){
	$this->assertEqual("a","b","This should generate an error");
}

function testSecond(){
	$this->assertEqual("a","a","This should pass");
}

}
?>

Save the file and then right click and select "Run As" -> "PHP Script"

If you look at a "Console" view [it should open automatically] the
output should be:

1) This should generate an error at
[C:\eclipse-3.5\workspace\Test\simple_test.php line 6]
	in testFirst
	in simple_test
FAILURES!!!
Test cases run: 1/1, Passes: 1, Failures: 1, Exceptions: 0

Or something similar

If you get the PHP debugger setup correctly (in Eclipse) in becomes
easy to right click and "Debug As" -> "PHP Script"

I hope this helps.

Regards,
Steven Balthazor

Greetings,

I'm trying to install simpletest_1.0.1.eclipse_0.2.5 into Eclipse.

My Eclipse installation details window says in summary:

Eclipse IDE for PHP Developers 1.2.0.20090618-0925
Eclipse Platform               3.5.0.I20090611-1540
Eclipse Platform               3.5.0.v20090611a
PHP Development Tools (PDT)    2.1.0.v20090611-0930
Simpletest plug-in             0.2.5

I have installed following the instructions in the readme.html.
That is, downloaded the ZIP file of the plugin and installed
it from local files.

The installation and configuration seems to go well, but
when I select new project, there's no "Simple -> Project"
option.

If I make a new PHP file in another project and Run As
Simpletest, there's no output at all. It just doesn't
seem to run and I can't find any error messages.

I have found the Result View pane... nothing shows up there.

Is the plugin just not compatible with this version of Eclipse?
Or have I missed something?

 ...Richard.

Hi...

Guilhem Martin wrote:
> Before:
> $test=new GroupTest($filename);
> $test->addTestFile($fullpath);
> 
> After:
> $test=new TestSuite($filename);
> $test->addFile($fullpath);

If you check out the file HELP_MY_TESTS_DONT_WORK_ANYMORE in teh 
project root, it lists this and any other updates you probably want 
to make.

> 
> Best Regards,
> 
> Guilhem.

yours, Marcus

Thanks for your answer.

> A newer version is about to be released. The current tarball (1.0.1) is
> PHP4.2 to PHP5.3 compatible. It's just about impossible to maintain both
> E_STRICT compliance and PHP4 compatibility at the same time.
>
> The current SVN version supports PHP5.0.3 to PHP6.

Ok, I've just retrieved it and it works just fine plus I'm getting rid of
the E_STRICT error, which is very fine.

For information, I had to change a little bit my code for this latest
simpletest version to run:

Before:
$test=new GroupTest($filename);
$test->addTestFile($fullpath);

After:
$test=new TestSuite($filename);
$test->addFile($fullpath);

Best Regards,

Guilhem.

Hi...

Guilhem Martin wrote:
> Is there a way I can easily disable theses messages? Or perhaps a newer
> version correct these?

A newer version is about to be released. The current tarball (1.0.1) is
PHP4.2 to PHP5.3 compatible. It's just about impossible to maintain both
E_STRICT compliance and PHP4 compatibility at the same time.

The current SVN version supports PHP5.0.3 to PHP6.

> 
> Thanks,
> 
> Guilhem.

yours, Marcus

Hi...

Guilhem Martin wrote:
> I've changed that and the tests are running again, thanks.

Cool.

> I went through HELP_MY_TESTS_DONT_WORK_ANYMORE and I think there is nothing
> about that in this file.

OK, I'll add an entry next chance I get. Thanks for the feedback.

> 
> Best Regards,
> 
> Guilhem.

yours, Marcus

Hello,

I'm using SimpleTest 1.0.1 with PHP5.3.0.

I get a lot of strict standards messages:

Strict Standards: Non-static method SimpleTest::getContext() should not be
called statically in C:\simpletest\errors.php on line 283
Strict Standards: Non-static method SimpleErrorQueue::getSeverityAsString()
should not be called statically in C:\simpletest\errors.php on line 280

Is there a way I can easily disable theses messages? Or perhaps a newer
version correct these?

Thanks,

Guilhem.

Hi Markus, hi all,

thanks for your answer.

>> The error refers to:
>>
>> class FlexibleComputing_SDK_Test extends GroupTest {
>>
>> function FlexibleComputing_SDK_Test() {
>> parent::GroupTest(''); // <-- line 7
>>
>> If I use PHP5.2.9-2/php.exe, then it's fine.
>>
>> Any idea about this?
>
> Try changing it to...
>
> class FlexibleComputing_SDK_Test extends TestSuite {
>
> function FlexibleComputing_SDK_Test() {
> parent::__construct(''); // <-- line 7
> ...
> PHP 5 style.

I've changed that and the tests are running again, thanks.

>> I've just upgraded from PHP 5.2.9-2 to 5.3.0 and I cannot run my
simpletest
>> suite no more.
>
> Which version are you running?

I'm using 1.0.1.

> Anything flagged in the file HELP_MY_TESTS_DONT_WORK_ANYMORE?

I went through HELP_MY_TESTS_DONT_WORK_ANYMORE and I think there is nothing
about that in this file.

Best Regards,

Guilhem.

Hi...

Perrick Penet wrote:
> PS : when you're done don't hesitate to contact me in order to get them 
> online.

I was about to honest :). He's still on the first draft and I still have
to send him a list of files I am still working on.

He's only just signed up and I asked him to talk to you.

> 
> Yours,
> 	Perrick

On a related note, there is now code in SimpleTest to use HTMLTidy
extension if installed. It is disabled by default right now, due to some
semantic fiddling we have to do to get textarea tags working correctly.

It would be great if you could try it out and see if any issues arise in
your tests. Runs web tests 2-4 times faster.

yours, Marcus

Hi...

Guilhem Martin wrote:
> I've just upgraded from PHP 5.2.9-2 to 5.3.0 and I cannot run my simpletest
> suite no more.

Which version are you running? Anything flagged in the file
HELP_MY_TESTS_DONT_WORK_ANYMORE?

> The error refers to:
> 
> class FlexibleComputing_SDK_Test extends GroupTest {
> 
>   function FlexibleComputing_SDK_Test() {
>     parent::GroupTest('');  // <-- line 7
> 
> If I use PHP5.2.9-2/php.exe, then it's fine.
> 
> Any idea about this?

Try changing it to...

class FlexibleComputing_SDK_Test extends TestSuite {

  function FlexibleComputing_SDK_Test() {
    parent::__construct('');  // <-- line 7
...

PHP 5 style.

> 
> Thanks,
> 
> Guilhem.

Let us know if this helps.

yours, Marcus

Hi all,

Reading the Simpletest-devel mailing list (for commits only), I've just 
realized that the documentation is currently being translated to 
italian. Welcome onboard Arialdo Martini !!

PS : when you're done don't hesitate to contact me in order to get them 
online.

Yours,
	Perrick

Hello all,

I've just upgraded from PHP 5.2.9-2 to 5.3.0 and I cannot run my simpletest
suite no more.

I got the following error:

PHP Fatal error:  Call to undefined method GroupTest::GroupTest() in
C:\path\to\_AllTests_Test.php on line 7

The error refers to:

class FlexibleComputing_SDK_Test extends GroupTest {

  function FlexibleComputing_SDK_Test() {
    parent::GroupTest('');  // <-- line 7

If I use PHP5.2.9-2/php.exe, then it's fine.

Any idea about this?

Thanks,

Guilhem.

I use Cruisecontrol to do my cakephp testing.
http://cruisecontrol.sourceforge.net/index.html

I setup an ant build script that uses an "exec" element to run the  
cakephp console to run the tests.
http://ant.apache.org/manual/CoreTasks/exec.html

The output is saved using the "output" attribute of the "exec"  
element.  Then the cruisecontrol project merges it into the log so it  
can be processed on the cruisecontrol dashboard.

I'm sure something similar can be accomplished with Phing.

Hope that helps,
Jason

On Sep 1, 2009, at 3:57 AM, Massimiliano Bertinetti wrote:

> I have read the book from Apress Pro PHP Pattern and I want to   
> recreate
> CI like in chapter 8, but the examples use PhpUnit. I read that phing
> support SimpleTest but I found no documentation, and I like to see an
> exampkle of Xinc / Phing / Cake / SimpleTest in action or a similiar
> system if possible. Any idea where to find something?
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support

Hi...

alexa driti wrote:
> I am using simpletest to do integration testing of my websites, and I need
> to tell the internal browser to wait for a certain amount of time (as the
> page is being redirected), and then do assertText.
> 
> Is there an easy way to do this ?

I need a little more information. Is this a meta refresh or a 3xx 
redirect? Or is this some kind of JavaScript delay.

SimpleTest will follow redirects automatically, and you can alter 
it's behaviour with setMaximumRedirects(). Setting to zero will stop 
the redirects altogether.

There is no concept of a delay here. SimpleTest will just wait for 
the page. Do you have a race condition?

> 
> Regards

yours, Marcus

You can do a sleep() in your test works well for me.

Pete
irc: cabbiepete

2009/9/1 alexa driti <ale...@gm...>

> Hi all,
>
> I am using simpletest to do integration testing of my websites, and I need
> to tell the internal browser to wait for a certain amount of time (as the
> page is being redirected), and then do assertText.
>
> Is there an easy way to do this ?
>
> Regards
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

I have read the book from Apress Pro PHP Pattern and I want to  recreate
CI like in chapter 8, but the examples use PhpUnit. I read that phing
support SimpleTest but I found no documentation, and I like to see an
exampkle of Xinc / Phing / Cake / SimpleTest in action or a similiar
system if possible. Any idea where to find something?

Hi all,

I am using simpletest to do integration testing of my websites, and I need
to tell the internal browser to wait for a certain amount of time (as the
page is being redirected), and then do assertText.

Is there an easy way to do this ?

Regards

Thank you for the answer, Marcus!
> Alexei Anisimov wrote:
>   
>> Is there any way to alter the way Scriptable Browser resolves domain 
>> names, like some local hosts file/table?
>>     
>
> This is below the level the browser normally operates. 

Yes, I understand.
> We just open 
> a socket to the host and that's it. You can use an ip though (static 
> I presume)...
>
> $this->get("http://1.2.3.4/stuff.html");
>   
That might work, but - in this case I will not get the desired virtual 
host documents, because HTTP request will not contain domain name, only 
IP, and therefore web server would return it's default page.
> Alternately, can you use another tool to get the URL first?
>   
I'm not sure - do you mean substitute getURL functions? But as I'm not 
much into PHP I doubt that I can do it in reasonable amount of time :)

Thanks again for you time!

Best regards,
--
Alexei Anisimov

Hi...

Alexei Anisimov wrote:
> Is there any way to alter the way Scriptable Browser resolves domain 
> names, like some local hosts file/table?

This is below the level the browser normally operates. We just open 
a socket to the host and that's it. You can use an ip though (static 
I presume)...

$this->get("http://1.2.3.4/stuff.html");

Alternately, can you use another tool to get the URL first?

> 
> Thanks!
> 

yours, Marcus

Hello everyone,

I'm trying to use Scriptable Browser 
<http://www.simpletest.org/en/browser_documentation.html> part of 
SimpleTest to automate a PHP application configuration - i.e. the 
application I work with has it's own configuration script which is 
accessible via HTTP. I successfully managed to use Scriptable Browser to 
connect and pass the configuration script, it works OK.

But as always it's not always that easy - in some cases the domain name 
where application resides is not resolvable, in this case I need to be 
able to force Scriptable Browser to connect to the IP I specify as if 
the domain name resolved to that IP. I know it can be done by modifying 
hosts file, but that is not an option for me, I don't have access there 
from the script.

Is there any way to alter the way Scriptable Browser resolves domain 
names, like some local hosts file/table?

Thanks!

-- 
Best regards,
--
Alexei Anisimov

Hi...

Noel Darlow wrote:
> Later I
> decided there's no clear distinction. Fixtures will usually want to
> decorate as well: probably a new assert method, maybe some accessors
> so you can make an assertion about a fixture file path or etc. 

That was my thought to.

> Noel

yours, Marcus

On Thu, 30 Jul 2009 10:16:15 +0200
troels knak-nielsen <tro...@gm...> wrote:

> I wonder what aspect of test cases makes them particularly suitable
> for multiple inheritance?

I guess it's just that a test case may be asked to do many different
things and we don't know in advance what they might be. There's a need
to assemble a custom interface (and fixtures) from different groups of
components, tailor-made for the task at hand.

Marcus wrote:
> 1) Fixtures would have a standardised format and become 
> a kind of plug-in. 
> 2) setUp() and tearDown() would be pulled directly from the
> composed classes leaving the setUp() and tearDown() free. 
> Also stops the error where you forget to chain these.
> 3) __call() is used to inline supplied assertions.

> What do you think?

Looks good. When I was playing around with this I started off thinking
about two separate things: decorators (which add new methods) and
fixtures (which are plugged into the setUp/tearDown cycle). Later I
decided there's no clear distinction. Fixtures will usually want to
decorate as well: probably a new assert method, maybe some accessors
so you can make an assertion about a fixture file path or etc. 

Noel

Hi...

troels knak-nielsen wrote:
> I wonder what aspect of test cases makes them particularly suitable
> for multiple inheritance?

I think it's the fixture reuse without spoiling the spec. We do lot of
this...

class MyTest extends WebBaseCaseToHoldFixtures {
    // ...messy setup() and tearDown() chaining.

    function testCanChangeAddress() {
        $this->accounting()->createAccount('fred');
        $this->authentication()->login('fred', 'secret');
        $this->navigation()->goToHome();
        $this->click('MyAccount');
        $this->setField('address', '1 Here street');
        $this->click('Update');
        $this->accounting()->assertAddress('fred', '1 here street');
    }

    ...
}

class WebBaseCaseToHoldFixtures extends WebTestCase { ... }

I'd rather do this...

class MyTest extends WebTestCase {
    function __construct() {
        $this->given(new AccountExists('fred'));
        $this->given(new LoggedInAs('fred', 'secret'));
        $this->given(new StartFromHomePage());
    }

    function testCanChangeAddress() {
        $this->click('MyAccount');
        $this->setField('address', '1 Here street');
        $this->click('Update');
        $this->assertAddress('fred', '1 here street');
    }

    ...
}

I haven't made the difference all that stark, but basically:

1) Fixtures would have a standardised format and become a kind of plug-in.
2) setUp() and tearDown() would be pulled directly from the composed
classes leaving the setUp() and tearDown() free. Also stops the error
where you forget to chain these.
3) __call() is used to inline supplied assertions.

What do you think?

> 
> --
> troels

yours, Marcus

I wonder what aspect of test cases makes them particularly suitable
for multiple inheritance?

--
troels

On Wed, Jul 29, 2009 at 11:41 PM, Noel Darlow<ma...@mc...> wrote:
> On Wed, 29 Jul 2009 22:14:11 +0100
> Noel Darlow <ma...@mc...> wrote:
>
>> Hi
>>
>> I've been using a traits-like system of "method injection" in test
>> cases for some time now. See docs at
>
> PS: I had to re-write UnitTestCase (and WebTestCase) in order to make
> them compatible with the decorator system. See here:
>
> http://aperiplus.svn.sourceforge.net/viewvc/aperiplus/lib/simpletest-extensions/unit-testing.php?view=markup
>
> This is more or less a copy-paste of SimpleTest code into another open
> source repository, with some minor changes. Is that OK? Sorry I
> should have asked first. I have to do this in order to extend
> SimpleTest with the test case decorator stuff.
>
> Noel
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

2003	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (4)	Sep (14)	Oct (22)	Nov (21)	Dec (7)
2004	Jan (4)	Feb (26)	Mar (62)	Apr (60)	May (73)	Jun (41)	Jul (64)	Aug (39)	Sep (19)	Oct (18)	Nov (55)	Dec (24)
2005	Jan (35)	Feb (122)	Mar (130)	Apr (62)	May (57)	Jun (103)	Jul (71)	Aug (142)	Sep (67)	Oct (27)	Nov (49)	Dec (56)
2006	Jan (42)	Feb (65)	Mar (30)	Apr (43)	May (13)	Jun (25)	Jul (5)	Aug (14)	Sep (18)	Oct (55)	Nov (126)	Dec (82)
2007	Jan (83)	Feb (83)	Mar (173)	Apr (30)	May (64)	Jun (156)	Jul (50)	Aug (29)	Sep (25)	Oct (26)	Nov (51)	Dec (9)
2008	Jan (36)	Feb (71)	Mar (93)	Apr (123)	May (34)	Jun (14)	Jul (21)	Aug (26)	Sep (49)	Oct (38)	Nov (19)	Dec (46)
2009	Jan (18)	Feb (16)	Mar (46)	Apr (4)	May (18)	Jun (9)	Jul (11)	Aug (4)	Sep (31)	Oct (19)	Nov (4)	Dec (11)
2010	Jan (15)	Feb (9)	Mar	Apr (20)	May (5)	Jun (8)	Jul (2)	Aug (9)	Sep (6)	Oct (21)	Nov (20)	Dec (11)
2011	Jan (11)	Feb (5)	Mar (6)	Apr (1)	May (12)	Jun (4)	Jul (1)	Aug (3)	Sep (4)	Oct (3)	Nov (3)	Dec (5)
2012	Jan (28)	Feb (7)	Mar (3)	Apr	May (5)	Jun (6)	Jul (5)	Aug (4)	Sep	Oct (4)	Nov (5)	Dec (4)
2013	Jan	Feb	Mar (3)	Apr	May	Jun	Jul (3)	Aug	Sep (1)	Oct	Nov	Dec
2014	Jan	Feb	Mar (1)	Apr	May	Jun (5)	Jul	Aug	Sep	Oct	Nov (7)	Dec
2015	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)
2016	Jan (2)	Feb	Mar	Apr	May (4)	Jun (1)	Jul	Aug (2)	Sep (3)	Oct	Nov (1)	Dec
2017	Jan (2)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2018	Jan	Feb	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec

simpletest-support Mailing List for SimpleTest (Page 14)

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