Skip to content

ATF: regression test for IRE identification of computers - #2677

Open
itam-automation wants to merge 2 commits into
ServiceNowDevProgram:mainfrom
itam-automation:feature/atf-ire-identification
Open

itam-automation wants to merge 2 commits into
ServiceNowDevProgram:mainfrom
itam-automation:feature/atf-ire-identification

Conversation

@itam-automation

@itam-automation itam-automation commented Nov 11, 2026 •

Copy link
Copy Markdown

PR Description:

A "Run Server Side Script" step (Jasmine 3.1) that checks the identification rules for computers: the same device sent twice must stay one CI, a renamed device must be found by its serial number, a new serial number must create a new CI, and a payload without identifying attributes must be rejected with MISSING_MATCHING_ATTRIBUTES. Useful after upgrades or changes to identification rules.

Tested on a PDI (Brazil) as an ATF test created in the global scope: all four specs passed and ATF rolled back the CIs. The README also notes one pitfall I ran into: if the test is created while a scoped application is selected, runtime access enforcement blocks the read on cmdb_ci_computer.

Pull Request Checklist

Overview

  • I have read and understood the CONTRIBUTING.md guidelines
  • My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
  • I've included only files relevant to the changes described in the PR title and description
  • I've created a new branch in my forked repository for this contribution

Code Quality

  • My code is relevant to ServiceNow developers
  • My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
  • I've disclosed use of ES2021 features (if applicable)
  • I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

  • I've placed my code snippet(s) in one of the required top-level categories
  • I've used appropriate sub-categories within the top-level categories
  • Each code snippet has its own folder with a descriptive name

Documentation

  • I've included a README.md file for each code snippet
  • The README.md includes description, usage, prerequisites

Restrictions

  • My PR does not include XML exports of ServiceNow records
  • My PR does not contain sensitive information (passwords, API keys, tokens)
  • My PR does not include changes that fall outside the described scope

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant