Changes for page How to Develop Selenium Tests

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.kieran
	1	+XWiki.kiddyr

Content

...	...	@@ -21,7 +21,7 @@
21	21	* First fire up your WebObjects application and open the Selenium IDE
22	22	* In the Selenium IDE, insert commands for each user action.
23	23	* The most common commands you will use are clickAndWait, addSelection, open.
24		-* Specifying targets can be really easy as long as you are willing to sprinkle passive test identifiers into your WOComponents.
	24	+* Specifying targets can be really easy as long as you are willing to sprinkle passive test identifiers into your WOComponents.
25	25	** The easiest approach is to assign css classes to the elements you want to click on and then use that to identify the HTML element that is being clicked. So while your WO app is running, you can add css identifiers to the static or dynamic elements in your WOComponent, then save and refresh the page. Using FireBug's Inspect feature will allow you to easily verify the presence of your locator identifier.
26	26	** Other approaches:
27	27	*** Assign ids to html elements if you are sure the element will only ever appear once on the page. With the css class identifiers, Selenium will act on the first one it locates in the page.
...	...	@@ -42,3 +42,11 @@
42	42	The @repeat tag denotes the beginning of the portion to be repeated and the @done denotes the end of the portion to be repeated. These (can/cannot?) be nested?
43	43
44	44	The first pass thru the repeated segment, the actual values in the test are used and on consecutive repetitions the items from the @values list are substituted into the value part (the 3rd column) of the step immediately following the @values declaration
	45	+
	46	+{{panel title="WIKITODO"}}
	47	+
	48	+\* Flesh this out more with screenshots and examples for meta tags usage
	49	+
	50	+{{/panel}}
	51	+
	52	+\\