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

Re: [Simpletest-support] Licensing Question

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

If you want, we could also include this extension directly to the 
SimpleTest projet. What do you think ?

Yours,
	Perrick



Elijah Insua wrote:
> Great!
> 
> 
> Perrick Penet wrote:
>> SimpleTest has a LGPL license : it means you're OK to use it in your 
>> project.
>>
>> Yours,
>> 	Perrick Penet
>>
>>
>> Elijah Insua wrote:
>>   
>>> Greetings,
>>>
>>> I have created an ajax test runner initially using PHPUnit.
>>> Due to its flexible nature I have decided to include support for 
>>> SimpleTest as well.
>>> The project is licensed under the BSD license and I'm concerned about how
>>> releasing it as such would effect my ability to distribute my project.
>>>
>>> Source for connector: 
>>> http://trac.blerby.com/browser/project/TestRunner/library/Blerby/TestRunner/Runner/SimpleTest/Reporter.php
>>>
>>> I am not 'linking or compiling' the source in to the project, but I 
>>> would like to make certain that there is no breach.
>>>
>>> Thank You,
>>>
>>> Elijah Insua
>>>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>> _______________________________________________
>>> Simpletest-support mailing list
>>> Sim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>>>
>>>
>>>     
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Simpletest-support mailing list
>> Sim...@li...
>> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>>   
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
> 
> 

Re: [Simpletest-support] Licensing Question

[Elijah I. <tm...@gm...>]

Great!


Perrick Penet wrote:
> SimpleTest has a LGPL license : it means you're OK to use it in your 
> project.
>
> Yours,
> 	Perrick Penet
>
>
> Elijah Insua wrote:
>   
>> Greetings,
>>
>> I have created an ajax test runner initially using PHPUnit.
>> Due to its flexible nature I have decided to include support for 
>> SimpleTest as well.
>> The project is licensed under the BSD license and I'm concerned about how
>> releasing it as such would effect my ability to distribute my project.
>>
>> Source for connector: 
>> http://trac.blerby.com/browser/project/TestRunner/library/Blerby/TestRunner/Runner/SimpleTest/Reporter.php
>>
>> I am not 'linking or compiling' the source in to the project, but I 
>> would like to make certain that there is no breach.
>>
>> Thank You,
>>
>> Elijah Insua
>>
>>
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Simpletest-support mailing list
>> Sim...@li...
>> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>>
>>
>>     
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>   

Re: [Simpletest-support] Licensing Question

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

SimpleTest has a LGPL license : it means you're OK to use it in your 
project.

Yours,
	Perrick Penet


Elijah Insua wrote:
> Greetings,
> 
> I have created an ajax test runner initially using PHPUnit.
> Due to its flexible nature I have decided to include support for 
> SimpleTest as well.
> The project is licensed under the BSD license and I'm concerned about how
> releasing it as such would effect my ability to distribute my project.
> 
> Source for connector: 
> http://trac.blerby.com/browser/project/TestRunner/library/Blerby/TestRunner/Runner/SimpleTest/Reporter.php
> 
> I am not 'linking or compiling' the source in to the project, but I 
> would like to make certain that there is no breach.
> 
> Thank You,
> 
> Elijah Insua
> 
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
> 
> 

[Simpletest-support] Licensing Question

[Elijah I. <tm...@gm...>]

Greetings,

I have created an ajax test runner initially using PHPUnit.
Due to its flexible nature I have decided to include support for 
SimpleTest as well.
The project is licensed under the BSD license and I'm concerned about how
releasing it as such would effect my ability to distribute my project.

Source for connector: 
http://trac.blerby.com/browser/project/TestRunner/library/Blerby/TestRunner/Runner/SimpleTest/Reporter.php

I am not 'linking or compiling' the source in to the project, but I 
would like to make certain that there is no breach.

Thank You,

Elijah Insua

[Simpletest-support] input parameters to tests

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

Hi,

I find myself  wanting to pass in various test files for the tests to 
use.  But I will have a lot of tests so grouping them is needed.

For example if I want to pass in something I can do a:

**$test->addTestCase(new MyTestCase($infile));

what I think I want to do is a

******$test->addTestfile(mytestcase.php); and somehow invoke the 
constructor for that class/file...

this of course implies only one class per file.

reading the section on grouping tests sorta makes my mind spin as I 
don't quite understand
all of the implied implications. Like using addTestCase and a (new 
foo()).****

Thanks for any insight you can give.

-- 
Mark Donohoe
OSLO/OSTT, Cupertino CA.
fossology.org


-- 
Mark Donohoe
OSLO/OSTT, Cupertino CA.
fossology.org

[Simpletest-support] Webtester : basic authentication with post

[Guillaume G. <gui...@en...>]

Hi,

I have an issue with simpletest : I'm testing a web form. The 
destination webpage needs an authentification, and the form data is sent 
using POST.

Here is the code of my test class :

    $this->assertTrue($this->post($url,array("param1"=>"val1")));

    $this->assertResponse(401);

    $this->authenticate("foo","bar")

    $this->assertResponse(200);
      

The authentification process does not fail, but the data sent by post is 
not sent again when sending the authentification data.

When I use GET all my stuff is working great, but when I use POST, no 
post data is received by the destination page.

I think it that might be a bug.

Last thing : I created a little form test to verify that browsers 
actually send the post data twice. I tested with FF 3b, it worked.



Greetings

-- 
Guillaume Gautreau

[Simpletest-support] two web test case questions

[Roberto M. <rob...@sa...>]

Greetings,

I've just started playing with simpletest and love it so far. I'm trying
to create some web test cases for one of our legacy apps written in
plsql and I've hit two snags so far:

1. We have a page with a form which points to a plsql package:

  <form action="app.org_set">

The simpletest browser parses this relative url as a hostname instead of
a path/request. This appears to happen in SimpleUrl::_ChompHost() due to
the regex used here:

     if (preg_match('/[a-z0-9\-]+\.(' . $tlds . ')/i', $matches[1])) {

If I modify the regex with a "\b" or "$" at the end, it works fine for
this case. Any comments on this?

2. I'm trying to test forms with select lists. It looks like the
simpletest browser isn't parsing the select options for the list. This
legacy app doesn't generate the cleanest html so my options don't have a
closing tag. Could that be causing the problem? Any other ideas?

Thanks for any help.

Roberto

-- 
Roberto Mansfield
Institutional Research and Application Development (IRAD)
SAS Computing

Re: [Simpletest-support] 2 qns: Selenium, setField (newbie)

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

Sorry for the belated reply,

----- Original Message ----

>From: Marcus Baker <ma...@wo...>
>>George Herson wrote:
>> phpDocumentor qn: I found it in the API's class documentation but do you know why methods such as >> setField aren't in the API's index of elements (http://simpletest.org/api/)?
>
>No idea. This method has been around for a while. Could be a doc bug.

Just checked, a bunch out there now:


 setField 
WebTestCase::setField() in web_tester.php
Sets all form fields with that label, or name if there     is no label attached.
 setField 
SimpleForm::setField() in form.php
Sets a widget value within the form.
 setField 
SimplePage::setField() in page.php
Sets a field on each form in which the field is     available.
 setField 
SimpleFrameset::setField() in frames.php
Sets a field on each form in which the field is     available.
 setField 
SimpleBrowser::setField() in browser.php
Sets all form fields with that name.but in somewhat questionable order (they were at least in the "S" section :) )

Regards,
Jason


      

[Simpletest-support] How are relative paths translated?

[<el...@gm...>]

Hello, again,

I have a file at

    document_root/www/script.php

that uses an html template at

    document_root/www/templates/script.tpl

and whose URL is

    www.domain.com/script


This file passes a form to

  document_root/www/form_parser.php

but because the action field of the form is in the html template, which is
one level down in the file tree, the path is

   action = ../form_parser.php


Simpletest then tries to submit the form to

    www.domain.com/../form_parser.php


>From what I can tell, the server is using the absolute path of the html
template to translate the relative path, but Simpletest is using something
else (a $_SERVER var?) to translate relative paths.  Is this correct?  If
so, is there a file I could change to mimic what the server does?

Many thanks,
Erica

[Simpletest-support] I'm changing from Simpletest Eclipse to Simpletest Browser + Suggestions

[John B. <php...@mk...>]

Hi SimpleTest,

Over the past two hours I've been migrating my Simpletest test cases 
from the Eclipse plugin to a test suite that I can run from a web 
browser. Apparently clicking on a browser and pressing F5 is more 
appealing to me.

For reference I've zipped up the test part of my project, so if you're 
interested you can see how I've structured things:
http://mkv25.net/showcase/php-simpletest-obyr-tests.zip

I've tried to keep the number of lines of junk code down to a minimum, I 
think I've mostly achieved that.
I guess I wanted to show that the revised addFile function in 
run_tests.php helps neaten up the test suite file.

I've used simpletest/autorun.php ... based on simpletest's own 
test/all_tests.php script, because again, I've been too lazy to read the 
documentation and write my own harness for running tests, well, until 
now I guess.

Few suggestions for the web test results page:
- A timer that reports how long the script / tests took to execute, 
that'd be cool
- A break down of the actual test methods that were called, and not just 
a counter of passes
- When tests do fail, red boxes separated the results would be great
 o (Presentation: make it easier to tell how many fails, and which tests 
failed, headings, dividing lines, boxes)
- JavaScript expand/collapse test cases from the browser
 o (Use case: New programmer brought onto team, wants to explore program 
code, runs tests first, browses list of tests cases to understand 
program structure, gets used to running and breaking tests)
- JavaScript / HTML Form - Enable + disable test cases and rerun them 
(to reduce execution time)
 o (Use case: Running full suite of tests takes several minutes, 
enabling only local test speeds things up, all tests can be enabled 
later on after local tests are confirmed, central place / script to 
access all tests)

...
Maybe I'm reading into this too much, but those features could 
potentially save people a lot of time (perhaps in program comprehension 
if not writing and running test cases).

Disadvantage of my test strucutre: have ended up localising the 
simpletest/ folder to my project, could end up with multiple copies 
floating around. Trying to make project / test suite eclipse independent 
(Not that I don't like using eclipse).

Best regards,
- John
 

Re: [Simpletest-support] submitting form to relative path

[<el...@gm...>]

Thanks, John, for the good idea.  I commented out the redirect on the page
that was working so I could compare the requests directly.

Ohhhh my gosh.  This is a bit of a can of worms...or Pandora's box....

There is a whole lot of Apache magic in the .htaccess files that isn't
translating to SimpleTest.  It's happening on two levels, and it's so
complicated and convoluted that, rather than go into it, I may just do a
search on the archives and start a new thread if I don't come up with
anything.

Thanks again for helping me get unstuck so I could diagnose the problem.
That's half the solution!

Cheers,
Erica

On Mon, May 26, 2008 at 4:59 PM, John Beech <php...@mk...>
wrote:

> Hi Erica,
>
> Could it be the encoding type of the form?
> "application/x-www-form-urlencoded " ... URL encoded post vars?
>
> How are you using ShowRequest and ShowHeaders?
> Can you compare the results of these from the two different form
> submissions?
>
> These are my best hypotheses at the moment.
>
> Regards,
> - John
>
>
> el...@gm... wrote:
> > Hi to all,
> >
> > I'm new SimpleTest and newer to the list.  Please point me to any
> > documentation or threads that have already covered this.  I searched but
> > couldn't find anything.
> >
> > I am testing a store that has a database backend.  One page's form is not
> > submitting properly, while another page's nearly identical form is.  I
> can't
> > figure out what the problem is with the first page.
> >
> > The page submitting its form *correctly* has this form tag:
> > <form name="select_widget_a" style="margin:0;"
> > action="../project_router.php" method="POST">
> >
> > It submits only hidden fields (that are already filled out).  When a user
> > submits the form, they click on a span that uses a onclick:submit(this)
> > javascript to submit it, but in SimpleTest I use SubmitFormByName, and it
> > passes the test.  I then echo out the current URL (using SimpleTest's
> > getURL) and the SimpleTest browser is on the next page that the user
> would
> > see.  The browser has opened ../project_router.php, which has stored the
> > value in the database and then used Location: to redirect the browser to
> the
> > next "visible" page.  So that's working as it should.
> >
> > The page submitting its form *incorrectly* has this form tag:
> > <form name="zidget_a_qty" style="display:inline; margin:0"
> > action="../router.php" method="post">
> >
> > It submits hidden fields (that are already filled out) along with one
> text
> > field that SimpleTest is able to assert and set correctly.  Regardless of
> > whether I use SubmitFormByName or ClickImage, SimpleTest seems to have a
> > problem submitting the form to the ../router.php page.  That page acts as
> > ../project_router.php acts by storing information in the database and
> then
> > using Location: to redirect the browser to the next "visible" page.
> > However, no information from the form is getting stored in the database.
> > Echoing out the URL shows:
> >
> > https://subdomain.domain.com/../router.php
> >
> > Obviously, that's not going to work, but why doesn't the other form have
> the
> > same problem with submitting to ../project_router.php?  Both pages being
> > tested are at the same level in the file tree, as are both files
> specified
> > in the action field.
> > Here is the display from ShowRequest:
> >
> > POST /../router.php HTTP/1.0
> > Host: subdomain.domain.com
> > Connection: close
> > Cookie: PHPSESSID=blahblahblahnumber
> > Content-Length: 73
> > Content-Type: application/x-www-form-urlencoded
> >
> >
> hiddenfield1=value1&hiddenfield2=value2&hiddenfield3=value3&quantity=SimpleTestValue&x=10&y=10
> > [x and y are from ClickImage parameters]
> >
> > Here is the display from ShowHeaders:
> >
> > HTTP/1.1 400 Bad Request
> > Date: Mon, 26 May 2008 20:52:07 GMT
> > Server: Apache/2.2.3 (Debian) DAV/2 ... PHP/5.2.0-8+etch11...
> > Content-Length: 442
> > Connection: close
> > Content-Type: text/html; charset=iso-8859-1
> >
> > Thanks in advance for any light you can shed on this, or any resources
> you
> > can point me to.
> >
> > Erica
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Simpletest-support mailing list
> Sim...@li...
> https://lists.sourceforge.net/lists/listinfo/simpletest-support
>

Re: [Simpletest-support] submitting form to relative path

[John B. <php...@mk...>]

Hi Erica,

Could it be the encoding type of the form?
"application/x-www-form-urlencoded " ... URL encoded post vars?

How are you using ShowRequest and ShowHeaders?
Can you compare the results of these from the two different form 
submissions?

These are my best hypotheses at the moment.

Regards,
- John


el...@gm... wrote:
> Hi to all,
>
> I'm new SimpleTest and newer to the list.  Please point me to any
> documentation or threads that have already covered this.  I searched but
> couldn't find anything.
>
> I am testing a store that has a database backend.  One page's form is not
> submitting properly, while another page's nearly identical form is.  I can't
> figure out what the problem is with the first page.
>
> The page submitting its form *correctly* has this form tag:
> <form name="select_widget_a" style="margin:0;"
> action="../project_router.php" method="POST">
>
> It submits only hidden fields (that are already filled out).  When a user
> submits the form, they click on a span that uses a onclick:submit(this)
> javascript to submit it, but in SimpleTest I use SubmitFormByName, and it
> passes the test.  I then echo out the current URL (using SimpleTest's
> getURL) and the SimpleTest browser is on the next page that the user would
> see.  The browser has opened ../project_router.php, which has stored the
> value in the database and then used Location: to redirect the browser to the
> next "visible" page.  So that's working as it should.
>
> The page submitting its form *incorrectly* has this form tag:
> <form name="zidget_a_qty" style="display:inline; margin:0"
> action="../router.php" method="post">
>
> It submits hidden fields (that are already filled out) along with one text
> field that SimpleTest is able to assert and set correctly.  Regardless of
> whether I use SubmitFormByName or ClickImage, SimpleTest seems to have a
> problem submitting the form to the ../router.php page.  That page acts as
> ../project_router.php acts by storing information in the database and then
> using Location: to redirect the browser to the next "visible" page.
> However, no information from the form is getting stored in the database.
> Echoing out the URL shows:
>
> https://subdomain.domain.com/../router.php
>
> Obviously, that's not going to work, but why doesn't the other form have the
> same problem with submitting to ../project_router.php?  Both pages being
> tested are at the same level in the file tree, as are both files specified
> in the action field.
> Here is the display from ShowRequest:
>
> POST /../router.php HTTP/1.0
> Host: subdomain.domain.com
> Connection: close
> Cookie: PHPSESSID=blahblahblahnumber
> Content-Length: 73
> Content-Type: application/x-www-form-urlencoded
>
> hiddenfield1=value1&hiddenfield2=value2&hiddenfield3=value3&quantity=SimpleTestValue&x=10&y=10
> [x and y are from ClickImage parameters]
>
> Here is the display from ShowHeaders:
>
> HTTP/1.1 400 Bad Request
> Date: Mon, 26 May 2008 20:52:07 GMT
> Server: Apache/2.2.3 (Debian) DAV/2 ... PHP/5.2.0-8+etch11...
> Content-Length: 442
> Connection: close
> Content-Type: text/html; charset=iso-8859-1
>
> Thanks in advance for any light you can shed on this, or any resources you
> can point me to.
>
> Erica
>   

[Simpletest-support] submitting form to relative path

[<el...@gm...>]

Hi to all,

I'm new SimpleTest and newer to the list.  Please point me to any
documentation or threads that have already covered this.  I searched but
couldn't find anything.

I am testing a store that has a database backend.  One page's form is not
submitting properly, while another page's nearly identical form is.  I can't
figure out what the problem is with the first page.

The page submitting its form *correctly* has this form tag:
<form name="select_widget_a" style="margin:0;"
action="../project_router.php" method="POST">

It submits only hidden fields (that are already filled out).  When a user
submits the form, they click on a span that uses a onclick:submit(this)
javascript to submit it, but in SimpleTest I use SubmitFormByName, and it
passes the test.  I then echo out the current URL (using SimpleTest's
getURL) and the SimpleTest browser is on the next page that the user would
see.  The browser has opened ../project_router.php, which has stored the
value in the database and then used Location: to redirect the browser to the
next "visible" page.  So that's working as it should.

The page submitting its form *incorrectly* has this form tag:
<form name="zidget_a_qty" style="display:inline; margin:0"
action="../router.php" method="post">

It submits hidden fields (that are already filled out) along with one text
field that SimpleTest is able to assert and set correctly.  Regardless of
whether I use SubmitFormByName or ClickImage, SimpleTest seems to have a
problem submitting the form to the ../router.php page.  That page acts as
../project_router.php acts by storing information in the database and then
using Location: to redirect the browser to the next "visible" page.
However, no information from the form is getting stored in the database.
Echoing out the URL shows:

https://subdomain.domain.com/../router.php

Obviously, that's not going to work, but why doesn't the other form have the
same problem with submitting to ../project_router.php?  Both pages being
tested are at the same level in the file tree, as are both files specified
in the action field.
Here is the display from ShowRequest:

POST /../router.php HTTP/1.0
Host: subdomain.domain.com
Connection: close
Cookie: PHPSESSID=blahblahblahnumber
Content-Length: 73
Content-Type: application/x-www-form-urlencoded

hiddenfield1=value1&hiddenfield2=value2&hiddenfield3=value3&quantity=SimpleTestValue&x=10&y=10
[x and y are from ClickImage parameters]

Here is the display from ShowHeaders:

HTTP/1.1 400 Bad Request
Date: Mon, 26 May 2008 20:52:07 GMT
Server: Apache/2.2.3 (Debian) DAV/2 ... PHP/5.2.0-8+etch11...
Content-Length: 442
Connection: close
Content-Type: text/html; charset=iso-8859-1

Thanks in advance for any light you can shed on this, or any resources you
can point me to.

Erica

Re: [Simpletest-support] Simpletest-support Digest, Vol 24, Issue 3

[Marc L. <ma...@ma...>]

Dagfinn Reiersøl wrote:
> Marc Lucke wrote:
>   
>> Jason Sweat wrote:
>>   
>>     
>>> ----- Original Message ----
>>>
>>> From: Marcus Baker <ma...@wo...>
>>>  
>>>     
>>>       
>>>>> Marc Lucke wrote:
>>>>> I'd like to give the command document.forms[num].submit();
>>>>>       
>>>>>         
>>>>>           
>>>> You don't have to. As long as you can identify the submit button, you 
>>>> should be OK. Normally the text of the button is enough.
>>>>     
>>>>       
>>>>         
>>> I think the original poster is implying that the buttons may not be 
>>> form submit buttons, but in fact just triggers for javascript to 
>>> submit a specific hidden form.  If I remember correctly, you can use 
>>> the WebTestCase::Post() method to simulate what javascript would be 
>>> requesting for the post operation.
>>>   
>>>     
>>>       
>>  > I would rather create or generate id attributes for all the forms and 
>> use submitFormById(). If possible.
>>
>> Hi!  I had my subscription on digest & so didn't see your replies until now.
>>
>> Specifically the submit buttons are just submit buttons but aren't 
>> distinguished from one another.  I don't want to change the code output 
>> from the server (politics.)
>>
>> So I'll have this:
>>
>> <form action="hi.php" method="post">
>>     <input type="hidden" name="how" value="with a smile on one's face" />
>>     <input type="submit" value="Say hi!" />
>> </form>
>> <form action="hi.php" method="post">
>>     <input type="hidden" name="how" value="holding onto one's valuables" />
>>     <input type="submit" value="Say hi!" />
>> </form>
>> ....
>> <form action="hi.php" method="post">
>>     <input type="hidden" name="how" value="in some way n, where n=k+1" />
>>     <input type="submit" value="Say hi!" />
>> </form>
>>
>> No name, no id, no value, no different text.  There is nothing 
>> distinguishable about the forms (except for the hidden input text, I 
>> guess) apart from that as a dom element they are forms[0], forms[1] ... 
>> forms[n]
>>
>> To me it seems like the answer is that I'm going to have to get freaky 
>> and find a workaround because simpletest doesn't provide what I need.
>>   
>>     
> Jason's suggestion to use the post() method should work. If for whatever 
> reason it turns out to be hard to get it to work, my tip is to press the 
> buttons manually and log $_REQUEST. Then you can copy the logged request 
> variables into the post() call.
>
>   
Yes, I see.  Hoping for something quicker, but yes.  Thanks guys.

Re: [Simpletest-support] Simpletest-support Digest, Vol 24, Issue 3

[Dagfinn R. <da...@re...>]

Marc Lucke wrote:
> Jason Sweat wrote:
>   
>> ----- Original Message ----
>>
>> From: Marcus Baker <ma...@wo...>
>>  
>>     
>>>> Marc Lucke wrote:
>>>> I'd like to give the command document.forms[num].submit();
>>>>       
>>>>         
>>> You don't have to. As long as you can identify the submit button, you 
>>> should be OK. Normally the text of the button is enough.
>>>     
>>>       
>> I think the original poster is implying that the buttons may not be 
>> form submit buttons, but in fact just triggers for javascript to 
>> submit a specific hidden form.  If I remember correctly, you can use 
>> the WebTestCase::Post() method to simulate what javascript would be 
>> requesting for the post operation.
>>   
>>     
>  > I would rather create or generate id attributes for all the forms and 
> use submitFormById(). If possible.
>
> Hi!  I had my subscription on digest & so didn't see your replies until now.
>
> Specifically the submit buttons are just submit buttons but aren't 
> distinguished from one another.  I don't want to change the code output 
> from the server (politics.)
>
> So I'll have this:
>
> <form action="hi.php" method="post">
>     <input type="hidden" name="how" value="with a smile on one's face" />
>     <input type="submit" value="Say hi!" />
> </form>
> <form action="hi.php" method="post">
>     <input type="hidden" name="how" value="holding onto one's valuables" />
>     <input type="submit" value="Say hi!" />
> </form>
> ....
> <form action="hi.php" method="post">
>     <input type="hidden" name="how" value="in some way n, where n=k+1" />
>     <input type="submit" value="Say hi!" />
> </form>
>
> No name, no id, no value, no different text.  There is nothing 
> distinguishable about the forms (except for the hidden input text, I 
> guess) apart from that as a dom element they are forms[0], forms[1] ... 
> forms[n]
>
> To me it seems like the answer is that I'm going to have to get freaky 
> and find a workaround because simpletest doesn't provide what I need.
>   
Jason's suggestion to use the post() method should work. If for whatever 
reason it turns out to be hard to get it to work, my tip is to press the 
buttons manually and log $_REQUEST. Then you can copy the logged request 
variables into the post() call.

Re: [Simpletest-support] Simpletest-support Digest, Vol 24, Issue 3

[Marc L. <ma...@ma...>]

Jason Sweat wrote:
> ----- Original Message ----
>
> From: Marcus Baker <ma...@wo...>
>  
>>> Marc Lucke wrote:
>>> I'd like to give the command document.forms[num].submit();
>>>       
>> You don't have to. As long as you can identify the submit button, you 
>> should be OK. Normally the text of the button is enough.
>>     
>
> I think the original poster is implying that the buttons may not be 
> form submit buttons, but in fact just triggers for javascript to 
> submit a specific hidden form.  If I remember correctly, you can use 
> the WebTestCase::Post() method to simulate what javascript would be 
> requesting for the post operation.
>   
 > I would rather create or generate id attributes for all the forms and 
use submitFormById(). If possible.

Hi!  I had my subscription on digest & so didn't see your replies until now.

Specifically the submit buttons are just submit buttons but aren't 
distinguished from one another.  I don't want to change the code output 
from the server (politics.)

So I'll have this:

<form action="hi.php" method="post">
    <input type="hidden" name="how" value="with a smile on one's face" />
    <input type="submit" value="Say hi!" />
</form>
<form action="hi.php" method="post">
    <input type="hidden" name="how" value="holding onto one's valuables" />
    <input type="submit" value="Say hi!" />
</form>
....
<form action="hi.php" method="post">
    <input type="hidden" name="how" value="in some way n, where n=k+1" />
    <input type="submit" value="Say hi!" />
</form>

No name, no id, no value, no different text.  There is nothing 
distinguishable about the forms (except for the hidden input text, I 
guess) apart from that as a dom element they are forms[0], forms[1] ... 
forms[n]

To me it seems like the answer is that I'm going to have to get freaky 
and find a workaround because simpletest doesn't provide what I need.

Now to turn digest mode off.

Thanks for your answers guys.

Marc

Re: [Simpletest-support] SimpleTest @ php|tek

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

----- Original Message ----

>From: Travis Swicegood <dev...@do...>
>Hey Guys;
>
>I know Jason Sweat is going to be at php|tek in Chicago, anyone else  
>going?  Look me up if you're going to be there...
>
>-T

Yep, I am here!!!  Looking for other SimpleTesters :)

Jason



      

[Simpletest-support] SimpleTest @ php|tek

[Travis S. <dev...@do...>]

Hey Guys;

I know Jason Sweat is going to be at php|tek in Chicago, anyone else  
going?  Look me up if you're going to be there...

-T

Re: [Simpletest-support] newbie question: forms[num]

[Dagfinn R. <da...@re...>]

Jason Sweat wrote:
> ----- Original Message ----
>
> From: Marcus Baker <ma...@wo...>
>   
>>> Marc Lucke wrote:
>>> I'd like to give the command document.forms[num].submit();
>>>       
>> You don't have to. As long as you can identify the submit button, 
>> you should be OK. Normally the text of the button is enough.
>>     
>
> I think the original poster is implying that the buttons may not be form submit buttons, but in fact just triggers for javascript to submit a specific hidden form.  If I remember correctly, you can use the WebTestCase::Post() method to simulate what javascript would be requesting for the post operation.
>   
I would rather create or generate id attributes for all the forms and 
use submitFormById(). If possible.

Re: [Simpletest-support] methods marked "deprecated"

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

Hi...

Perrick Penet wrote:
> Looking for the keyword "deprecated", I noticed that 
> SimpleTest::getMockBaseClass() was still used in the "mock_objects.php". 
> It seems to contradict one of our "[task] Remove all deprecated 
> methods". Should we keep it for at least one more release while its use 
> is being removed ?

We have to. I tried to get rid of it and failed, because our own test 
suite uses it too much.

> 
> Yours,
> 	Perrick

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

Re: [Simpletest-support] newbie question: forms[num]

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

----- Original Message ----

From: Marcus Baker <ma...@wo...>
>>Marc Lucke wrote:
> >I'd like to give the command document.forms[num].submit();
>You don't have to. As long as you can identify the submit button, 
>you should be OK. Normally the text of the button is enough.

I think the original poster is implying that the buttons may not be form submit buttons, but in fact just triggers for javascript to submit a specific hidden form.  If I remember correctly, you can use the WebTestCase::Post() method to simulate what javascript would be requesting for the post operation.

Regards,
Jason



      

Re: [Simpletest-support] newbie question: forms[num]

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

Hi...

Marc Lucke wrote:
> I'd like to give the command document.forms[num].submit();

You don't have to. As long as you can identify the submit button, 
you should be OK. Normally the text of the button is enough.

> Thanks in advance
> 
> 
> Marc

yours, Marcus

[Simpletest-support] newbie question: forms[num]

[Marc L. <ma...@ma...>]

Hi list,

I have a website I'm meant to automatically test which has 10 forms on 
it without name, ID or labels.  And the button names are all the same.

I'd like to give the command document.forms[num].submit();

where num is the number of the form I want to submit.


How do I do this?

Thanks in advance


Marc

[Simpletest-support] methods marked "deprecated"

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

Hi Marcus et all,

Looking for the keyword "deprecated", I noticed that 
SimpleTest::getMockBaseClass() was still used in the "mock_objects.php". 
It seems to contradict one of our "[task] Remove all deprecated 
methods". Should we keep it for at least one more release while its use 
is being removed ?

Yours,
	Perrick

Re: [Simpletest-support] WebTestCase - How do I populate form fields

[John B. <php...@mk...>]

Thanks Marcus- setField and assertText (and assertNoText) work great.

Sometimes you just become blind to the things nearest to you, I 
completely failed to read the next chapter.

I'm really pleased with the WebTestCase framework so far, I can write 
test-cases like I would for clicking through a browser, but I can run 
them much quicker then manually entering information. Clever stuff.

Kind regards,
- John


Marcus Baker wrote:
> Hi...
>
> John Beech wrote:
>> Hey,
>> I'm writing a tests for a user Registration page using the 
>> WebTestCase framework.
>> I want to test the registration form, but I don't see any methods for 
>> populating form fields.
>> How do you suggest I do this?
>
> $this->setField('username', 'me');
>
> See the docs, especially the page "Testing forms":
> http://www.lastcraft.com/form_testing_documentation.php
>
> (The simpletest.org site seems to be down right now)
>
> There are some extra undocumented options if you check out the code 
> itself.
>
>> And also, is there a better assertion for matching patterns that 
>> doesn't require encapsulating '/' around strings?
>
> $this->assertText()
>
> This will match visible text (and alt text).
>
>> If I can't find anything soon I'll switch to using the post($url, 
>> $params) request method, but that cirmuvents the form, which I don't 
>> want to do.
>
> It's the very next page in the manual :).
>
>>
>> Kind regards,
>> - John Beech
>
> yours, Marcus
>
>
>