Instanbul (automated) Functional testing

Last month Jennifer provided us with the hype versus reality around the new Automated Testing Framework (ATF) within ServiceNow’s Istanbul release. This month I’d like to give my take and step you through the basic use of the application.

My slant:

Functional testing in ServiceNow hasn’t gotten much of a face lift in the last few releases. Istanbul changes this by bringing automated testing into ServiceNow without any 3rd party integration (regular testing application is still available).

Don’t worry “future me” (and others reading this whose job relies on functional testing to pay the bills), this automated testing WILL NOT replace an actual person. Someone will still have to write and run test scripts (or suites). Currently, the automated testing framework focuses on forms.

So how do you write these futuristic self-testing test cases? Well, let’s do this like a functional test case:

Roles needed: test designer

  1. Navigate to the ‘Automated Test Framework’.
  2. In another window navigate to ‘Test Client Runner’ PRO TIP to run the automated test faster, be sure to run in a window that has no other tabs open. DOUBLE PRO TIP if you pause or cancel during the test case you may be impersonating someone and be super confused what is going on and why you can’t do something.
  3. From here, select ‘Tests’ Module, and then the ‘new’ UI.
  4. Select the test case you just created (this is when the real fun begins).
  5. Select ‘add test step’ UI (look at all those options!)
  6. Select impersonate & then ‘next’ (this is a great best practice to always do)
  7. Choose the user (with the correct role(s)) to impersonate.
  8. From here, you can build your own test case; verify fields are present, mandatory, read only, etc.
    *Select ‘run test’ UI when ready to run a test case (it will run in the window you opened in test two)

If a test fails (it shouldn’t happen that often if you work with amazing people like I do), simply go to the results. The test results will show on which test step it failed via the ‘status field’, the ‘outputs’ field will have details on why it failed, and when all else fails…there are screen shots from every test step!!

Happy testing