Adding my own xml element , extensions/plugins....

[Mark.Winney]

Hi,
I have just subscribed to WebTest and have run against our test system
here, and it works exceptionally well.

I have wanted to ask if there is any procedures/examples of how to add
additional functionality to the tests, for example:
Within our product all the text on the web page is configurable via
property files.  These properties are loaded and held in the application
servers memory for fast accesses when rendering the web pages.  We have a
mechanism for modifying the properties in memory at run-time, by executing
a jsp on the server passing the property key and new value as query string
parameters.  ie.  http://changeproperty.jsp?key=abc&value=def.

To test a page fully, we modify all the text on a page, using this URL, and
then refresh the page, and we make sure all the text changed.

To do this via a WebTest how easy would it be to add a new plugin/feature,
xml element, such as <changeProperty key="abc" value="def" />
Can I just create a new jar file and add to the libs directory and away I
go?

Any help is appreciated.
Thanks
Mark Winney
Metavante [phone]
mark.winney(AT)metavante.com
---------------------------------------------------------------------
This message contains confidential and proprietary information of the
sender, and is intended only for the person(s) to whom it is addressed.
Any use, distribution, copying or disclosure by any other person is
strictly prohibited.  If you have received this message in error, please
notify the e-mail sender immediately, and delete the original message
without making a copy.

_______________________________________________
WebTest mailing list
WebTest@...
http://lists.canoo.com/mailman/listinfo/webtest

[Marc Guillemot]

Hi,

you can surely define your own Ant task (or WebTest step) in Java and
package it in a jar but it is easier to do it on the fly in the same
project.

One solution is to define your own macro the other one is to define
custom tasks/steps. In this second case, Groovy is your friend ;-)

Cheers,
Marc.

Mark.Winney@... wrote:

> Hi,
> I have just subscribed to WebTest and have run against our test system
> here, and it works exceptionally well.
>
> I have wanted to ask if there is any procedures/examples of how to add
> additional functionality to the tests, for example:
> Within our product all the text on the web page is configurable via
> property files.  These properties are loaded and held in the application
> servers memory for fast accesses when rendering the web pages.  We have a
> mechanism for modifying the properties in memory at run-time, by executing
> a jsp on the server passing the property key and new value as query string
> parameters.  ie.  http://changeproperty.jsp?key=abc&value=def.
>
> To test a page fully, we modify all the text on a page, using this URL, and
> then refresh the page, and we make sure all the text changed.
>
> To do this via a WebTest how easy would it be to add a new plugin/feature,
> xml element, such as <changeProperty key="abc" value="def" />
> Can I just create a new jar file and add to the libs directory and away I
> go?
>
> Any help is appreciated.
> Thanks
> Mark Winney
> Metavante [phone]
> mark.winney(AT)metavante.com
> ---------------------------------------------------------------------
> This message contains confidential and proprietary information of the
> sender, and is intended only for the person(s) to whom it is addressed.
> Any use, distribution, copying or disclosure by any other person is
> strictly prohibited.  If you have received this message in error, please
> notify the e-mail sender immediately, and delete the original message
> without making a copy.
>
> _______________________________________________
> WebTest mailing list
> WebTest@...
> http://lists.canoo.com/mailman/listinfo/webtest
>

_______________________________________________
WebTest mailing list
WebTest@...
http://lists.canoo.com/mailman/listinfo/webtest

[Mark.Winney]

Thanks Marc,
Do you have examples of how I can go about creating my own custom
task/steps - on the fly, using a macro, or Groovy?

Thanks
Mark Winney
Metavante [phone]
mark.winney(AT)metavante.com


                                                                                                                               
  From:       Marc Guillemot <mguillemot@...>                                                                            
                                                                                                                               
  To:         webtest@...                                                                                          
                                                                                                                               
  Date:       07/21/2009 01:29 AM                                                                                              
                                                                                                                               
  Subject:    Re: [Webtest] Adding my own xml element , extensions/plugins....                                                
                                                                                                                               





Hi,

you can surely define your own Ant task (or WebTest step) in Java and
package it in a jar but it is easier to do it on the fly in the same
project.

One solution is to define your own macro the other one is to define
custom tasks/steps. In this second case, Groovy is your friend ;-)

Cheers,
Marc.

Mark.Winney@... wrote:

> Hi,
> I have just subscribed to WebTest and have run against our test system
> here, and it works exceptionally well.
>
> I have wanted to ask if there is any procedures/examples of how to add
> additional functionality to the tests, for example:
> Within our product all the text on the web page is configurable via
> property files.  These properties are loaded and held in the application
> servers memory for fast accesses when rendering the web pages.  We have a
> mechanism for modifying the properties in memory at run-time, by

executing
> a jsp on the server passing the property key and new value as query
string
> parameters.  ie.  http://changeproperty.jsp?key=abc&value=def.
>
> To test a page fully, we modify all the text on a page, using this URL,
and
> then refresh the page, and we make sure all the text changed.
>
> To do this via a WebTest how easy would it be to add a new
plugin/feature,

> xml element, such as <changeProperty key="abc" value="def" />
> Can I just create a new jar file and add to the libs directory and away I
> go?
>
> Any help is appreciated.
> Thanks
> Mark Winney
> Metavante [phone]
> mark.winney(AT)metavante.com
> ---------------------------------------------------------------------
> This message contains confidential and proprietary information of the
> sender, and is intended only for the person(s) to whom it is addressed.
> Any use, distribution, copying or disclosure by any other person is
> strictly prohibited.  If you have received this message in error, please
> notify the e-mail sender immediately, and delete the original message
> without making a copy.
>
> _______________________________________________
> WebTest mailing list
> WebTest@...
> http://lists.canoo.com/mailman/listinfo/webtest
>

_______________________________________________
WebTest mailing list
WebTest@...
http://lists.canoo.com/mailman/listinfo/webtest



---------------------------------------------------------------------
This message contains confidential and proprietary information of the
sender, and is intended only for the person(s) to whom it is addressed.
Any use, distribution, copying or disclosure by any other person is
strictly prohibited.  If you have received this message in error, please
notify the e-mail sender immediately, and delete the original message
without making a copy.

_______________________________________________
WebTest mailing list
WebTest@...
http://lists.canoo.com/mailman/listinfo/webtest

[A Vander]

Sounds like all you need is a macro. You put it in your webtest as you typed it:
<changeProperty key="abc" value="def" />

Within the macro definition you translate it to an appropriate <invoke>.

Regards, Avander.