5.4 Kills PageTester

[Martin Kersten <ma...@gmail.com>]

Hi everyone,

   I just updated my pom today and removed all irritating dependencies
regarding to tapestry 5.3 and replaced them with their counterpart versions
of 5.4.

Now I run my page tester driven tests and it failed since the Page Tester
Constants class can be not found. It is just gone. The rest of page tester
is their so its broken beyond repair.

Looking for information I found this (its part of a blog post of Lewis)
tapestry-test deprecated

The tapestry-test module contains base classes used when writing TestNG,
Selenium, and EasyMock tests. It has been deprecated; users are directed to
the Spock Framework (as a replacement for TestNG and EasyMock), and to Geb
(which is a vastly improved wrapper around Selenium, and works nicely with
Spock).

The useful RandomDataSource class has been extracted into a new module,
tapestry-test-data.

The code for launching an instance of Jetty or Tomcat has been extracted to
a new module, tapestry-runner.

<<<>>

So this not funny I guess. So it seams that the tapestry way forces me to
spock and groovy for my testing. I just dont like it that much since I
program in java and I want to do unit testing for pages and components (ok
questionable) and I would like to stick to java here.

Since I asked a couple of days ago regarding to testing pages it seams that
I was encorraged encouraged to get up and ride a dead horse.

So I have two options. Switch to spock I am currently not familar with or
second extract the PageTester and maintain it outside of tapestry providing
it myself.

The problem came after I switched form alpha 21 to alpha 23. Did the class
just died by accident? As I said the rest is there.



Cheers,

Martin (Kersten),
Germany

Re: 5.4 Kills PageTester

[Martin Kersten <ma...@gmail.com>]

TapestryRunnerConstants was the class to vanish. I recreated it but the
page rendering is resulting in null response. Nothing is written so there
is something else to hunt for. I will extract the whole page tester related
classes (rewrote the PageTester class also) and the selenium is also
rewritten since I use JUnit test. So in the end I will move the support to
my own project then.


2013/10/16 Thiago H de Paula Figueiredo <th...@gmail.com>

> On Wed, 16 Oct 2013 17:34:52 -0300, Martin Kersten <
> martin.kersten.mk@gmail.com> wrote:
>
>  Hi everyone,
>>
>
> Hi!
>
>
>     I just updated my pom today and removed all irritating dependencies
>> regarding to tapestry 5.3 and replaced them with their counterpart
>> versions of 5.4.
>>
>
> Don't forget that 5.4 is an alpha version. It's not finished. Things can
> break from an alpha version to another. It's released so people can run it
> and report what they see.
>
> Please file a JIRA about it.
>
> Regarding tapestry-test and its support of TestNG and Selenium, if it
> really disappears (and I don't want that to happen), I (and everybody else)
> can make it reappear by copying the code to outside the Tapestry project
> just as I did with the old URL rewriter API which was deprecated then
> removed than ressurrected at https://github.com/thiagohp/**
> tapestry-url-rewriter <https://github.com/thiagohp/tapestry-url-rewriter>.
>
>
>  The problem came after I switched form alpha 21 to alpha 23. Did the
>> class just died by accident? As I said the rest is there.
>>
>
> I don't know the answer.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

Re: 5.4 Kills PageTester

[Thiago H de Paula Figueiredo <th...@gmail.com>]

On Wed, 16 Oct 2013 17:34:52 -0300, Martin Kersten  
<ma...@gmail.com> wrote:

> Hi everyone,

Hi!

>    I just updated my pom today and removed all irritating dependencies
> regarding to tapestry 5.3 and replaced them with their counterpart  
> versions of 5.4.

Don't forget that 5.4 is an alpha version. It's not finished. Things can  
break from an alpha version to another. It's released so people can run it  
and report what they see.

Please file a JIRA about it.

Regarding tapestry-test and its support of TestNG and Selenium, if it  
really disappears (and I don't want that to happen), I (and everybody  
else) can make it reappear by copying the code to outside the Tapestry  
project just as I did with the old URL rewriter API which was deprecated  
then removed than ressurrected at  
https://github.com/thiagohp/tapestry-url-rewriter.

> The problem came after I switched form alpha 21 to alpha 23. Did the  
> class just died by accident? As I said the rest is there.

I don't know the answer.

-- 
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org