Repository navigation
ATF: regression test for IRE identification of computers - #2677
Open
itam-automation wants to merge 2 commits into
Open
itam-automation wants to merge 2 commits into
itam-automation wants to merge 2 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Code Quality
Repository Structure Compliance
Documentation
Restrictions