How to use ATF to test a custom checkout widget?

Per5
Giga Guru

We switched our service portal to Employee Center recently and activated shopping cart at the same time. 

The original checkout widget sc-shopping-cart-v2 did not fit our needs to we cloned it and changed the fields. 

The problem now is that I cannot create ATF testing for this custom widget. There is a test step for the original widget but nothing for custom widgets. 

I have looked at the test steps for custom UI but either I have to direct to an UI page or I have to scan the current page which doesn't work since the checkout widget is a pop-up window.

This is Rome, but we will upgrade to San Diego later this year. 

 

Is there a way to create a ATF step to test our custom checkout widget?

1 ACCEPTED SOLUTION

Hi,

That's what I mentioned in my 1st response.

ATF has limitations in terms of Custom UI Steps.

It becomes difficult to detect the HTML elements using Custom UI Steps and hence you will face difficult in achieving this.

Please inform your customer about this limitations.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

6 REPLIES 6

Ankur Bawiskar
Tera Patron
Tera Patron

Hi,

You can try to use Custom UI Test Steps but I have faced challenges in testing using ATF for custom portal and widgets

Also if you face any challenges ServiceNow won't help you since you have created custom components for your portal and ATF has few limitations around it.

Custom UI test steps

Regards
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Per5
Giga Guru

Thanks. I created a new portal page and added our custom widget, thinking I could use Custom UI Test Steps on that page.  

I also added the test step "Set Component Values (Custom UI)" but it doesn't pick up the fields in the widget. It only finds the search field. 

The fields are a reference field to sys_user and a date field. Is that a problem?

find_real_file.png

Hi,

That's what I mentioned in my 1st response.

ATF has limitations in terms of Custom UI Steps.

It becomes difficult to detect the HTML elements using Custom UI Steps and hence you will face difficult in achieving this.

Please inform your customer about this limitations.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

I had a feeling that this might be outside the limits of ATF and just wanted to see if I had missed something. Thanks for the help.