FitnesseFor Appian

Anu over 7 years ago

Hi All,

I have a button before my login page which is nothing but a certificate page . I just want to click that button{I Agree} and proceed to my login screen . Here is my error and script . Please help!!

2016-12-15 16:42:14,473 [main] DEBUG com.appiancorp.ps.automatedtest.tempo.interfaces.TempoButton - WAIT FOR BUTTON [I Agree]
2016-12-15 16:43:15,098 [main] ERROR com.appiancorp.ps.automatedtest.exception.ExceptionBuilder - Wait for Button - I Agree
org.openqa.selenium.TimeoutException: Timed out after 60 seconds waiting for presence of element located by: By.xpath: //button[contains(translate(text(),'ABCDEFGHIJKLMNOPQRSTUVWXYZ','abcdefghijklmnopqrstuvwxyz'),'i agree') and not(contains(@class, 'button-disabled'))]
--------------------------------------------------------------------------------
Script:-
!*** CLick on AGree and go to login page
!| script |
|set timeout seconds to|60 |
|click o...

Discussion posts and replies are publicly visible

Top Replies

lucasj over 7 years ago +2
A Score Level 2

Hi Anushri, Try using "login with terms with username" rather than "login with username". This should work by itself without the need to tell FitNesse to click on the "I Agree" button

Parents

0 Ben Edwards
A Score Level 3
over 7 years ago

I'd agree with Chandra's idea above. Try replacing
| verify link |I Agree| is present |
with
| verify button |I Agree| is present |

Also do the same with the click statement.

As for custom functions, you can create a jar (typically placed in the /lib folder in the Fitnesse folder structure) that can be imported as a Fixture in automated tests that. You can see an example of how the given 'TempoFixture' is imported in the cheat sheet included in your Fitnesse implementation's documentation (typically at localhost:8980/FitNesseForAppian.CheatSheet). Check out the Fitnesse Full Reference Guide to see plenty of examples of source code for Fixtures: www.fitnesse.org/FitNesse.FullReferenceGuide.

Hopefully this helps some. If I can think of a good way to show a simple example of writing a Fixture I'll try to share. I'm not sure it's necessary for this scenario though because it seems like you just need to click a button. Did you try the 'screenshot' statement and get a good picture of what was happening at this moment?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Ben Edwards
A Score Level 3
over 7 years ago

I'd agree with Chandra's idea above. Try replacing
| verify link |I Agree| is present |
with
| verify button |I Agree| is present |

Also do the same with the click statement.

As for custom functions, you can create a jar (typically placed in the /lib folder in the Fitnesse folder structure) that can be imported as a Fixture in automated tests that. You can see an example of how the given 'TempoFixture' is imported in the cheat sheet included in your Fitnesse implementation's documentation (typically at localhost:8980/FitNesseForAppian.CheatSheet). Check out the Fitnesse Full Reference Guide to see plenty of examples of source code for Fixtures: www.fitnesse.org/FitNesse.FullReferenceGuide.

Hopefully this helps some. If I can think of a good way to show a simple example of writing a Fixture I'll try to share. I'm not sure it's necessary for this scenario though because it seems like you just need to click a button. Did you try the 'screenshot' statement and get a good picture of what was happening at this moment?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data