Hi

The best way to learn testing tapestry is by reading the tests present in
the source code. Also, I learned a lot from the test written in chenillekit.

Hope it helps
regards
Taha

On Mon, Jun 20, 2011 at 5:22 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:

> On Mon, 20 Jun 2011 04:22:27 -0300, <p.stavrini...@albourne.com> wrote:
>
>  Hi Inge, Thiago,
>>
>
> Hi!
>
>
>  Firstly, Thanks guys for your replies!
>> I was aware of Jasmine, but not JsTestDriver... together they look very
>> promising (powerful) for unit tests. I think I will give them a go.
>>
>
> You're welcome!
>
>
>  As for Selenium, we had used it in the past for integration testing, but
>> we wrote only one larger scale test with broad coverage... It was pretty
>> good as well, but we found the test got outdated almost as quick as we could
>> write it.
>>
>
> Well, the idea of automated testing is to write the test before the tested
> feature or at least just after you implemented the feature. This quick
> outdating is quite strange: it seems the team is not writing tests in a more
> safe manner or the markup is changing very fast. Am I right? I work on
> projects which forbid commits without tests, almost all the tests are
> Selenium ones and we don't have this quick outdating you're experiencing. We
> do need to fix some tests after the markup it's based on changes, but this
> doesn't happen frequently.
>
>
>  After a time we were not maintaining it because it was quite time
>> consuming to do. Worst case I will revisit Selenium and have a rethink about
>> better maintenance this time.
>>
>
> If your tests are failing, the recommended approach is to stop development
> and fix bugs (code or tests) until all tests pass.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> and instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to