In an earlier post, I mentioned creating a custom approval state, “Rework.” It is used by my company as sort of a mid-way point between approval and rejection. (Maybe the request is missing information, or the approver would like to see something different in the request, but doesn’t want the requester to fill out the entire form again – just change the part that is wrong.) Today, we’ll examine how I did that. It’s really not that hard once you understand where to go to to make the changes.
So hopefully by now, you’ve set up your environment, understand how Selenium interacts with ServiceNow forms, wrote your first test (or more), and understand some common pitfalls that you may face during testing. Today we’ll talk about handling approvals, something I neglected in the first few posts.
Now that you have your environment set up, and have a basic understanding of how Selenium is going to interact with your ServiceNow instance, let’s move on to actually writing tests.
“Looks like you got your hands full.” A phrase I hear at least every day, sometimes more if I’m particularly unfortunate.
For several months now, I’ve been trying to automate the development testing for my job as a ServiceNow developer. It was not as easy as I thought it’d be. There have been many snags along the way, from page timeouts, how to interact with the ServiceNow forms (and Service Catalog pages), brittle tests, and just learning how to organize this process.