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

Re: [Simpletest-support] getDumper() error

[Ibbar <ib...@ep...>]

On 1/2/11 12:40 PM, Ibbar wrote:
> Hello,
>
> Sorry if this has been addressed before, but I couldn't find the answer
> any where.
>
>
> When running my test with version 1.0.1 using php 5.2.14 on OSX (10.5.8)
> I get the following error
>
>
> Fatal error: Call to a member function getDumper() on a non-object in
> /Users/ibbar/project/test/simpletest/test_case.php on line 312
>
>
> == TEST ==
> <?php
> require_once 'simpletest/autorun.php';
> require_once '../lib/BitwiseStatus.php';
>
> class BitwiseStatusTest extends UnitTestCase {
>       private $bitwiseStatusObj;
>
>       public function __construct() {
>           parent::__construct();
>           $this->bitwiseStatusObj = new BitwiseStatus();
>       }
>
>       public function testSetStatus() {
>           $this->bitwiseStatusObj->setStatus(4);
>           $this->assertEqual($this->bitwiseStatusObj->getStatus(), 4);
>       }
> }
>
> $test =&new BitwiseStatusTest();
> $test->testSetStatus();
> == TEST ==
>
>
> Any help will be appreciated.
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
Hello,

I finally figured out what the issue was. I shouldn't have included a 
constructor. Instead I should have used the setUp() method.

Best Regards,
William

[Simpletest-support] getDumper() error

[Ibbar <ib...@ep...>]

Hello,

Sorry if this has been addressed before, but I couldn't find the answer 
any where.


When running my test with version 1.0.1 using php 5.2.14 on OSX (10.5.8) 
I get the following error


Fatal error: Call to a member function getDumper() on a non-object in 
/Users/ibbar/project/test/simpletest/test_case.php on line 312


== TEST ==
<?php
require_once 'simpletest/autorun.php';
require_once '../lib/BitwiseStatus.php';

class BitwiseStatusTest extends UnitTestCase {
     private $bitwiseStatusObj;

     public function __construct() {
         parent::__construct();
         $this->bitwiseStatusObj = new BitwiseStatus();
     }

     public function testSetStatus() {
         $this->bitwiseStatusObj->setStatus(4);
         $this->assertEqual($this->bitwiseStatusObj->getStatus(), 4);
     }
}

$test = &new BitwiseStatusTest();
$test->testSetStatus();
== TEST ==


Any help will be appreciated.

Re: [Simpletest-support] customized assert methods?

[Christoph B. <ber...@ne...>]

Marcus, Noel, Tim - Thanks for the responses. I'm in good shape.

As I noted, the notion of doing the test once (e.g. for login behavior) and
then assuming that login works, during subsequent tests, goes a long way, so
I've rewritten a bunch of my tests.

Chris

On Wed, Dec 22, 2010 at 4:06 PM, Marcus Baker <ma...@la...> wrote:

> Hi...
>
> Christoph Berendes wrote:
> > function assertLoginSuccessful($userName, $passWord)
> > {
> >         $this->setField('username',$userName);
> >         $this->setField('password',$passWord);
> >         $this->click('Login');
> >         return $this->assertText('Login successful!');
> > }
>
> Try:
> return $this->assertText('Login successful! -> %s');
>
> This might be what you need. If not, tell us where this falls down. Also
> if you look at the SimpleTest versions, you'll see that it calls another
> class to do the line number sniffing. You could add a call to this as
> part of assertLoginSuccessful().
>
> yours, Marcus
>
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

Re: [Simpletest-support] customized assert methods?

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

Hi...

Christoph Berendes wrote:
> function assertLoginSuccessful($userName, $passWord)
> {
>         $this->setField('username',$userName);
>         $this->setField('password',$passWord);
>         $this->click('Login');
>         return $this->assertText('Login successful!');
> }

Try:
return $this->assertText('Login successful! -> %s');

This might be what you need. If not, tell us where this falls down. Also
if you look at the SimpleTest versions, you'll see that it calls another
class to do the line number sniffing. You could add a call to this as
part of assertLoginSuccessful().

yours, Marcus

Re: [Simpletest-support] customized assert methods?

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

Hi

> In particular, I'd like to write some customized assertions, for
> instance

> function assertLoginSuccessful($userName, $passWord)
> {
>         $this->setField('username',$userName);
>         $this->setField('password',$passWord);
>         $this->click('Login');
>         return $this->assertText('Login successful!');
> }

You only need to assert that you can login once and therefore
I don't think there is a need for an assertLoginSuccessful method. I'd
just make that a test:

   function testCanLogin($userName, $passWord)
   {
         $this->get(..login page..);
         $this->setField('username',$userName);
         $this->setField('password',$passWord);
         $this->click('Login');
         return $this->assertText('Login successful!');
   }

When that test has passed, I'd write a login method:

    function login($name, $pass) {
        $this->get(..login page..);
        $this->setField('username',$name);
        $this->setField('password',$pass);
        $this->click('Login');
    }

I'd expect you'll need to login a lot throughout the web test suite.
Anywhere you find you're repeating yourself is probably a sign to
refactor into a custom method. Also, a custom method like this will
make tests clearer and simpler because you don't have to read four
lines of code to get the sense of what's going on. Good tests - and
good code in generally - should try to tell a story. That's all about
hiding complexity behind some well-named methods and classes.

I'd probably end up with a loginAsAdmin() method as well, and any
others I need for different user roles. 

> What's the right way to create new assert methods that behave like the
> built-in ones, and also build on the built-in ones?

UNIT TESTS

It's OK to hack up a simple assert method as above but, for anything
non-trivial, the "proper" way to create custom expectations is like
this:

class Something extends SimpleExpectation {

    var $test_message = 'oops %s';

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

An assert method using the Something expectation would look like this:

    function assertSomething($value, $compare, $message = '%s') {
        return $this->assert(
                new Something($value), // expectation object
                $compare,              // the thing being checked
                $message);             // optional custom message
    }

Note that you can pass a custom message in the constructor. If this
contains an "%s" the framework will also embed the simpletest message.
This set up conforms to normal SimpleTest behaviour - that's important
if other people are using your code. Optional if not. I never seem to
use custom messages myself.

It's usual to pass an "A" value in the constructor and then the "B"
comparison value in the test() method. Sometimes you might have more
bits and pieces to pass in to the expectation object: do it in the
constructor. The test() method expects a single value, ie the second
parameter in an assert() call. 

Note that testMessage() can use $this->dumper to describe values and
differences - have a look through the SimpleTest code to see how it's
used.

I'd almost certainly want to test the expectation class itself. A test
framework has to be written to a very high standard. Debugging is
exponentially more difficult if you're not sure about the test code
behaviour.

Is it worth all that effort? Most definitely. I wouldn't think twice
about stopping to rattle off some testing code. Time spent now will be
saved in the future. Whenever I try to cut corners I always regret it
later.


WEB TESTS

I don't think I've ever written a custom expectation class for a web
test (but I do write lots of simple methods like your
assertLoginSuccessful). That makes me wonder if I'm maybe doing
something wrong... Probably we're well-covered already with everything
we need in the exisiting test framework. A web page is a well-known
problem which we can predict in advance but unit tests will throw up
all kinds of things which aren't covered by a basic test framework. 

Ask away if you need more help.


Noel

Re: [Simpletest-support] customized assert methods?

[Christoph B. <ber...@ne...>]

Thanks for the quick answer, Tim. As I've been reading, I also see that some
of my problem has been my habit of sticking assertions in setup code. E.g.

  function setUp ()
{
    doSomething();
    $this->assertSomethingDone();
}

I'm also revising to run the above once as a test, and from then on assume
that doSomething does what it's supposed to do.

Chris

On Wed, Dec 22, 2010 at 9:38 AM, T.J.Hunt <t.j...@op...> wrote:

> The right way to do extensions like this is to create a new Expectation
> class. For example like
> https://github.com/moodle/moodle/blob/master/lib/simpletestlib.php#L105.
>
> You can then use that as
>
> $this->assert(new MyExpectation($parameters), $value);
>
> That is the best way for tests you will want to reuse a lot. In other
> situations, a simple helper method is fine, but as you say, the default
> display is unhelpful. You can improve the display with a custom reporter.
> For example:
> https://github.com/moodle/moodle/blob/master/admin/report/unittest/ex_reporter.php#L160.
> That does a good job of showing just the interesting bits of the
> stack-trace, but not all the layers of the simpletest library.
>
> All that code is GPL, so you can copy it if you are working to a suitable
> open source license.
>
> Tim.
>
> ________________________________________
> From: Christoph Berendes [ber...@ne...]
> Sent: 22 December 2010 14:05
> To: Help, advice,       bugs and workarounds
> Subject: [Simpletest-support] customized assert methods?
>
> Hi - I've been using Simpletest successfully and happily for a few years --
> thanks -- and now want to wade in a little deeper.
>
> In particular, I'd like to write some customized assertions, for instance
>
> function assertLoginSuccessful($userName, $passWord)
> {
>        $this->setField('username',$userName);
>        $this->setField('password',$passWord);
>        $this->click('Login');
>        return $this->assertText('Login successful!');
> }
>
> This works fine, but I'd like one more thing - if the assertText fails, I'd
> like to see the line where assertLoginSuccessful was called.
>
> It looks like I could hack this together myself by calling the assert
> method
> directly, but then it seems I have to recreate assertText.
>
> What's the right way to create new assert methods that behave like the
> built-in ones, and also build on the built-in ones?
>
> Thanks.
> Chris Berendes
>
> ------------------------------------------------------------------------------
> Forrester recently released a report on the Return on Investment (ROI) of
> Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even
> within 7 months.  Over 3 million businesses have gone Google with Google
> Apps:
> an online email calendar, and document program that's accessible from your
> browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>
> --
> The Open University is incorporated by Royal Charter (RC 000391), an exempt
> charity in England & Wales and a charity registered in Scotland (SC 038302).
>
>
>
> ------------------------------------------------------------------------------
> Forrester recently released a report on the Return on Investment (ROI) of
> Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even
> within 7 months.  Over 3 million businesses have gone Google with Google
> Apps:
> an online email calendar, and document program that's accessible from your
> browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

Re: [Simpletest-support] customized assert methods?

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

The right way to do extensions like this is to create a new Expectation class. For example like https://github.com/moodle/moodle/blob/master/lib/simpletestlib.php#L105.

You can then use that as

$this->assert(new MyExpectation($parameters), $value);

That is the best way for tests you will want to reuse a lot. In other situations, a simple helper method is fine, but as you say, the default display is unhelpful. You can improve the display with a custom reporter. For example: https://github.com/moodle/moodle/blob/master/admin/report/unittest/ex_reporter.php#L160. That does a good job of showing just the interesting bits of the stack-trace, but not all the layers of the simpletest library.

All that code is GPL, so you can copy it if you are working to a suitable open source license.

Tim.

________________________________________
From: Christoph Berendes [ber...@ne...]
Sent: 22 December 2010 14:05
To: Help, advice,       bugs and workarounds
Subject: [Simpletest-support] customized assert methods?

Hi - I've been using Simpletest successfully and happily for a few years --
thanks -- and now want to wade in a little deeper.

In particular, I'd like to write some customized assertions, for instance

function assertLoginSuccessful($userName, $passWord)
{
        $this->setField('username',$userName);
        $this->setField('password',$passWord);
        $this->click('Login');
        return $this->assertText('Login successful!');
}

This works fine, but I'd like one more thing - if the assertText fails, I'd
like to see the line where assertLoginSuccessful was called.

It looks like I could hack this together myself by calling the assert method
directly, but then it seems I have to recreate assertText.

What's the right way to create new assert methods that behave like the
built-in ones, and also build on the built-in ones?

Thanks.
Chris Berendes
------------------------------------------------------------------------------
Forrester recently released a report on the Return on Investment (ROI) of
Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even
within 7 months.  Over 3 million businesses have gone Google with Google Apps:
an online email calendar, and document program that's accessible from your
browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew
_______________________________________________
Simpletest-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simpletest-support

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

[Simpletest-support] customized assert methods?

[Christoph B. <ber...@ne...>]

Hi - I've been using Simpletest successfully and happily for a few years --
thanks -- and now want to wade in a little deeper.

In particular, I'd like to write some customized assertions, for instance

function assertLoginSuccessful($userName, $passWord)
{
        $this->setField('username',$userName);
        $this->setField('password',$passWord);
        $this->click('Login');
        return $this->assertText('Login successful!');
}

This works fine, but I'd like one more thing - if the assertText fails, I'd
like to see the line where assertLoginSuccessful was called.

It looks like I could hack this together myself by calling the assert method
directly, but then it seems I have to recreate assertText.

What's the right way to create new assert methods that behave like the
built-in ones, and also build on the built-in ones?

Thanks.
Chris Berendes

Re: [Simpletest-support] Problem with Mocks

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

From: Piotr Skowronek <pio...@gm...>

To: sim...@li...
Sent: Sat, December 18, 2010 4:33:56 PM
Subject: [Simpletest-support] Problem with Mocks

> Help, please.

Hi Piotr,

You are testing the wrong thing.  The mock does nothing buy verify methods were 
called.  If you execute a method of the mock, that is it, it counts the method 
as called.  I think what you may want to do is something like create a mock 
Controller object, inject it into a real Dispatch object, and then verify it's 
"execute" method or whatever, is called when you $dispatcher->dispatch();  The 
dispatcher would grab "his" controller (your Mock Controller) and do whatever 
with it in the runController() method.  This is what you should be testing, the 
interaction between these objects.

Hope that helps.

Regards,
Jason



      

[Simpletest-support] Problem with Mocks

[Piotr S. <pio...@gm...>]

Hello

I  write  Framework  and  now I am writing test for my dispatcher. And
there's following problem:

class TestDispatcher extends UnitTestCase
{
    public function setUp()
    {
        require_once "../core/fDispatcher.php";
        Mock::generate( "fDispatcher" );
    }
    
    public function testDispatch()
    {
        $dispatcher = new MockfDispatcher;
        $dispatcher->expectOnce( "runController" );
        $dispatcher->dispatch();
    }
}

Original  method  dispatch()  calls  runController(). It doesn't work.
Even it doesn't count it as an assertion so test case is completed. It
works only when I replace
$dispatcher->dispatch() to $dispatcher->runController().

Help, please.


-- 
 Piotr Skowronek

[Simpletest-support] Simpletest Login issue

[Jose De A. <dea...@gm...>]

Hi,

I'm having trouble to test login process on my test server although it 
works fine locally.

here is the code I use:

<?php

require_once 'simpletest/browser.php';

$browser = new SimpleBrowser();
$browser->useCookies();

$browser->get('http://test.example.com/login.php');

$browser->setField('login', 'login');
$browser->setField('password', 'password');
$browser->submitFormById('login');

$page = $browser->getContentAsText();

echo $page;
?>

Any thoughts why it doesn't work.

Thank you for your input

José

Re: [Simpletest-support] Running just a single test method?

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

From: Roy Smith <ro...@s7...>

To: sim...@li...
Sent: Thu, December 16, 2010 1:15:55 PM
Subject: [Simpletest-support] Running just a single test method?

>Is there a way to run just a single test method?

>When I'm debugging, it's often convenient to just run the one method
>which demonstrates the bug I'm working on.

What I typically do is run tests either as a single file, or as a test suite.  
If I am working on a particular class, I execute the test file for it.  When it 
is satisfactory, I run a test covering all files to ensure I have not 
inadvertently broken something else.

You may want to read up on group tests for how to accomplish this: 
http://simpletest.org/api/SimpleTest/tutorial_GroupTests.pkg.html

The other thought to keep in the back of your mind is if your test suite is 
slow, you may be doing more integration testing than unit testing.  Try to keep 
everything fast so you don't worry about executing the tests as often as you 
can.

Hope that helps.

Regards,
Jason


      

[Simpletest-support] Running just a single test method?

[Roy S. <ro...@s7...>]

Is there a way to run just a single test method?

When I'm debugging, it's often convenient to just run the one method
which demonstrates the bug I'm working on.

[Simpletest-support] tutorial about Selenium/code coverage?

[Jim T. <jim...@ho...>]

I notice that there are extensions listed on the API page for both Selenium and code coverage, but I don't see any information as to how to enable either, or how to implement them together.  (I have been frustrated with phpunit, since it doesn't appear to be possible to generate code coverage reports from selenium tests...)

Is there any information / documentation / scattered notes available for implementing these extensions?  (When I downloaded the latest simpletest tarball, it didn't include them?)

Thanks in advance-

Jim Tibbetts
QA PHP Developer
Hooah, LLC
T.   407-362-7715
F.   407-362-1538
M.  505-490-0357
jim...@ho...
www.hooah.cc
:::::::::::::::::::::::::::::::
Interactive
Communications
:::::::::::::::::::::::::::::::
807-P South Orlando Ave.
Winter Park, FL 32789
:::::::::::::::::::::::::::::::

Re: [Simpletest-support] no runnable test cases

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

From: R. Michael Litchfield <rm...@uo...>

To: "Help, advice, bugs and workarounds" 
<sim...@li...>
Sent: Wed, November 3, 2010 2:07:58 PM
Subject: Re: [Simpletest-support] no runnable test cases

>I have some experience writing cli phpunit tests but I'm brand new to 
simpletest. I was trying to use simpletest as a quick, simple way to get 
a web interface for my phpunit tests by just dropping in the 
"require(path/autorun.php);"

>But that doesn't seem like a viable course, the tests don't match. It 
seems that simpletest doesn't complement phpunit but instead competes 
with it as an alternate testing structure.

Which reminds me, I owe the world a blog post on an adapter I wrote to get from 
simpletest to phpunit a while back that I never made public :(

Regards,
Jason



      

Re: [Simpletest-support] no runnable test cases

[R. M. L. <rm...@uo...>]

 On Wed, 3 Nov 2010 10:38:54 -0700 (PDT), Jason Sweat wrote:
>>When it failed on the webbrowser I ran it in cli "phpunit
>>gobblegobble/test/unit/ddsPagewebTest.php" and got this result:
>>1) Bad TestSuite [phpunit] with error [No runnable test cases in
>>[phpunit]]
>
> did you really mean to run with phpunit, or should you just run with
> the php cli
> binary?

 Hmm, I think that starts to get to the heart of my confusion.

 I have some experience writing cli phpunit tests but I'm brand new to 
 simpletest. I was trying to use simpletest as a quick, simple way to get 
 a web interface for my phpunit tests by just dropping in the 
 "require(path/autorun.php);"

 But that doesn't seem like a viable course, the tests don't match. It 
 seems that simpletest doesn't complement phpunit but instead competes 
 with it as an alternate testing structure.

> Jason

 -Michael

Re: [Simpletest-support] no runnable test cases

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

From: R. Michael Litchfield <rm...@uo...>

To: "Help, advice, bugs and workarounds" 
<sim...@li...>
Sent: Wed, November 3, 2010 12:06:33 PM
Subject: [Simpletest-support] no runnable test cases

>When it failed on the webbrowser I ran it in cli "phpunit 
gobblegobble/test/unit/ddsPagewebTest.php" and got this result:
[assorted test outoput showing them running fine]
Time: 1 second, Memory: 7.25Mb

OK (18 tests, 45 assertions)
phpunit
1) Bad TestSuite [phpunit] with error [No runnable test cases in 
[phpunit]]
    in
FAILURES!!!
Test cases run: 0/0, Passes: 0, Failures: 1, Exceptions: 0

>so it seems phpunit is seeing seeing and running the tests but 
simpletest is not seeing them.

did you really mean to run with phpunit, or should you just run with the php cli 
binary?

Regards,
Jason



      

[Simpletest-support] no runnable test cases

[R. M. L. <rm...@uo...>]

 I fixed the missing file errors in all_tests:
 /test/support/recorder_sample.php
 /test/arguments_test.php
 /test/recorder_test.php

 All_test now runs successfully (147/154 test cases complete: 2669 
 passes, 0 fails and 0 exceptions) but I still get the errors below 
 (Fail: -> Bad TestSuite [ddspagewebtest.php] with error [No runnable 
 test cases in [ddspagewebtest.php]]) when I try to run my test.

 When it failed on the webbrowser I ran it in cli "phpunit 
 gobblegobble/test/unit/ddsPagewebTest.php" and got this result:
 [assorted test outoput showing them running fine]
 Time: 1 second, Memory: 7.25Mb

 OK (18 tests, 45 assertions)
 phpunit
 1) Bad TestSuite [phpunit] with error [No runnable test cases in 
 [phpunit]]
 	in
 FAILURES!!!
 Test cases run: 0/0, Passes: 0, Failures: 1, Exceptions: 0

 so it seems phpunit is seeing seeing and running the tests but 
 simpletest is not seeing them.

 The only obvious thing I'm doing that's at all odd is that my test 
 class is an extension of a custom test class:

 require_once(dirname(__FILE__).'/../lib/DDSTest.php');
 require_once(dirname(__FILE__).'/simpletest/autorun.php');
 require_once('DDSPage/DDSPage.class.php');
 class ddsPagewebTest extends DDSTest
 {severaltests}


 DDSTest is a pretty kosher extension of PHPUnit_Framework_TestCase that 
 just adds ZendDB connectors.

 Any ideas?
 environment:
 OS X 10.5
 Firefox
 apache
 PHP 5.3.1

 -Michael
 On Tue, 02 Nov 2010 11:18:46 -0700, R. Michael Litchfield wrote:
> Dug up a copy of arguments.php from a previous verision and dropped 
> it
>  into the simpletest directory
>
>  I then got 4 undefined index errors from default_reporter.php
>
>  Notice: Undefined index: c in
>  gobblegobble/test/unit/simpletest/default_reporter.php on line 154
>  Notice: Undefined index: t in
>  gobblegobble/test/unit/simpletest/default_reporter.php on line 155
>  Notice: Undefined index: skips in
>  gobblegobble/test/unit/simpletest/default_reporter.php on line 156
>  Notice: Undefined index: show-skips in
>  gobblegobble/test/unit/simpletest/default_reporter.php on line 156
>
>
>  then it finally started processing my file but it popped an error:
>  ddspagewebtest.php
>  Fail: -> Bad TestSuite [ddspagewebtest.php] with error [No runnable
>  test cases in [ddspagewebtest.php]]
>

Re: [Simpletest-support] 1.1alpha missing arguments.php

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

Hi...

R. Michael Litchfield wrote:
>  Installed 1.1alpha and tried to load a file with firefox on os X 10.5.8 
>  that has:
>  require_once(dirname(__FILE__).'/simpletest/autorun.php');
>  in the header
> 
>  Warning: require_once(gobblegobble/test/unit/simpletest/arguments.php) 
>  [function.require-once]: failed to open stream: No such file or 
>  directory in gobblegobble/test/unit/simpletest/reporter.php on line 13

I did an updated tarball. Bit of a rush release. I'll be more careful
next time.

> 
>  -Michael

yours, Marcus

Re: [Simpletest-support] Eclipse Helios

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

On Tue, Nov 2, 2010 at 9:22 AM, Benjamin Schuetz <
ben...@ti...> wrote:

> Hi all, got the following strange issue:
>
> Installing Simpletest Eclipse plugin on Eclipse Helios does not seem to
> work.
>
>
> 1.) I download/install simpletest via Install New Software... function as
> described
>
> 2.) Restarted Eclipse
>
> 3.) No plugin available (under preferences)
>
>
> Any hints on what I do wrong ?
>

Hello,

I just downloaded the latest version of Eclipse (Eclipse Class 3.6.1 from
here: http://www.eclipse.org/downloads/ - windows 32bit).  The instructions
on the website (http://www.simpletest.org/en/extension_eclipse.html) are a
little bit dated (they are correct for earlier versions of Eclipse, but they
just keep changing the way the installation process works); however, if you
follow the concepts then the Simpletest plugin will install.

I was able to install it by downloading and unzipping the zip file and
pointing "Software Updates" at the folder in the file system.  I also was
able to install by copying the appropriate files (one jar in the plugins
folder and one jar in the features folder) into the same folders in the
Eclipse installation.

In both cases, I was able to restart Eclipse and had a Simpletest category
inside Preferences.

Something obviously went wrong somewhere for you.  I would recommend looking
in the "Error Log" or the "Problems" views (Window->Show View).  Another
place to see possible errors is under Help->About Eclipse SDK then click the
"Installation Details" button.  The configuration tab then has a "View Error
Log" button.

Regards,
Steven Balthazor

[Simpletest-support] 1.1alpha undefined index errors and then no runnable tests

[R. M. L. <rm...@uo...>]

 Dug up a copy of arguments.php from a previous verision and dropped it 
 into the simpletest directory

 I then got 4 undefined index errors from default_reporter.php

 Notice: Undefined index: c in 
 gobblegobble/test/unit/simpletest/default_reporter.php on line 154
 Notice: Undefined index: t in 
 gobblegobble/test/unit/simpletest/default_reporter.php on line 155
 Notice: Undefined index: skips in 
 gobblegobble/test/unit/simpletest/default_reporter.php on line 156
 Notice: Undefined index: show-skips in 
 gobblegobble/test/unit/simpletest/default_reporter.php on line 156


 then it finally started processing my file but it popped an error:
 ddspagewebtest.php
 Fail: -> Bad TestSuite [ddspagewebtest.php] with error [No runnable 
 test cases in [ddspagewebtest.php]]

 since my test runs fine without autorun I ran all tests and got this 
 set of errors

 Warning: 
 include_once(/gobblegobble/test/unit/simpletest/test/arguments_test.php) 
 [function.include-once]: failed to open stream: No such file or 
 directory in /gobblegobble/test/unit/simpletest/test_case.php on line 
 381

 Warning: include_once() [function.include]: Failed opening 
 '/gobblegobble/test/unit/simpletest/test/arguments_test.php' for 
 inclusion (include_path='redacted') in 
 /gobblegobble/test/unit/simpletest/test_case.php on line 381

 Warning: 
 file_get_contents(/gobblegobble/test/unit/simpletest/test/arguments_test.php) 
 [function.file-get-contents]: failed to open stream: No such file or 
 directory in /gobblegobble/test/unit/simpletest/test_case.php on line 
 417

 Warning: 
 include_once(/gobblegobble/test/unit/simpletest/test/recorder_test.php) 
 [function.include-once]: failed to open stream: No such file or 
 directory in /gobblegobble/test/unit/simpletest/test_case.php on line 
 381

 Warning: include_once() [function.include]: Failed opening 
 '/gobblegobble/test/unit/simpletest/test/recorder_test.php' for 
 inclusion (include_path='redacted') in 
 /gobblegobble/test/unit/simpletest/test_case.php on line 381

 Warning: 
 file_get_contents(/gobblegobble/test/unit/simpletest/test/recorder_test.php) 
 [function.file-get-contents]: failed to open stream: No such file or 
 directory in /gobblegobble/test/unit/simpletest/test_case.php on line 
 417

 all_tests.php
 Skipped: All tests for SimpleTest 1.1alpha -> 
 gobblegobble/test/unit/simpletest/test/unit_tests.php -> Unit tests -> 
 gobblegobble/test/unit/simpletest/test/errors_test.php -> E_USER_ERROR 
 not tested for PHP 5.2 and above at 
 [gobblegobble/test/unit/simpletest/test/errors_test.php line 172]
 Fail: All tests for SimpleTest 1.1alpha -> 
 gobblegobble/test/unit/simpletest/test/unit_tests.php -> Unit tests -> 
 gobblegobble/test/unit/simpletest/test/arguments_test.php -> Bad 
 TestSuite [gobblegobble/test/unit/simpletest/test/arguments_test.php] 
 with error [No runnable test cases in 
 [gobblegobble/test/unit/simpletest/test/arguments_test.php]]
 Fail: All tests for SimpleTest 1.1alpha -> 
 gobblegobble/test/unit/simpletest/test/unit_tests.php -> Unit tests -> 
 gobblegobble/test/unit/simpletest/test/recorder_test.php -> Bad 
 TestSuite [gobblegobble/test/unit/simpletest/test/recorder_test.php] 
 with error [No runnable test cases in 
 [gobblegobble/test/unit/simpletest/test/recorder_test.php]]
 Skipped: All tests for SimpleTest 1.1alpha -> 
 gobblegobble/test/unit/simpletest/test/unit_tests.php -> Unit tests -> 
 gobblegobble/test/unit/simpletest/test/parsing_test.php -> Install 
 'tidy' php extension to enable html tidy based parser at 
 [gobblegobble/test/unit/simpletest/test/parsing_test.php line 631]
 144/151 test cases complete: 2647 passes, 2 fails and 0 exceptions.


 On Tue, 02 Nov 2010 10:12:32 -0700, R. Michael Litchfield wrote:
> Installed 1.1alpha and tried to load a file with firefox on os X
> 10.5.8 that has:
> require_once(dirname(__FILE__).'/simpletest/autorun.php');
> in the header
>
> Warning:
> require_once(gobblegobble/test/unit/simpletest/arguments.php)
> [function.require-once]: failed to open stream: No such file or
> directory in gobblegobble/test/unit/simpletest/reporter.php on line 
> 13
>
> -Michael

[Simpletest-support] 1.1alpha missing arguments.php

[R. M. L. <rm...@uo...>]

 Installed 1.1alpha and tried to load a file with firefox on os X 10.5.8 
 that has:
 require_once(dirname(__FILE__).'/simpletest/autorun.php');
 in the header

 Warning: require_once(gobblegobble/test/unit/simpletest/arguments.php) 
 [function.require-once]: failed to open stream: No such file or 
 directory in gobblegobble/test/unit/simpletest/reporter.php on line 13

 -Michael

[Simpletest-support] Eclipse Helios

[Benjamin S. <ben...@ti...>]

Hi all,

 

got the following strange issue:
 

Installing Simpletest Eclipse plugin on Eclipse Helios does not seem to work.

 

1.) I download/install simpletest via Install New Software... function as described

2.) Restarted Eclipse

3.) No plugin available (under preferences)

 

Any hints on what I do wrong ?

 

Best,

benny!

 

PS:

I also tried to download eclipse plugin manually and copied plugins/feature folder - No success either.

Re: [Simpletest-support] assertions don't throw?

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

Hi

> Noel Darlow wrote:
> > (1) A fail will halt execution of the current test method but other
> > test methods will proceed as normal. That sounds OK.
> 
> That's the aim. We actually do this already in the case that the code
> under test throws an exception. In the 1.0.1 version this was only
> enabled if PHP5 was detected.

OK thanks :)


Noel

Re: [Simpletest-support] bugs are for logged-in only SF users

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

Hi...

Perrick Penet-Avez wrote:
> For the first time in 5 years, we're facing a spam wave on the bugs 
> tracker : I just unchecked the "Allow non-logged-in postings" option. I 
> might reconsider enabling it in a few days.

Thanks. I had a friend complain about this.

> 
> Yours,
> 	Perrick

yours, Marcus