On Sat, 15 Mar 2014 22:34:01 +0100, Richard Lavoie
<[email protected]> wrote:
What about just changing the selector to rely on html markup instead of
actual text ?
This will solve the issue altogether of the I18n problem.
In this case probably yes, generally no. There are a lot of elements that
are rather obscure to identify using markup so we rely on text labels
quite often (repeatable elements for instance). Adding meaningful ids to
Jenkins UI elements will have other benefits besides UI tests but I am not
convinced it is a good idea (to avoid reading text labels). Verification
is often based on reading text that is a subject of localization. We can
probably rely exclusively on machine readable information like markup and
REST API but then we no longer have acceptance tests from perspective of a
human using web browser.
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
