feat(scenarios): add firmware update success scenario#133
Open
YANGCHUNHONG3000 wants to merge 1 commit into
Open
feat(scenarios): add firmware update success scenario#133YANGCHUNHONG3000 wants to merge 1 commit into
YANGCHUNHONG3000 wants to merge 1 commit into
Conversation
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
1 participant
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.
Add a new scenario to verify that a station undergoing a successful firmware update does not trigger any false positives:
expectedFailures: []— The trace describes a clean firmware update flow (BootNotification → FirmwareStatusNotification(Dowloaded) → FirmwareStatusNotification(Installed) → Heartbeat), which should not trigger any detection rule.assertions: [{ type: 'no_failures', params: {} }]— Verifies that no failures are detected, acting as a regression guard against overly aggressive detection rules.tests/external-fixture/test.mjswas also updated (line 161:15→16) because it has a hard-coded scenario count assertion.