Security analytics latest tests

[amsiglan]

Description

Updated tests for security analytics dashboards plugin

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[kavilla]

@amsiglan should this go into 2.10?

[amsiglan]

@amsiglan should this go into 2.10?

Yes, it would be nice if it did. I have the tests passing locally but not sure why they are failing to run altogether here

[kavilla]

manual backport: #826

[kavilla]

#834 will suffer from the same issue here

[amsiglan]

#834 will suffer from the same issue here

Updated the tests in this PR

[amsiglan]

#834 will suffer from the same issue here

Updated the tests in this PR

Updated this PR with all the latest changes that were merged for 2.10

[ashwin-pc]

The only major blocker here is the cypress commands. They are quite generic and can overide similar commands that other tests rely on. Ideally we should split them such that Security analytics specific commands are namespaced and others are moved to the common commands folder, but i'm also okay with just namespacing for now.

[amsiglan]

The only major blocker here is the cypress commands. They are quite generic and can overide similar commands that other tests rely on. Ideally we should split them such that Security analytics specific commands are namespaced and others are moved to the common commands folder, but i'm also okay with just namespacing for now.

Will look into moving common commands to a shared location. For now added sa_ prefix to all commands to make them unique enough

[kavilla]

How is this getting ran? I get failures locally like:

root_cause":[{"type":"action_request_validation_exception","reason":"Validation Failed: 1: rule_topic is missing;"}],"type":"action_request_validation_exception","reason":"Validation Failed: 1: rule_topic is missing;"},"status":400}',

[amsiglan]

How is this getting ran? I get failures locally like:

root_cause":[{"type":"action_request_validation_exception","reason":"Validation Failed: 1: rule_topic is missing;"}],"type":"action_request_validation_exception","reason":"Validation Failed: 1: rule_topic is missing;"},"status":400}',

The tests passed locally after the changes in latest commit

[amsiglan]

Screenshots with tests passing locally:

1. Detectors spec:

2. Rules spec:

3. Alerts spec:

4. Findings spec:

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-825-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c7195aef4ba6ee55a91b025bf614198966886d
# Push it to GitHub
git push --set-upstream origin backport/backport-825-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-825-to-2.x.

[opensearch-trigger-bot]

The backport to 2.11 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.11 2.11
# Navigate to the new working tree
cd .worktrees/backport-2.11
# Create a new branch
git switch --create backport/backport-825-to-2.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 85c7195aef4ba6ee55a91b025bf614198966886d
# Push it to GitHub
git push --set-upstream origin backport/backport-825-to-2.11
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.11

Then, create a pull request where the base branch is 2.11 and the compare/head branch is backport/backport-825-to-2.11.