On Tue, Aug 3, 2010 at 1:27 PM, Sharma Vishav
wrote:
> yes you did answer my question
I forgot to say before, it is possible to automate tests even when
developers do not care about testability (and/or having automated tests),
but automation will be a lot easier if developers cared about it.
Žel
yes you did answer my question
thank you very much
On Tue, Aug 3, 2010 at 11:23 PM, Željko Filipin
wrote:
> 2010/8/3 Sharma Vishav
>> using element ID would be able to access element, as long as the
>> element ID and the frame it was defined originally does not change.
>
> Exactly. There is not
2010/8/3 Sharma Vishav
> using element ID would be able to access element, as long as the
> element ID and the frame it was defined originally does not change.
Exactly. There is not much you can do if the application changes a lot, but
even then fixing the tests would be easier if the element had
Thanks Zeljko,
To clarify when you say
you can use
> element ID to access the element and no matter where the element is located
> on the page."
using element ID would be able to access element, as long as the
element ID and the frame it was defined originally does not change.
On Tue, Aug 3, 20
On Tue, Aug 3, 2010 at 12:45 PM, Sharma Vishav
wrote:
> I am working on an agile project, where screens, hence underline HTML
> changes between sprints.
Application that I am testing is just changing technologies, so I face a
similar problem.
Make sure your Watir code is good quality.
The only
I like simplicity of Watir and ease of writing test cases with it.I am
working on an agile project, where screens, hence underline HTML
changes between sprints. Actual screens will get finalised towards
very end of the project. Watir scripts depend on HTML code to identify
elements and drive autom
