Re: Selenium testing

[Wayne W <wa...@gmail.com>]

Thanks all for your replies.
Food for thought there.

WicketTester seems the 'better' solution, but I'm trying to hand this over
to a QA person who cannot program. Ernesto - I think it would be a massive
undertaking for use to get the css paths working well enough so that there
was some consistency for Selenium.



On Mon, Jan 31, 2022 at 2:37 PM Ernesto Reinaldo Barreiro <
reiern70@gmail.com> wrote:

> Hi,
>
> Our app contains about 600 selenium tests... They are a pain to maintain
> even when we are trying to do things "the smart way". By this we mean:
>
>    - We have some reusable wicket components. E.g. some AJAX table with
>    lateral filtering facets. We roll in component marker CSS classes (e.g.
>    .facets, .facet, .date-time-facet) + "use custom key attributes" (e.g
>    facet-category="xxxx").
>    - We mirror this component structure at client side selenium tests. i.e.
>    we have a FacetsDriver that  hides low level complexity (e.g.
> FacetDriver
>    xxx = tableWithFacets.getFacteDriverFof("xxx") and xxx.select("aaa")).
>
> The above works fine (mostly). Except people sometimes forget to use proper
> ways and reinvent the wheel. Sometimes tests do not pass or are shaky for
> no clear reason and a lot of time goes into stabilizing those. We are using
> global AJAX blocker div for pages, to prevent component not found issues,
> this makes very easy to have a global waitForAjaxFinished().
>
> In summary. We run our tests on a server running in production mode. Thus
> we do not use any wicket path or anything similar, we use custom CSS
> classes + custom element attributes to give a more precise context.
>
> Hope this helps?
>
>
> On Mon, Jan 31, 2022 at 8:38 AM Wayne W <wa...@gmail.com>
> wrote:
>
> > Hello all,
> >
> > Is anyone out there successfully using Selenium to do regression testing?
> > It seems with the latest version of Selenium you cannot add custom
> > selectors anymore (the idea turning on
> > getDebugSettings().setComponentPathAttributeName("wicketpath") ). So it
> > just uses css selectors and xpath now.
> >
> > Whilst I can had craft css selectors to use the wicketpath attribute I
> > cannot get the IDE to use this by default. The problem is I want to hand
> > this over to our QA person but she is not technical nature and would
> > struggle to understand the correct selector when looking at the code and
> > also it would really slow down the whole process of setting up tests.
> >
> > Anyone got Selenium working well, or can recommend another tool for web
> > regressing testing that works well with Wicket?
> >
> > thanks
> >
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Re: Selenium testing

[Martin Terra <ma...@koodaripalvelut.com>]

ti 1. helmik. 2022 klo 13.32 Wayne W (waynemailinglists@gmail.com)
kirjoitti:

> Thanks all for your replies.
> Food for thought there.
>
> WicketTester seems the 'better' solution, but I'm trying to hand this over
> to a QA person who cannot program. Ernesto - I think it would be a massive
> undertaking for use to get the css paths working well enough so that there
> was some consistency for Selenium.
>

If your "coders" provide all handles, the QA person can probably invoke the
hooks. Anways, your success odds are better if your QA is somewhat code
savvy, for example comfortable with running and debugging from IDE etc.

You might also want to divide and conquer, the QA person manages strategy,
scope and stats of tests and their results, and (delegates)  coders
maintain the actual tests.

**
Martin


>
>
>
> On Mon, Jan 31, 2022 at 2:37 PM Ernesto Reinaldo Barreiro <
> reiern70@gmail.com> wrote:
>
> > Hi,
> >
> > Our app contains about 600 selenium tests... They are a pain to maintain
> > even when we are trying to do things "the smart way". By this we mean:
> >
> >    - We have some reusable wicket components. E.g. some AJAX table with
> >    lateral filtering facets. We roll in component marker CSS classes
> (e.g.
> >    .facets, .facet, .date-time-facet) + "use custom key attributes" (e.g
> >    facet-category="xxxx").
> >    - We mirror this component structure at client side selenium tests.
> i.e.
> >    we have a FacetsDriver that  hides low level complexity (e.g.
> > FacetDriver
> >    xxx = tableWithFacets.getFacteDriverFof("xxx") and xxx.select("aaa")).
> >
> > The above works fine (mostly). Except people sometimes forget to use
> proper
> > ways and reinvent the wheel. Sometimes tests do not pass or are shaky for
> > no clear reason and a lot of time goes into stabilizing those. We are
> using
> > global AJAX blocker div for pages, to prevent component not found issues,
> > this makes very easy to have a global waitForAjaxFinished().
> >
> > In summary. We run our tests on a server running in production mode. Thus
> > we do not use any wicket path or anything similar, we use custom CSS
> > classes + custom element attributes to give a more precise context.
> >
> > Hope this helps?
> >
> >
> > On Mon, Jan 31, 2022 at 8:38 AM Wayne W <wa...@gmail.com>
> > wrote:
> >
> > > Hello all,
> > >
> > > Is anyone out there successfully using Selenium to do regression
> testing?
> > > It seems with the latest version of Selenium you cannot add custom
> > > selectors anymore (the idea turning on
> > > getDebugSettings().setComponentPathAttributeName("wicketpath") ). So it
> > > just uses css selectors and xpath now.
> > >
> > > Whilst I can had craft css selectors to use the wicketpath attribute I
> > > cannot get the IDE to use this by default. The problem is I want to
> hand
> > > this over to our QA person but she is not technical nature and would
> > > struggle to understand the correct selector when looking at the code
> and
> > > also it would really slow down the whole process of setting up tests.
> > >
> > > Anyone got Selenium working well, or can recommend another tool for web
> > > regressing testing that works well with Wicket?
> > >
> > > thanks
> > >
> >
> >
> > --
> > Regards - Ernesto Reinaldo Barreiro
> >
>