Fitnesse - test sites - login fails

Not sure why it did not work, the fixture is there and implemented.
For site url, you only need the site name, e.g. "applicant".

Hi Mike,

I am also not able to work with Sites fixture. I am getting the error messages in 'login with username' command.

Below are the steps being followed:
- I have initialized my script with SitesFixture and other parameters as follows:
!*** Initialization
!| script | com.appiancorp.ps.automatedtest.fixture.SitesFixture |
| setup with browser | FIREFOX |
| set appian url to | mydastest.appiancloud.com/.../} |
| set appian version to | 17.1 |
| set appian locale to | en_GB |
| set timeout seconds to | 60 |
| set screenshot path to | C:\\SARASYSTEMS\\FitNesseForAppian\\SCREENSHOTS |
| set take error screenshots to | true |
| set stop on error to | true |
| set start datetime |
***!
- Used the following commands to login to sites and to navigate to a specific site
!*** Script to recognize the sites
!| script |
| login with username | CO | and password | PW |
| navigate to site |internal-user |
| click on menu | ACTIONS |
***!

When I run the above script, it opens the Firefox browser, logs in with the user details given by me and just hangs there. The error message shows at the login with username step.

Please let me know what I am doing incorrectly here. Thanks in advance.

--Kiran

Hi Kiran, the above code looks good, can you add one more step like, navigating to records or news first and then navigate to site.?

Hi Chandu,

Thanks for your reply. It does open the Sites page with Open command but after that it is not recognizing the menus. Check the below code snippet being used:
!*** Initialization
!| script | com.appiancorp.ps.automatedtest.fixture.TempoFixture |
| setup with browser | FIREFOX |
| set appian url to | mydastest.appiancloud.com/.../} |
| set appian version to | 17.1 |
| set appian locale to | en_GB |
| set timeout seconds to | 60 |
| set screenshot path to | C:\\SARASYSTEMS\\FitNesseForAppian\\SCREENSHOTS |
| set take error screenshots to | true |
| set stop on error to | true |
| set start datetime |
***!
!*** Validate change request as CO
!| script |
| login with username | ${UN_CO} | and password | ${PW_CO} |
| open |mydastest.appiancloud.com/.../internal-user|
| wait for | +2 seconds |
| click on menu | actions |
| click on link | Refer application |
| wait for | +2 seconds |
| logout |
*!

It throws the error in click on menu option (Object not found: Tempo Menu - actions). Also, logout doesn't seem to work as well (Object not found: Logout link).

Let me know if you are able to make it work for menus and logout.

Note: I could work with the links in page by navigating to actions url / application url which is not a good thing to do in script.

Thanks,
Kiran

Kiran,

For one site I wrote a test script for, I had to use the command |click on link| instead of |click on menu|. Perhaps that may be the same issue you are having.

Meagan

Hi Meagan,
Thanks for the response, that helped me.

Kiran,
I found a workaround for the logout. | logout | does not work in sites, try this:
1. Navigate back to Tempo | open | mydastest.appiancloud.com/suite/tempo |
2. Logout | logout |

Works in my scripts. I hope Appian could fix the FitNesse for sites as soon as possible.

Magnus

Yes, I used often |click on link|command when the tool cannot able to identify the object.

Thank you all. I was struck in similar situation and i used click on link.

Thank you all. I was struck in similar situation and i used click on link.

Well I have to mention that another way to solve the issue is to change from (instead of changing the menu to ,link)

If you are using :
!| script | com.appiancorp.ps.automatedtest.fixture.TempoFixture |
change it to
!| script | com.appiancorp.ps.automatedtest.fixture.SitesFixture |

NOTE: on the version Release 18.1.2 they changed the example that came on the FitnesseForAppian.

Please try that and comment here what you find

Jose