The online community for software testing & quality assurance professionals
 
 
Calendar   Today's Topics
Sponsors:




Lost Password?

Home
BetaSoft
Blogs
Jobs
Training
News
Links
Downloads



Software Testing >> Automated Testing

MrBungle
Member


Reged: 05/11/09
Posts: 85
Loc: Canada
Layers separation VS testing UI functionalities
      03/22/12 04:04 PM

Hi all,

So I'm still struggling at creating my first automation framework using WebDriver.

Today I was refactoring my page objects so that they encapsulate any reference to the UI, and keep them private.

My page objects won't let you "click a button", but they will let you "Navigate to a page", or "add a comment" etc. "Macro actions".

But somtehing struck me: if you need to test some UI functionality, your framework is useless then. Yes, you spent all that time making sure that the UI was in its own separate layer, and now you can't directly access it from your test layer anymore.
Isn't that a paradox? we have those UI automation tools, and we still use them only to validate business scenarios that could be validated without the UI (if an API is available of course).
But a failure on a particular UI element can lead to block a business scenario, and if you don't cover this particular business scenario, you're screwed. However, you would have found the bug if you had some automation testing all the states of this particular UI element.

Or maybe you just want to automate testing on a particular UI element that is known to be fragile.

Now even if I stick to the layer separation approach, in my application I can come across complicated screens with forms where there are many possible combinations possible before submitting the form.
It seems like a pain to make sure that my Page Object doesn't expose the UI, because it would mean I need a lot of different functions for my different combinations.
Sometimes it seems it would even be preferable to have one function per UI element, and let the test layer set everything, rather than having bigger UI abstracted functions from my page object for each combination.

It kind of kill the purpose of layers separation, doesn't it?

Edited by MrBungle (03/22/12 04:09 PM)

Post Extras Print Post   Remind Me!     Notify Moderator


Entire topic
Subject Posted by Posted on
* Layers separation VS testing UI functionalities MrBungle 03/22/12 04:04 PM
. * * Re: Layers separation VS testing UI functionalities dlai   03/23/12 12:26 AM
. * * Re: Layers separation VS testing UI functionalities MrBungle   04/12/12 03:03 AM
. * * Re: Layers separation VS testing UI functionalities dlai   04/12/12 07:41 AM
. * * Re: Layers separation VS testing UI functionalities MrBungle   04/12/12 08:27 PM
. * * Re: Layers separation VS testing UI functionalities dlai   04/13/12 09:36 AM

Extra information
0 registered and 14 anonymous users are browsing this forum.

Moderator:  Elfriede Dustin, AJ, Joe Strazzere 



Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Rating:
Thread views: 2243

Rate this thread

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5