| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 10 months |
| seen | yesterday | |
| stats | profile views | 5 |
|
Nov 28 |
revised |
PageObjects: Aggregation/Composition vs Inheritance for nested components added flag |
|
Nov 28 |
awarded | Scholar |
|
Nov 28 |
comment |
Is Selenium's LoadableComponent a good solution as test design pattern? I still don't like very much the second issue. I'm using a PageObjects hierarchy to model the nested components of our UI. Take for instance their example. To me, it makes sense that EditIssue component also offers the signOut() method in its API (it'd pertain to SecuredPage component). However, the LoadableComponent implementations is fairy symple to include directly in my root component, so this is now also fine to me. |
|
Nov 28 |
comment |
Is Selenium's LoadableComponent a good solution as test design pattern? You have answered my first question, as after reading your answer I have noticed the important part I have missed from their documentation: "By using these assertions it's possible to give users of the class clear information that can be used to debug tests." That is, your checkWheterLoaded method is much too cumbersome compared to a list of informative assertTrues. I should have read the Are exceptions really for exceptional errors question in stackoverflow! |
|
Nov 28 |
comment |
Is Selenium's LoadableComponent a good solution as test design pattern? Thanks a lot for your answer. I'm afraid I didn't thought long enough about this, and your reasoning is what I was missing. The two things I didn't understand were: 1- Why use Errors to control the flow? (I wrote 'exceptions' meaning Throwables that must be caught); and 2- Why is LoadableComponent a class that must be extended, instead of an interface? |
|
Nov 28 |
accepted | Is Selenium's LoadableComponent a good solution as test design pattern? |
|
Nov 23 |
comment |
WebDriver API: 'Failed to send keys because cannot focus element' — better workaround than using Firefox instead of Chrome? Did you try using javascript directly? (for instance: sendkeys). (I'm sorry, it's to late to elaborate the answer anymore or to test it myself.) |
|
Nov 22 |
revised |
Is Selenium's LoadableComponent a good solution as test design pattern? explicit formatting. |
|
Sep 4 |
awarded | Teacher |
|
Jul 27 |
awarded | Quorum |
|
Jul 27 |
comment |
How to use Selenium's PageFactory annotations with dynamic loaded elements? Indeed, it works removing the mySelect.click(). I'm a bit confused now, as I was "double"-clicking due to Selenium's issue 2112. I have to check if without this "double" click it still works in my SUSE Linux Enterprise Server 11 box with Firefox 3.6.18 |
|
Jul 27 |
comment |
How to use Selenium's PageFactory annotations with dynamic loaded elements? I'm testing it now, and it seems that it doesn't work :-( The two consecutive clicks (in select and in option) are failing somehow, and unfortunately it is not easy to debug, as the debugger interferes with the normal flow. |
|
Jul 27 |
answered | How to use Selenium's PageFactory annotations with dynamic loaded elements? |
|
Jul 27 |
revised |
How to use Selenium's PageFactory annotations with dynamic loaded elements? code fragment simplified |
|
Jul 27 |
awarded | Supporter |
|
Jul 27 |
comment |
PageObjects: Aggregation/Composition vs Inheritance for nested components That's a good idea! I'll try to figure out how to combine it with IOC as you mention. |
|
Jul 27 |
awarded | Editor |
|
Jul 27 |
revised |
PageObjects: Aggregation/Composition vs Inheritance for nested components Title corrected |
|
Jul 26 |
asked | How to use Selenium's PageFactory annotations with dynamic loaded elements? |
|
Jul 26 |
awarded | Student |