On Wed, Sep 28, 2011 at 6:38 PM, Leo Arias <email address hidden> wrote:
> Hey guys.
>
> We have discussed about this on the u1 team, and reached a solution that
> made the developers and QAs happy.
>
> You might like to take a look: https://blueprints.launchpad.net
> /ubuntuone-testing/+spec/identifiers-for-webui-testing
Cool - thanks Leo, I just had a browse through and added the following
question to the discussion page:
Hi Leo, and thanks for all the work that's gone into this. The only
point that is unclear for me from above is whether you think it best
to add the data-qa-id to every element that your QA tests will use, or
just when a meaningful identifier matching the user experience is not
possible? Second point regarding the 'Con' of longer sst statements,
if the sst guys think the data-qa-id a great idea, I'm sure they won't
mind updating button_click and friends to check for data-qa-id after
id (or similar) -- Michael Nelson 2011-09-29 08:02:33
On Wed, Sep 28, 2011 at 6:38 PM, Leo Arias <email address hidden> wrote: /blueprints. launchpad. net testing/ +spec/identifie rs-for- webui-testing
> Hey guys.
>
> We have discussed about this on the u1 team, and reached a solution that
> made the developers and QAs happy.
>
> You might like to take a look: https:/
> /ubuntuone-
Cool - thanks Leo, I just had a browse through and added the following
question to the discussion page:
Hi Leo, and thanks for all the work that's gone into this. The only
point that is unclear for me from above is whether you think it best
to add the data-qa-id to every element that your QA tests will use, or
just when a meaningful identifier matching the user experience is not
possible? Second point regarding the 'Con' of longer sst statements,
if the sst guys think the data-qa-id a great idea, I'm sure they won't
mind updating button_click and friends to check for data-qa-id after
id (or similar) -- Michael Nelson 2011-09-29 08:02:33