Automation: Confirm UI Text

tufa4311a
Kilo Explorer

With Automation - how can I confirm the text of a pop-up that was triggered by a particular action? For example, if I attempt to create an Incident, do NOT fill in all required fields, and click submit, a pop-up message appears. Can automation confirm that the pop-up message contains the correct text? If the text in the pop-up should say "This field is missing data" - can automation confirm the UI pop-up message actually has that text in it?

1 ACCEPTED SOLUTION

Correct, currently there is no way to test that.


On the client side (visible data loaded in the browser window) ATF only provides a way to test some of the form functionality, there is no way to test how lists are loaded or the left nav items.


View solution in original post

15 REPLIES 15

Jace Benson
Mega Sage

Do you mean using the automated testing framework?


If so, it does not have a test step to check the text of the dialog List of Automated Test steps


Yes, that is what I meant.



Ok, then next question - this should be easy. I believe it is Click Modal Button step. In this all I want to do is click buttons from the left navigation menu, such as "Incident->Assigned To Me" and ensure it takes you to the correct page. I've been able to execute "Incident->Create New" by using the Open A New Form action. Here I just want to click on all of the navigation button from the left and ensure they go to the correct page.



Is that a Click Modal Button step? or is it the Click a UI Action step.



If it's Click Modal Button, what UI Page and what button?


If it's Click UI Action what table do I choose (sys_home?), what UI Action.


Neither.   Click Modal would handle GlideDialogWindow or GlideModal Form test step: Click Modal Button



I don't think the automated testing framework can test what you want the way you want.



You could have it load the records of the modules/applications, and verify the values though.


Follow-up on "You could have it load the records of the modules/applications, and verify the values though."



I think what you are saying here is that I can click on, say, "Incident->Open" and verify that the records there are all the expected Open Incidents? If that is the case, I think this would confirm my original goal anyway - obv if I can confirm all the records are Open records after clicking "Incident->Open" that will, by default, also confirm that it went to the right place.



Am I reading you right?