AutomatePro AutoTest 101 shows business users how to test ServiceNow changes without writing code. With AutomatePro AutoTest, ServiceNow process owners, analysts, and managers turn everyday work into repeatable, automated tests using simple, visual building blocks.

Even better, as soon as your tests pass, you can send them straight into AutoDoc, which automatically produces training videos, user guides, and presentation-ready materials with almost zero extra work. Next, as you explore this step-by-step guide, you’ll learn the real meaning of a Test Plan, Test Block, Step, and Check in clear, everyday language. After that, you’ll build a simple test that logs in, opens a new Incident, and verifies the Caller field displays correctly. And before you’re done, you’ll understand why AutoTest runs in SubProd, why personas replace your login, and how to interpret test results quickly, without touching a line of code.

In this friendly starter guide, learn what a Test Plan, Test Block, Step, and Check mean. Along the way, build a first test that logs in, opens a new Incident, and confirms the Caller field appears. Discover why AutoTest runs in SubProd, why personas replace your own login, and how to read results quickly—without digging into code or logs.

---

Getting Started with AutomatePro AutoTest (No Code Required)

Testing ServiceNow no longer is a developer-only sport. With AutomatePro AutoTest for ServiceNow automated testing, you can:

• Capture how real users work.
• Turn that workflow into a no-code Test Plan.
• Run it again and again for upgrades, releases, and hotfixes.

---

What Is AutomatePro AutoTest and Why It Matters

At its core, AutomatePro AutoTest is an automated testing solution built specifically for ServiceNow. It protects your instance by running thousands of tests in hours instead of days, which dramatically reduces:

• Upgrade risk
• Release rework and rollback
• Manual regression effort across teams

Rather than manually clicking through forms after every change, AutoTest:

• Logs in like a real user
• Navigates the live UI
• Creates, updates, and approves records
• Verifies that ServiceNow behaves exactly as required

For non-technical users, this means you can finally:

• Use the business process you already know as the blueprint
• Capture that process visually in a Test Plan
• See what passed, what failed, and why in a single place

---

Key AutoTest Concepts in Plain Language

Test Plans: One End-to-End Business Process

A Test Plan is the full story of one business process in ServiceNow.

Common examples include:

• Create and Resolve Incident
• Submit and Approve Change
• Order and Receive a Laptop

Imagine asking a user: “Show me this process from start to finish.”
That end-to-end walkthrough becomes your Test Plan for no-code ServiceNow testing.

---

Test Blocks: Clear, Reusable User Activities

A Test Block represents one activity inside that bigger story.

For instance:

• Login
• Create Incident
• Approve Change
• Resolve Incident

Blocks keep long tests readable, modular, and reusable. The same Create Incident block can appear in multiple Test Plans, giving you fast, consistent ServiceNow automated testing.

---

Test Steps and Checks: Clicks and Validations

Inside each Block, AutoTest uses two simple ideas:

A Step performs an action:

• Login as ITIL user
• Navigate to Create New Incident
• Click Submit

A Check verifies the result:

Steps do the work. Checks prove the outcome. Together they create reliable, repeatable AutomatePro AutoTest 101 coverage for your key processes.

---

Quick Tutorial: Build Your First No-Code ServiceNow Test

Scenario: Log in, open a new Incident, and confirm the Caller field is visible.

1. Open the AutoTest Control Console

First, open the AutoTest workspace:

• In the ServiceNow filter, type “AutoTest”.
• Click Control Console (or Control Console (new)).
• Add it to Favorites for fast, one-click access.

---

2. Create and Name Your Test Plan

Next, define the process you want to protect:

• In Control Console, click Create New Test Plan.
• Set Test Plan Name to: Incident – Login and Caller Visible.
• Click Save.

You now have the container for your no-code ServiceNow test.

---

3. Add a “Create Incident” Test Block

Then, break the story into a clear activity:

• On the Test Plan form, go to Test Blocks.
• Click New.
• Name the block Create Incident.
• Click Submit.

You’ve described the activity. Now AutoTest needs to know how to perform it.

---

4. Add Login, Navigate, and Validate Steps

After defining the block, build out the actions:

• Click Test Plan Editor.
• Select the Create Incident Test Block.
• Open the Actions tab.

Add three Steps:

1. Login
   • Category: Authentication
   • Drag Login into the block.
   • Choose a persona user (for example, an ITIL persona).
   • Click Submit.
2. Navigate to Create New Incident
   • Category: Navigation
   • Drag Navigate to Module into the block.
   • Select Incident → Create New.
   • Click Submit.
3. Validate Form (placeholder)
   • Category: Validation
   • Drag Validate Form into the block.
   • Description: “Validate Incident form fields.”
   • Click Submit.

---

5. Add a Check for the Caller Field

Finally, add a Check so AutoTest knows what “success” looks like:

• In the Editor, select the Validate Form step.
• Open the Checks tab.
• Choose Display Validation → Forms → Field is shown.
• Drag Field is shown into the step.
• Set:
  • Table = Incident
  • Field = Caller
• Click Submit.

You’ve just built a fully executable no-code ServiceNow automated test that:

• Logs in as a persona
• Navigates to Create New Incident
• Confirms the Caller field appears

---

Run Your AutoTest and Read Results in Minutes

When you run a Test Plan, AutoTest creates a Test Run that records every detail.

What a Test Run Shows

From your Test Plan:

• Click Create Test Run.
• Open the new Test Run record.

You’ll immediately see:

• Overall status: In Progress → Executed
• Each Block, Step, and Check
• Which items passed and which failed
• Screenshots for failures (if configured)

Because everything lives in one record, non-technical users can review a full ServiceNow regression test without leaving the platform.

---

How Failures Help You Fix Issues Fast

Whenever a test fails, AutoTest clearly highlights:

• The exact Step or Check that failed
• A failure message in plain language
• An optional screenshot of the screen at failure time

Common simple causes include:

• Persona password has changed
• Module name was updated
• A field was removed from the form

You adjust the Test Plan or data, rerun the test, and quickly build a reliable regression safety net for that process.

---

AutoTest Personas, SubProd, and Retire (FAQ)

Why use personas instead of my own login or impersonate?

Personas are dedicated test users with stable roles. They:

• Stay consistent over time
• Appear clearly as test activity in logs
• Avoid audit confusion with real people running automation

By contrast, personal logins change passwords and roles, and impersonation—while helpful for support—creates noisy, hard-to-audit histories. Personas keep AutomatePro AutoTest clean, secure, and repeatable.

---

Why run AutoTest in SubProd instead of Production?

Because AutoTest can create and update large volumes of records, SubProd provides a safe playground where you can:

• Test new features thoroughly
• Validate upgrades before go-live
• Keep Production reports and dashboards clean

Even though Agile Stories and Changes may live in Prod, testing those changes belongs in SubProd, where it’s safe, controlled, and reversible.

---

What does “Retire” mean in Test Plans, Blocks, Steps, and Checks?

When you choose Retire, AutoTest:

• Marks the item inactive for new work
• Preserves it for history and audit
• Prevents teams from copying outdated patterns by accident

Retired items can be Recovered later if needed, making this a safe way to evolve your ServiceNow test suite over time.

---

How can I safely reuse Test Blocks and Steps?

To reuse work safely and efficiently, AutoTest offers Clone and Copy:

• Clone a Test Plan for a similar but slightly different process
• Copy a Test Block (for example, Create Incident) into multiple Test Plans

This approach keeps tests consistent, speeds setup, and steadily grows coverage for ServiceNow upgrades and releases.

---

From First Test to Full ServiceNow Regression Suite

Once your first test feels easy, you can expand step by step:

• Add Test Blocks for approve, resolve, and cancel flows
• Tag Test Plans by Application and Theme to visualize coverage
• Link Test Plans to Stories, Epics, and Releases for clear traceability

Over time, AutomatePro AutoTest evolves into a full ServiceNow regression suite that catches issues before they hit production—and, with AutoDoc, the same tests can power training content, user guides, and executive presentations with almost no rework.

Other AutomatePro AutoTest 101 Resources

• AutoTest Capability Maturity Model
• AutoTest Time to Value