Re: Best practice unit testing pages and components

2009-06-23 Thread Paul Field
Hi Kai, > > How would I test a page or a component when a @Parameter is not accessible > > because of its need to be a private variable? As well as tests directly on the page/component object that you can do with Tapestry's TestBase class, you can also write tests that run a page through one o

Re: Best practice unit testing pages and components

2009-06-22 Thread Igor Drobiazko
Take a look into this class: http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/ioc/test/TestBase.html The methods create, get and set are useful in tests. On Tue, Jun 23, 2009 at 12:19 AM, Kai Weber wrote: > How would I test a page or a component when a @Parameter is not acces

Re: Best practice unit testing pages and components

2009-06-22 Thread Thiago H. de Paula Figueiredo
Em Mon, 22 Jun 2009 19:19:27 -0300, Kai Weber escreveu: How would I test a page or a component when a @Parameter is not accessible because of its need to be a private variable? If the component is written by you, add a getter and a setter, probably with package visibility. -- Thiago H.

Best practice unit testing pages and components

2009-06-22 Thread Kai Weber
How would I test a page or a component when a @Parameter is not accessible because of its need to be a private variable? I want to test my pages and components with unit tests as I do with my service classes. Regards, Kai -