Hi Hans,
the short answer is no, you don't need to use page objects if you don't
feel the need for them.
Page objects are a design paradigm that enable you to encapsulate the
access to the business functionality exposed by the given web page and
make it easier to maintain it, while possibly changing the underlying
interaction, which can be at times rather complicated (web-speak and all).
The re-usability and readability criteria that you mention apply equally
to JBehave and BDD as they do the JUnit and unit testing. Even more so,
I would argue. E.g. they can be re-used across multiple steps classes.
It is true though that page objects introduce another layer between
steps and testing API, and it's up to you to decide if they are an
advantage or a hindrance. You can also introduce them when they are
needed and start off without them.
Cheers
On 16/09/2013 15:45, Hans Schwäbli wrote:
I started to write JBehave stories and steps and also page objects.
Some examples of JBehave contain page objects, so I thought this is a
good idea.
But now I ask myself what advantage there is if I write page objects?
The steps which I write are re-usable and I can structure them in a
similiar way like page objects (per page for instance).
Even today some people use JUnit for running GUI tests. I understand
that you need page objects with JUnit, because of re-usability and
readability.
But JBehave has its steps which are re-usable and readable, so why
should I write page objects addionally? I see no advantage but more
effort.
Did I overlook something? What would the disadvantage be of not using
page objects with JBehave?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
