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

Re: [Simpletest-support] Beta5 release

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

Hi...

Culley Harrelson wrote:
> I have @ and - symbols in my user name and password.  Maybe this is the 
> problem?  I don't expect I would use this syntax much but I thought you 
> would want to know.

Fantastic! I have released it all but 30 seconds ago and you have 
reduced it to a train wreck :).

I am afraid I just didn't think of that one. Could you post a sample URL 
with the mangled characters in. I am not exactly sure of the parsing 
rules to cope with this (frankly I didn't even know it was legal). I 
assume if you use the authenticate() method all is OK.

> 
> culley

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

Re: [Simpletest-support] Beta5 release

[Culley H. <cu...@fa...>]

I just downloaded this and tested the authentication setup-- works 
great.  I got a failure when trying to use this format:

$this->get('http://Me:se...@my.../protected.html');

I have @ and - symbols in my user name and password.  Maybe this is the 
problem?  I don't expect I would use this syntax much but I thought you 
would want to know.

culley

[Simpletest-support] Beta5 release

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

Hi...

I have pushed out an interim release to fix requested issues, the main 
one being HTTP authentication. I wanted to get these fixes out as 
quickly as possible so that people could confirm these issues really are 
resolved. I'll try to add some documentation to the Lastcraft site and 
to the Sourceforge API describing all of this.

The other main fixes are with PHP5. I haven't been able to get XML 
support working properly, so this side of things may not work at all. 
Sorry, but I just couldn't test it. Also completely untested is SSL 
support so please don't play with matches and definitely don't use these 
features. I haven't tested this one Windows either as that box got wiped 
so that I could place PHP5 on Linux. Please someone tell me if there are 
any problems on this environment or any other.

On a positive note the redirects now allow short form URLs (called 
expandomatic would you believe) and work correctly with form submissions 
and authentication.

Frames support got pushed out of the backlog, but will be in RC1. Sorry 
about all of the delays getting these fixes out.

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

Re: [Simpletest-support] basic authentication

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

Hi...

Culley Harrelson wrote:
> I am back to working with web tester.  What is the status of user 
> authentication?  Working in CVS?

Yes. It will also be released as a Beta5 in a couple of days.

You can find some examples at the bottom of the test/live_tests.php file 
in the checkout. Here is the gist...

class MyTest extends WebTestCase {
     function MyTest() {
         $this->WebTestCase();
     }
     function testProtectedLogin() {
         $this->get('http://mysite.com/protected.html'); // 401
         $this->authenticate('Me', 'Secret');            // 200
         $this->assertWantedPattern('/Top secret/');
     }
     function testOneProtectedPageOnly() {
         $this->get('http://Me:se...@my.../protected.html'); // 200
         $this->assertWantedPattern('/Top secret/');
     }
}

A realm is considered a directory. Once logged into a particular 
directory, it will present the identity to subdirectories as well. If
you change out of that directory tree you have to log in again, but it 
is smart enough to combine directories.

> 
> culley

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

[Simpletest-support] basic authentication

[Culley H. <cu...@fl...>]

I am back to working with web tester.  What is the status of user 
authentication?  Working in CVS?

culley

Re: [Simpletest-support] [Fwd: Line numbers for failed tests]

[Zbynek W. <zw...@us...>]

Marcus Baker wrote:

>> I think "debug_backtrace" gives the needed information. It is 
>> available from version 4.3.0 up. It returns current stack information 
>> in an array. Each item also has a line number. In each "assert*" 
>> function the line number could be found just by looking up the stack.
>
>
> I am looking at this problem at last. 

Great!

> Do you want the line number of the actual assert type method in the 
> test case? Basically just a quick way of finding the failed assertion 
> amongst the test cases? I don't want to display an entire stack trace 
> as this kind of thing is better handled by XDebug.

Just the single line number, not the entire stack trace.
Thanks!
Zbynek

-- 
http://zw.matfyz.cz/     http://robotika.cz/
Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic

Re: [Simpletest-support] [Fwd: Line numbers for failed tests]

[Culley H. <cu...@fa...>]

On Mar 28, 2004, at 4:30 PM, Marcus Baker wrote:

> Hi...
>
> Zbynek Winkler wrote:
>> I think "debug_backtrace" gives the needed information. It is 
>> available from version 4.3.0 up. It returns current stack information 
>> in an array. Each item also has a line number. In each "assert*" 
>> function the line number could be found just by looking up the stack.
>
> I am looking at this problem at last. Do you want the line number of 
> the actual assert type method in the test case? Basically just a quick 
> way of finding the failed assertion amongst the test cases? I don't 
> want to display an entire stack trace as this kind of thing is better 
> handled by XDebug.
>

Not my question but yes I think this would be very helpful.  I have 
been simulating this and it would be great not to have to.  When you 
have 30 assertions in one test it can get confusing.

culley

Re: [Simpletest-support] [Fwd: Line numbers for failed tests]

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

Hi...

Zbynek Winkler wrote:
> I think "debug_backtrace" gives the needed information. It is available 
> from version 4.3.0 up. It returns current stack information in an array. 
> Each item also has a line number. In each "assert*" function the line 
> number could be found just by looking up the stack.

I am looking at this problem at last. Do you want the line number of the 
actual assert type method in the test case? Basically just a quick way 
of finding the failed assertion amongst the test cases? I don't want to 
display an entire stack trace as this kind of thing is better handled by 
XDebug.

> 
> Zbynek

yours, Marcus

> 
> PS. What is the preferred way of communication/discussion? Is the 
> simpletest-support list meant also for discussion like this or do you 
> prefer to keep things off the list?
> 

This list definitely. I tend to miss things placed in the trackers.
-- 
Marcus Baker, ma...@la..., no...@ap...

Re: [Simpletest-support] expectCallCount only in PartialMock?

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

Hi...

Jochen Bünnagel wrote:
 > Thoughts?
 >

Bizarre. Can you mail/post the test case?

 >
 > Jochen Buennagel

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

[Simpletest-support] expectCallCount only in PartialMock?

[<jb...@bu...>]

Hi!

I just wrote an expectCallCount that would always fail, finding 0 calls. 
When I changed the mock to a partial mock, the test suddenly passed. the 
only change was from "Mock::generate('DataAccess')" to 
"Mock::generatePartial('DataAccess', 'MockDataAccess', 
array('nextRow'))" (the callcount was on 'nextRow')...

Thoughts?


Jochen Buennagel

Re: [Simpletest-support] Should there be an interim Beta5?

[Jon R. <jo...@ba...>]

Hi,

On Thu, Mar 18, 2004 at 10:26:37PM +0000, Marcus Baker wrote:
> One thing that was unexpected thing about this project is that
> having automated control of the web environment is useful for all
> sorts of development tasks. Makes me think the web browser component
> should have been kept separate.

I bought the O'Reilly Spidering Hacks book a little while ago and I've
been jealous of the looks of Perl's LWP:: and WWW::Mechanize libs ever
since. I haven't used the SimpleTest browser stuff for a little while
but I'm sure that it already provides a lot of equivalent
functionality. I can definitely see an angle in separating it from
SimpleTest as much as is possible.

Cheers,

--
Jon Ramsey

Re: [Simpletest-support] Should there be an interim Beta5?

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

Hi...

Jason Sweat wrote:
> Could you use use something like the secure login page for sf.net or some other
> https site?

It is difficult to find one that is not also password protected and a 
possible source of abuse. I'll add it as an undocumented feature then. 
Use at your peril...

> Certainly.  It would be nice to replace this shell script:

Ok, you've got my sympathy vote :).

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

Re: [Simpletest-support] Should there be an interim Beta5?

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

Hi...

Jason Sweat wrote:
> Sounds reasonable to me.  I did not get a chance to reply to your "todo"
> requests earlier.  Mine would lean towards supporting https (perhaps via the
> curl extension?)

PHP4.3+ already supports this (just put 'tls:' as part of the socket 
address) although I've not tried it out. My problem with this is the 
hassle of setting up a test environment that is available on the web. I 
use my home site as part of the tests for SimpleTest and HTTPS si not 
supported by default. If someone could donate a permanent test server 
that would be OK. Otherwise it would have to be an unsupported feature.

If I add it would you be willing to test and debug it? :)

> 
> In addition to my web site monitoring idea,

One of my work colleagues is setting up some scripts to work with the 
Naggios monitoring tool. Should be interesting to hear his conclusions 
when he's done.

> a) configure a script to login as me

$browser = &new SimpleBrowser();
$browser->get('http://.../login.html');
$browser->setField('username', 'Jason');
$browser->setField('password', 'secret');
$browser->clickSubmit('Log in');

> b) check the status daily

Can't remember my cron syntax :(.

> c) if the due date is tomorrow, attempt to renew

$browser->get('info.html');
preg_match(
         '/Due date (\d+\/\d+\/\d+)/',
         $browser->getContent(),
         $matches);
if (! is_pending($matches[1])) {
     exit(0);
}

> d) check the renewal, and on failure email me

$browser->clickSubmit('Renew');
if (strpos('Cannot', $browser->getContent()) == false) {
     mail('jason@...', ...);
     exit(1);
}

> this would be what I am thinking of as a "personal web agent". Seems like many
> of the pieces are in the web tester.

One thing that was unexpected thing about this project is that having 
automated control of the web environment is useful for all sorts of 
development tasks. Makes me think the web browser component should have 
been kept separate.

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

Re: [Simpletest-support] Should there be an interim Beta5?

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

--- Marcus Baker <ma...@la...> wrote:
> I have amged to get a lot of HTTP fixes into the current development 
> cycle as well as browser hiostory buttons (retry, back, forward). I am 
> also adding basic authentication support. I feel this is enough for an 
> interim Beta5 release so that people can test these features sooner 
> rather than later. Otherwise there will probably be a lot of fixes in 
> the 1.0 release candidate.
> 
> What do people think? Are any of these items compelling enough to 
> warrant another release? Although unplanned it shouldn't affect current 
> development, which is still looking at mid-April for a release.

Sounds reasonable to me.  I did not get a chance to reply to your "todo"
requests earlier.  Mine would lean towards supporting https (perhaps via the
curl extension?)

In addition to my web site monitoring idea, I have had another crazy idea that
the web tester might fit into: a relatively simple scripting mechanism for an
"personal web agent".  i.e. there are certain web based tasks that it might be
nice to have done via a cron job.  My local library has a web page to check the
status of items checked out and allows you to renew the items once.  If it were
relatively easy to:
a) configure a script to login as me
b) check the status daily
c) if the due date is tomorrow, attempt to renew
d) check the renewal, and on failure email me
this would be what I am thinking of as a "personal web agent".  Seems like many
of the pieces are in the web tester.

__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

[Simpletest-support] Simpletest API documentation

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

Is now live at:
http://simpletest.sourceforge.net/

Happy browsing! :)

__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

[Simpletest-support] Should there be an interim Beta5?

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

Hi.

I have amged to get a lot of HTTP fixes into the current development 
cycle as well as browser hiostory buttons (retry, back, forward). I am 
also adding basic authentication support. I feel this is enough for an 
interim Beta5 release so that people can test these features sooner 
rather than later. Otherwise there will probably be a lot of fixes in 
the 1.0 release candidate.

What do people think? Are any of these items compelling enough to 
warrant another release? Although unplanned it shouldn't affect current 
development, which is still looking at mid-April for a release.

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

Re: [Simpletest-support] Using type= "button"

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

--- Marcus Baker <ma...@la...> wrote:
> Hi...
> 
> Thomas Purdy wrote:
> > No: It uses the OnClick attribute to go to another page.  There is no
> > JavaScript involved.  Thomas
> 
> OK, in that case there should be no problem. I'll queue the work. Can 
> you give me a pointer to the syntax on this as it seems my books are a 
> little out of date :(.

The whole point of the onClick attribute of any HTML element is to accept
content to pass to the browser agent's script engine.

Here is the RFC documenting the button element
http://www.w3.org/TR/html4/interact/forms.html#h-17.5
and the "generic" onClick attribute
http://www.w3.org/TR/html4/interact/scripts.html#adef-onclick
and the definition of what "script" content is
http://www.w3.org/TR/html4/types.html#type-script


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

Re: [Simpletest-support] Using type= "button"

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

Hi...

Thomas Purdy wrote:
> No: It uses the OnClick attribute to go to another page.  There is no
> JavaScript involved.  Thomas

OK, in that case there should be no problem. I'll queue the work. Can 
you give me a pointer to the syntax on this as it seems my books are a 
little out of date :(.

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

RE: [Simpletest-support] Using type= "button"

[Thomas P. <tp...@in...>]

No: It uses the OnClick attribute to go to another page.  There is no
JavaScript involved.  Thomas

-----Original Message-----
From: sim...@li...
[mailto:sim...@li...] On Behalf Of
Marcus Baker
Sent: Tuesday, March 16, 2004 4:05 PM
To: simpletest-support
Subject: Re: [Simpletest-support] Using type= "button"

Hi...

Thomas Purdy wrote:
> I have a couple forms that have buttons that I need to test.  What is 
> the Status on the support of type="button" by simple Test?  Thanks

If this involves JavaScript then the prognosis is not good. Is this teh 
case?

> Thomas
> 

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Simpletest-support mailing list
Sim...@li...
https://lists.sourceforge.net/lists/listinfo/simpletest-support

Re: [Simpletest-support] Using type= "button"

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

Hi...

Thomas Purdy wrote:
> I have a couple forms that have buttons that I need to test.  What is 
> the Status on the support of type="button" by simple Test?  Thanks

If this involves JavaScript then the prognosis is not good. Is this teh 
case?

> Thomas
> 

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

[Simpletest-support] Using type= "button"

[Thomas P. <tp...@in...>]

Hi:
 
I have a couple forms that have buttons that I need to test.  What is
the Status on the support of type= "button" by simple Test?  Thanks
 
Thomas

Re: [Simpletest-support] Test is Timeing out

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

--- Thomas Purdy <tp...@in...> wrote:
> Hi:
>  
> First I want to thank you Marcus for you prompt responses to emails.  It
> really helps.  I do have another question.  I have been running through
> various pages/forms on my site.  I am now getting an error:
>  
> Fatal error: Maximum execution time of 30 seconds exceeded in
> C:\test\simpletest\socket.php on line 115
>  
> I am wondering if this is because my test has gotten to large.  If so, I
> split my test into two tests that are still included in the
> Unit_tests.php  Is there a variable that I can change so my test can be
> longer?  Thanks
>  
> Thomas
> 

set_time_limit(0);


__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com

[Simpletest-support] Test is Timeing out

[Thomas P. <tp...@in...>]

Hi:
 
First I want to thank you Marcus for you prompt responses to emails.  It
really helps.  I do have another question.  I have been running through
various pages/forms on my site.  I am now getting an error:
 
Fatal error: Maximum execution time of 30 seconds exceeded in
C:\test\simpletest\socket.php on line 115
 
I am wondering if this is because my test has gotten to large.  If so, I
split my test into two tests that are still included in the
Unit_tests.php  Is there a variable that I can change so my test can be
longer?  Thanks
 
Thomas

Re: [Simpletest-support] Pop up windows?

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

Hi...

Thomas Purdy wrote:
> How does SimpleTest handle pop up windows?  I have a couple pages that 
> use them and I was wondering what the browser does with them.  Thanks

It doesn't :(. In fact no JavaScript parsing is done at all. This 
situation really won't improve until there is a php library that can 
handle it and there doesn't seem to be one on the horizon right now.

If you know the URL then you could call it straight after the main page 
and then test it separately. The catch is that this will change the 
current URL which is probably not what you want. SimpleTest doesn't yet 
support multiple simultaneous pages, but will when I have finished 
adding frames support, so a better work around may be available then.

> Thomas
> 

yours, Marcus
-- 
Marcus Baker, ma...@la..., no...@ap...

[Simpletest-support] Pop up windows?

[Thomas P. <tp...@in...>]

Hi:
 
How does SimpleTest handle pop up windows?  I have a couple pages that
use them and I was wondering what the browser does with them.  Thanks
 
Thomas