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

Re: [Simpletest-support] 1.1alpha2 docs and usage

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

Hi Mark,

I'm looking into this issue currently.

I was under the assumption that the extensions were packaged
separately from the main build, and the location of the code file in
the extensions directory seems to reflect that. There is a case to be
made for including this in the main build if it is going to be widely
used, but we'd need to hear from more people to confirm this.

Regarding your other question, the most straightforward way would be
to use the SimpleTest::prefer(new CustomReporter()) -- call after you
require the autoload file in your test bootstrap.

If you want to read up on the history of how this part of the
SimpleTest API changed over time, there's an article on my blog
covering all the various ways of customizing reporters on test runs:

http://maetl.net/harnessing-simpletest

Best regards,
Mark

--
Mark Rickerby
http://maetl.net



2011/5/5 Mark Donohoe <mar...@hp...>:
> Hello Simpletesters,
>
> I have been using the 1.0.1 version for years now.  Looking forward to
> the newest version.  It was great to see the extensions like
> JunitXMLReporter.
>
> Things are a bit confusing... the api docs say it's in extensions, but
> the log in svn says it's been moved to the core.
>
> The biggest issue for me is how do I use it?  If it's in the core, is
> there a switch to the reporter that can be supplied to use that format?
>
> Same for SimpleSeleniumRemoteControl, as our site is using more ajax and
> javascript, so I have a need to use seleniumRC.  So where is it?  It's
> not in the extensions directory (I just down loaded alpha2).  This
> extension I think I can figure out from the class docs how to call and
> use it along wtih SeleniumTestCase.
>
> Are there any users of any of the above that could provide some examples
> or pointers on how to use these.  Thanks.
>
> ---
> Mark Donohoe
> OSPO, HP
> FOSSology.org
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

Re: [Simpletest-support] File missing: arguments.php

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

Thanks for your feedback; I downloaded the package from SF.net and got
the same problem – seems that the .tgz file doesn't have the
arguments.php included in the source.

I built another package which does have the correct file included.
Until we get the main distribution fixed on sourceforge, you can
download the 1.1 package from here –
http://pearfarm.org/simpletest/simpletest

(you will have to rename the directory when you copy the files – or
else, you can copy arguments.php to your existing installation, as it
looks like that is the only missing file – let me know if you have
further problems getting it to run)

Best Regards,
Mark

[Simpletest-support] File missing: arguments.php

[Attila <att...@gm...>]

Hello all,

I am new to SimpleTest and I just installed the package and ran the sample.
However I get the following error:

( ! ) Warning:
require_once(D:\www\svnrepos\en\branches\at\dev_server1\application\libraries\simpletest/arguments.php)
[function.require-once<http://localhost:8888/application/tests/function.require-once>]:
failed to open stream: No such file or directory in
D:\www\svnrepos\en\branches\at\dev_server1\application\libraries\simpletest\reporter.php
on line *13

It seems like:

Contents of reporter.php:
<?php
/**
 *  base include file for SimpleTest
 *  @package    SimpleTest
 *  @subpackage UnitTester
 *  @version    $Id: reporter.php 1995 2010-04-06 12:57:40Z lastcraft $
 */

/**#@+
 *  include other SimpleTest class files
 */
require_once(dirname(__FILE__) . '/scorer.php');
require_once(dirname(__FILE__) . '/arguments.php');
(Line 13 highlighted)

The file simpletest/arguments.php does not exist in the distribution.

Can someone please advise on how to proceed?

Thank you,
*

[Simpletest-support] 1.1alpha2 docs and usage

[Mark D. <mar...@hp...>]

Hello Simpletesters,

I have been using the 1.0.1 version for years now.  Looking forward to 
the newest version.  It was great to see the extensions like 
JunitXMLReporter.

Things are a bit confusing... the api docs say it's in extensions, but 
the log in svn says it's been moved to the core.

The biggest issue for me is how do I use it?  If it's in the core, is 
there a switch to the reporter that can be supplied to use that format?

Same for SimpleSeleniumRemoteControl, as our site is using more ajax and 
javascript, so I have a need to use seleniumRC.  So where is it?  It's 
not in the extensions directory (I just down loaded alpha2).  This 
extension I think I can figure out from the class docs how to call and 
use it along wtih SeleniumTestCase.

Are there any users of any of the above that could provide some examples 
or pointers on how to use these.  Thanks.

---
Mark Donohoe
OSPO, HP
FOSSology.org

Re: [Simpletest-support] SimpleTest and Sonar

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

Hi...

Perrick Penet-Avez wrote:
> Sonar, the "open platform to manage code quality", is again quite high 
> in my personal radar. Has anyone had any success with some kind of 
> integration with SimpleTest ?

Do you know what would be needed to integrate ST with this?

> 
> The PHP tools (http://docs.codehaus.org/display/SONAR/PHP+Plugin) don't 
> mention SimpleTest. Anyone working on it ???

There doesn't seem to be an easy way to contact the author of the
plug-in from that site. He has a blog here:

http://akrambenaissi.wordpress.com/

> 
> Yours,
> 	Perrick

yours, Marcus

[Simpletest-support] SimpleTest and Sonar

[Perrick Penet-A. <pe...@no...>]

Hi all,

Sonar, the "open platform to manage code quality", is again quite high 
in my personal radar. Has anyone had any success with some kind of 
integration with SimpleTest ?

The PHP tools (http://docs.codehaus.org/display/SONAR/PHP+Plugin) don't 
mention SimpleTest. Anyone working on it ???

Yours,
	Perrick

Re: [Simpletest-support] Invalid thread access error

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

On Tue, Mar 22, 2011 at 12:09 PM, Duct Tape Programmer <
com...@ve...> wrote:

> I new to using SimpleTest with the PHP5,
>
> ...

>
> The IDE is Eclipse Helios, when I attempt to run a test, in Debug Mode,
> I get the following error message box:
>
> An internal error occurred during: "Launching test simpletest".
> Invalid thread access
>
> Error Log looks like:
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4083)
> at org.eclipse.swt.SWT.error(SWT.java:3998)
> at org.eclipse.swt.SWT.error(SWT.java:3969)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:466)
> at org.eclipse.swt.widgets.Shell.<init>(Shell.java:262)
> at org.eclipse.swt.widgets.Shell.<init>(Shell.java:358)
> at org.eclipse.jface.window.Window.createShell(Window.java:487)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
> at org.eclipse.jface.window.Window.open(Window.java:790)
> at org.eclipse.jface.dialogs.ErrorDialog.open(ErrorDialog.java:356)
> at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:420)
> at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:385)
> at
>
> net.sf.simpletest.eclipse.launcher.TestLaunchConfigurationDelegate.launch(TestLaunchConfigurationDelegate.java:64)
> at
>
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
> at
>
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
> at
>
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:923)
> at
> org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1126)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>

Hello,

The simpletest eclipse plugin has not been maintained for several releases
of the Eclipse environment.  The plugin is actually trying to open an error
dialog box to give this error: "Please provide a path to the php executable
in the preferences.".  However, the method of opening an error dialog box
has changed so much since the plugin was written that it cannot do that.

I got this by looking at the source (line 64):
http://simpletest.svn.sourceforge.net/viewvc/simpletest/eclipse/trunk/src/net/sf/simpletest/eclipse/launcher/TestLaunchConfigurationDelegate.java?revision=2007&view=markup

I would recommend that you verify that all step under Installation (from
here: http://simpletest.sourceforge.net/en/extension_eclipse.html );
specifically step 18 are complete.

Good luck getting debugging to work correctly via the plugin; it is very
tricky.  Get it running as a "Run" script before trying to make debugging
work.

For debugging I recommend reworking your test scripts so they can run using
right-click - Debug As PHP Script (or Run As PHP Script).  The debugging
works much more reliably this way.  You lose the red/green bar and the
hierarchical display of errors but is much more stable and reliable.

Regards,
Steven Balthazor

[Simpletest-support] Invalid thread access error

[Duct T. P. <com...@ve...>]

I new to using SimpleTest with the PHP5,

The test looks like:
<?php
require_once('tools/autorun.php');
class test1 extends UnitTestCase {
     function test_pass ( ) {
         $x = 1;
         $y = 2;
         $total = $x + $y;
         $this->assertEqual ( 3, $total, "This should pass" );
     }
}
?>

The IDE is Eclipse Helios, when I attempt to run a test, in Debug Mode, 
I get the following error message box:

An internal error occurred during: "Launching test simpletest".
Invalid thread access

Error Log looks like:
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:4083)
at org.eclipse.swt.SWT.error(SWT.java:3998)
at org.eclipse.swt.SWT.error(SWT.java:3969)
at org.eclipse.swt.widgets.Widget.error(Widget.java:466)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:262)
at org.eclipse.swt.widgets.Shell.<init>(Shell.java:358)
at org.eclipse.jface.window.Window.createShell(Window.java:487)
at org.eclipse.jface.window.Window.create(Window.java:430)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.eclipse.jface.dialogs.ErrorDialog.open(ErrorDialog.java:356)
at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:420)
at org.eclipse.jface.dialogs.ErrorDialog.openError(ErrorDialog.java:385)
at 
net.sf.simpletest.eclipse.launcher.TestLaunchConfigurationDelegate.launch(TestLaunchConfigurationDelegate.java:64)
at 
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at 
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
at 
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:923)
at 
org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1126)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


I read that by including the php.ini file, it helps, in Helios, it does 
not. The only field that has content is the "Test File Suffix" field.

Is there a web page that has the solution for this?

Re: [Simpletest-support] 1.0.1 posts disabled form elements - where to patch?

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

Hi...

Christoph Berendes wrote:
> I'm happy to patch Simpletest for the moment to just omit disabled elements
> from the request, but I'd be grateful for guidance as to where, roughly to
> insert it , since I'm having some trouble unraveling the sequence of calls
> that lead to a post or get.

Hm. Not sure yet. I'll take a look on the train today. It might be quite
fiddly as this is a bit of a new concept to SimpleTest.

I'll take a look on the train later today.

> 
> Thanks
> Chris Berendes

yours, Marcus

Re: [Simpletest-support] 1.0.1 posts disabled form elements - where to patch?

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

Here's a brute force workaround patch to SimpleBrowser->clickSubmit() in
browser.php. Use at your own risk, YMMV, etc. Grateful for comments on where
to do it better.

         if (! ($form = &$this->_page->getFormBySubmit(new
SimpleByLabel($label)))) {
             return false;
         }
+        $disabled = false;
+        foreach ($form->_widgets as $index=>$element)
+        {
+            if (property_exists($element, '_attributes') &&
array_key_exists('disabled', $element->_attributes))
+            {
+                unset ($form->_widgets[$index]);
+                if (!$disabled) { echo '<hr>';}
+                echo '<br>not posted because disabled: ',
$element->_attributes['name'];
+                if (array_key_exists('value',$element->_attributes)) {echo
'=>',$element->_attributes['value'];}
+                echo '<br>';
+                $disabled=true;
+            }
+        }
+        if ($disabled) {$form->_widgets = array_values($form->_widgets);}
+
         $success = $this->_load(
                 $form->getAction(),
                 $form->submitButton(new SimpleByLabel($label),
$additional));



On Thu, Mar 17, 2011 at 10:18 PM, Christoph Berendes
<ber...@ne...>wrote:

> Hi.
>
> The 1.0.1 Simpletest clickSubmit method includes disabled form elements in
> the request, e.g.
> <input name="ddata" disabled value="goodbye">
> leads to ddata=goodbye in the request, when sent by Simpletest's
> clickSubmit method, but not by a standard browser.
>
> I'm happy to patch Simpletest for the moment to just omit disabled elements
> from the request, but I'd be grateful for guidance as to where, roughly to
> insert it , since I'm having some trouble unraveling the sequence of calls
> that lead to a post or get.
>
> Thanks
> Chris Berendes
>

[Simpletest-support] 1.0.1 posts disabled form elements - where to patch?

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

Hi.

The 1.0.1 Simpletest clickSubmit method includes disabled form elements in
the request, e.g.
<input name="ddata" disabled value="goodbye">
leads to ddata=goodbye in the request, when sent by Simpletest's clickSubmit
method, but not by a standard browser.

I'm happy to patch Simpletest for the moment to just omit disabled elements
from the request, but I'd be grateful for guidance as to where, roughly to
insert it , since I'm having some trouble unraveling the sequence of calls
that lead to a post or get.

Thanks
Chris Berendes

Re: [Simpletest-support] SimpleTest Plugin NOT Working

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

On Wed, Feb 23, 2011 at 12:32 AM, Anas Mughal <ana...@ya...> wrote:

>
> Okay, I had to restart Eclipse again. That fixed the problem with the
> preference window.
>
> Now, I have setup a test case as follows.
> When I run the test, I don't see any results in the "Result View" window.
>
> Please advise what I need to do to make SimpleTest work.
> Thanks.
>

Hello,

I am not sure where to start helping.  I have not maintained the Simpletest
Eclipse plugin (I am surprised it still works at all) and cannot guarantee
that it works with the version of Eclipse that you are using (I think I did
a quick check when 3.6 was released and confirmed the plugin still worked;
but I have not done any testing with 64bit java).

Have you tried following the step-by-step instructions in the usage
instructions?

http://simpletest.sourceforge.net/en/extension_eclipse.html#usage

These instructions are designed to provide the simplest possible php code to
verify that the plugin is working correctly.  When jump right in with your
own code (or other code) it is hard to know where the problem might lie
(include paths are a frequent problem).  I would suggest looking in your php
error logs and the console output (the plugin dumps the exact command line
command that it uses to the console, so you can copy and paste that to your
own command line to try and resolve the issue as well).  Another place to
look is the Eclipse "Error Log" view - this will tell you if the problem is
the underlying java code.

Hope that helps.

Regards,
Steven Balthazor

Re: [Simpletest-support] SimpleTest Plugin NOT Working

[Anas M. <ana...@ya...>]

Okay, I had to restart Eclipse again. That fixed the problem with the preference window.

Now, I have setup a test case as follows.
When I run the test, I don't see any results in the "Result View" window.

Please advise what I need to do to make SimpleTest work.
Thanks.


>>>>>>>>

<?php

loadModel('Post');

class PostTest extends Article {
    var $name = 'PostTest';
}


class PostTestCase extends CakeTestCase {

    function __construct() {
        parent::__construct('Log test');
    }

    function testPublished() {
        $this->assertEqual(true, false);
    }

}

?>

<<<<<<
 


       

--- On Tue, 2/22/11, Anas Mughal <ana...@ya...> wrote:

From: Anas Mughal <ana...@ya...>
Subject: [Simpletest-support] SimpleTest Plugin NOT Working
To: sim...@li...
Date: Tuesday, February 22, 2011, 2:45 PM


I am wondering if anyone encountered the following problem installing the SimpleTest plugin:



I have Eclipse Helios SR1 64-bit running on Mac OS X.



I downloaded and installed SimpleTest Plugin following the suggsted
directions. I do see the SimpleTest category in Eclipse Preferences.
However, when I click on it, it complains that it can't locate the
simpletest JAR file. 



Could someone advise... 



Thank you very much.

--Anas Mughal
http://anas-mughal.com      





      

[Simpletest-support] SimpleTest Plugin NOT Working

[Anas M. <ana...@ya...>]

I am wondering if anyone encountered the following problem installing the SimpleTest plugin:



I have Eclipse Helios SR1 64-bit running on Mac OS X.



I downloaded and installed SimpleTest Plugin following the suggsted
directions. I do see the SimpleTest category in Eclipse Preferences.
However, when I click on it, it complains that it can't locate the
simpletest JAR file. 



Could someone advise... 



Thank you very much.

--Anas Mughal
http://anas-mughal.com      


      

Re: [Simpletest-support] SimpleBrowser setField question

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

Hi...

Jason Sweat wrote:
> is where this gets used, default is to pass false.  Best I can determine, if 
> your selection criteria can identify multiple targets in the form, the position 
> parameter lets you target a specific one to set the value.

That's entirely correct. It's to disambiguate click targets with the
same name. It was too much of an edge case to clutter the tutorial with,
hence why it's an undocumented feature.

> 
> Regards,
> Jason

Thanks Jason.

yours, Marcus

Re: [Simpletest-support] Need help

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

Hi...

pradeep singh wrote:
> Please help me to solve the issue.

I suspect that the Eclipse module is now rather out of date. Can you try
your tests on the command line or browser? Tell me what happens and we
can proceed from there.

> 
> Thank You
> 
> Regards,
> 
> Pradeep

yours, Marcus

Re: [Simpletest-support] SimpleBrowser setField question

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

From: Richard Williams <ri...@ro...>

To: sim...@li...
Sent: Thu, January 27, 2011 3:46:59 PM
Subject: [Simpletest-support] SimpleBrowser setField question

>There is an argument "position" on the setField method of SimpleBrowser.  I
>cannot find any docs explaining its use or if it is actually used within
SimpleTest.

>Can someone enlighten me?

Hi Richard,

I am certain this will not count as enlightenment.

http://simpletest.org/api/__filesource/fsource_SimpleTest_WebTester_form.php.html#a233


is where this gets used, default is to pass false.  Best I can determine, if 
your selection criteria can identify multiple targets in the form, the position 
parameter lets you target a specific one to set the value.

Regards,
Jason


      

[Simpletest-support] SimpleBrowser setField question

[Richard W. <ri...@ro...>]

There is an argument "position" on the setField method of SimpleBrowser.  I
cannot find any docs explaining its use or if it is actually used within
SimpleTest.

Can someone enlighten me?

Richard

[Simpletest-support] Need help

[pradeep s. <er....@gm...>]

Hi!

I found below error while running simpletest.
I have easyeclipse as editor and codeigniter as framework.

PHP Deprecated:  Comments starting with '#' are deprecated in
/etc/php5/cli/conf.d/mcrypt.ini on line 1 in Unknown on line 0
Process returned: 255

Read error:Stream closed
[Ljava.lang.StackTraceElement;@c069ec
Process error:
PHP Fatal error:  Class 'GroupTest' not found in /tmp/Simpletest13835.php on
line 1

Please help me to solve the issue.

Thank You

Regards,

Pradeep

Re: [Simpletest-support] Fail fast?

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

There was an extensive thread on (almost) this topic a couple of months ago:

http://sourceforge.net/mailarchive/message.php?msg_id=26500668

As much as I'm in favor of test assertions throwing (which is how you implement fail-fast), I do agree with Chris that since this would be a backward incompatible change, it should not be the default. Either have a new set of assertions, or a different base class to inherit from, or a configuration switch, or something.  Then, people like Ben and myself can get the behavior we want, but people like Chris won't have all their existing tests break when they upgrade.

I assume what Ben is talking about is having a test method stop at the first assertion failure.  I would still expect that all the test methods in a test class get run.  At least that's the way I would do it (and is in line with most of the other X-Unit frameworks).


On Jan 5, 2011, at 3:59 PM, Christoph Berendes wrote:

> I'd prefer to have a configuration switch and if that's not possible to keep
> the current behavior.
> 
> We've been using Simpletest very happily for three years to test a
> moderately complex data collection website providing a nested set of forms
> for each user.
> 
> The argument against fast fail: yesterday, I made some underlying changes in
> the database - implementing InnoDB foreign key constraints, where before
> we'd relied just on PHP logic. I ran the test suite, and saw a handful of
> failures in one of the tests run "in the middle" of the suite. That was
> annoying, but it was helpful for my time planning to see that it was just
> part of one test file, rather than massive (or scattered) failures
> throughout.
> 
> With a "fast fail" constraint, I wouldn't have been able to distinguish, up
> front, between one failure that in effect hides dozens more (as I work
> through the code fixing bugs) or, as in this case, a single failure that
> really is the only failure in the test suite.
> 
> A "fast fail" option would be useful once I know the extent of the damage,
> in that it perhaps speeds up each test run and certainly reduces clutter.
> But my workaround is to to have separate test files, each relatively short,
> and a "run-all.php" in the directory as well. Once I see the extent of the
> problem via run-all, I can focus in on getting each individual test file to
> pass.
> 
> Chris Berendes
> 
> On Wed, Jan 5, 2011 at 3:33 PM, Marcus Baker <ma...@la...> wrote:
> 
>> Hi...
>> 
>> Solwitz, Benjamin wrote:
>>> Is it possible to configure simpletest to fail fast, that is, after the
>> first assertion failure, the rest of the test is skipped?
>> 
>> You can throw an exception instead, but no, there is no fail fast option
>> right now. I'm seriously thinking of switching to that behaviour as
>> default though unless I get a lot of objections.
>> 
>>> 
>>> Ben
>> 
>> 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
>> 
> ------------------------------------------------------------------------------
> 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


--
Roy Smith
roy...@s7...

Re: [Simpletest-support] Fail fast?

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

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

Hi, I'd just like to +1 this post.
T
On 01/05/2011 09:59 PM, Christoph Berendes wrote:
> I'd prefer to have a configuration switch and if that's not possible to keep
> the current behavior.
> 
> We've been using Simpletest very happily for three years to test a
> moderately complex data collection website providing a nested set of forms
> for each user.
> 
> The argument against fast fail: yesterday, I made some underlying changes in
> the database - implementing InnoDB foreign key constraints, where before
> we'd relied just on PHP logic. I ran the test suite, and saw a handful of
> failures in one of the tests run "in the middle" of the suite. That was
> annoying, but it was helpful for my time planning to see that it was just
> part of one test file, rather than massive (or scattered) failures
> throughout.
> 
> With a "fast fail" constraint, I wouldn't have been able to distinguish, up
> front, between one failure that in effect hides dozens more (as I work
> through the code fixing bugs) or, as in this case, a single failure that
> really is the only failure in the test suite.
> 
> A "fast fail" option would be useful once I know the extent of the damage,
> in that it perhaps speeds up each test run and certainly reduces clutter.
> But my workaround is to to have separate test files, each relatively short,
> and a "run-all.php" in the directory as well. Once I see the extent of the
> problem via run-all, I can focus in on getting each individual test file to
> pass.
> 
> Chris Berendes
> 
> On Wed, Jan 5, 2011 at 3:33 PM, Marcus Baker <ma...@la...> wrote:
> 
>> Hi...
>>
>> Solwitz, Benjamin wrote:
>>> Is it possible to configure simpletest to fail fast, that is, after the
>> first assertion failure, the rest of the test is skipped?
>>
>> You can throw an exception instead, but no, there is no fail fast option
>> right now. I'm seriously thinking of switching to that behaviour as
>> default though unless I get a lot of objections.
>>
>>>
>>> Ben
>>
>> 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
>>
> ------------------------------------------------------------------------------
> 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


- -- 
Tarjei Huse
Mobil: 920 63 413
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0leXEACgkQYVRKCnSvzfJQQgCeL9Nq/aUGb9nIbRmWtnDukXHr
cUkAn0XzyLWTKONmqUECQBCclvx6EZAb
=SkxG
-----END PGP SIGNATURE-----

Re: [Simpletest-support] Fail fast?

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

I'd prefer to have a configuration switch and if that's not possible to keep
the current behavior.

We've been using Simpletest very happily for three years to test a
moderately complex data collection website providing a nested set of forms
for each user.

The argument against fast fail: yesterday, I made some underlying changes in
the database - implementing InnoDB foreign key constraints, where before
we'd relied just on PHP logic. I ran the test suite, and saw a handful of
failures in one of the tests run "in the middle" of the suite. That was
annoying, but it was helpful for my time planning to see that it was just
part of one test file, rather than massive (or scattered) failures
throughout.

With a "fast fail" constraint, I wouldn't have been able to distinguish, up
front, between one failure that in effect hides dozens more (as I work
through the code fixing bugs) or, as in this case, a single failure that
really is the only failure in the test suite.

A "fast fail" option would be useful once I know the extent of the damage,
in that it perhaps speeds up each test run and certainly reduces clutter.
But my workaround is to to have separate test files, each relatively short,
and a "run-all.php" in the directory as well. Once I see the extent of the
problem via run-all, I can focus in on getting each individual test file to
pass.

Chris Berendes

On Wed, Jan 5, 2011 at 3:33 PM, Marcus Baker <ma...@la...> wrote:

> Hi...
>
> Solwitz, Benjamin wrote:
> > Is it possible to configure simpletest to fail fast, that is, after the
> first assertion failure, the rest of the test is skipped?
>
> You can throw an exception instead, but no, there is no fail fast option
> right now. I'm seriously thinking of switching to that behaviour as
> default though unless I get a lot of objections.
>
> >
> > Ben
>
> 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] Fail fast?

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

Hi...

Solwitz, Benjamin wrote:
> Is it possible to configure simpletest to fail fast, that is, after the first assertion failure, the rest of the test is skipped?

You can throw an exception instead, but no, there is no fail fast option
right now. I'm seriously thinking of switching to that behaviour as
default though unless I get a lot of objections.

> 
> Ben

yours, Marcus

Re: [Simpletest-support] Fail fast?

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

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

Hi,
On 01/04/2011 11:54 PM, Solwitz, Benjamin wrote:
> Is it possible to configure simpletest to fail fast, that is, after the first assertion failure, the rest of the test is skipped?
Currently not.

There was a discussion on this some time ago so you might want to
consult the list archives for more information.

Regards,
Tarjei
> 
> Ben
> ------------------------------------------------------------------------------
> 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


- -- 
Tarjei Huse
Mobil: 920 63 413
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0ktRsACgkQYVRKCnSvzfKnOQCgkUwctJU55V1DAs4c39MEKodt
/BsAoIMn3JihHGyXZrCIQRo3VIbxugRI
=XGnB
-----END PGP SIGNATURE-----

[Simpletest-support] Fail fast?

[Solwitz, B. <ben...@ny...>]

Is it possible to configure simpletest to fail fast, that is, after the first assertion failure, the rest of the test is skipped?

Ben