Skip to content

[backend] feat(openaev-scenarios): add scenarios seedings (#1196)#1906

Open
Antoine-Quintin wants to merge 2 commits intodevelopmentfrom
issue/1196
Open

[backend] feat(openaev-scenarios): add scenarios seedings (#1196)#1906
Antoine-Quintin wants to merge 2 commits intodevelopmentfrom
issue/1196

Conversation

@Antoine-Quintin
Copy link
Contributor

@Antoine-Quintin Antoine-Quintin commented Mar 20, 2026

Context

Briefly describe the purpose and context of this PR. Include relevant screenshots or screen recordings for the product team.

Adds 3 new OpenAEV scenario seeds for the development environment, so developers have realistic data available locally without having to create scenarios manually.

image

The following scenarios are now seeded:

  • Phishing Simulation — simulates a phishing campaign targeting organization users
  • Ransomware Simulation — simulates a ransomware attack on a Windows environment
  • Credential Brute Force — simulates a brute force attack on exposed authentication services

How to test

Provide step-by-step instructions to test your changes. Include screenshots of your local testing results.

1 - Navigate to the OpenAEV Scenarios Library page
2 - Verify that 5 scenario cards are visible, including the 3 newly added ones

Related issues

Checklist

Quality

  • I consider this work complete and ready for review
  • I tested all features and edge cases
  • I refactored code where necessary to improve quality
  • I made sure my code meets development guidelines
  • I performed a self-review of my code

Testing

  • I wrote test cases for the relevant use cases (unit, integration or e2e tests)
  • (Bug fixes only) I added tests that reproduce and verify the fix

What tests have been made

  • Unit tests
  • Integration tests
  • E2E tests
  • Local manual tests

Additional information

Any additional context, dependencies, or concerns reviewers should know about.

@Antoine-Quintin Antoine-Quintin self-assigned this Mar 20, 2026
@Antoine-Quintin Antoine-Quintin added Feature use for describing a new feature to develop tech Small technical tasks or data maintenance, such as updates, or minor arch fixes handled by devs P2 - Medium Must be fixed during the current release needs feature env Indicate if the PR needs an associated feature environment labels Mar 20, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 20, 2026

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
35 35 0 0 0 0 3m 39s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
35 0 0 23.9s

Suites

35 passed, 0 failed, and 0 other

Suite Passed Failed Other Duration
✅ app/apps/portal-e2e-tests/tests/tests_files/api/user.spec.ts
        ✅ should prevent user to update another one when he does not have MANAGE_ACCESS
        ✅ should allow user to update another one when he has ADMINISTRATE_ORGANIZATION
        ✅ should allow user to update another one when he has MANAGE_ACCESS
✅ 3 ❌ 0 ⏭️ 0 3.8s
✅ app/apps/portal-e2e-tests/tests/tests_files/capabilities.spec.ts
        ✅ Should add subscription with capabilities
✅ 1 ❌ 0 ⏭️ 0 23.9s
✅ app/apps/portal-e2e-tests/tests/tests_files/csv-feeds.spec.ts
        ✅ Should add CSV Feed
        ✅ Should delete CSV Feed from the list
        ✅ Should delete CSV Feed from the detailed page
✅ 3 ❌ 0 ⏭️ 0 19.9s
✅ app/apps/portal-e2e-tests/tests/tests_files/custom-dashboards.spec.ts
        ✅ Should add custom dashboard
        ✅ Should see the custom dashboard on public page
        ✅ Should edit a custom dashboard
✅ 3 ❌ 0 ⏭️ 0 28.3s
✅ app/apps/portal-e2e-tests/tests/tests_files/document.spec.ts
        ✅ should perform complete CRUD operations on documents
✅ 1 ❌ 0 ⏭️ 0 4.6s
✅ app/apps/portal-e2e-tests/tests/tests_files/one-click-deploy.spec.ts
        ✅ should send telemetry event
✅ 1 ❌ 0 ⏭️ 0 6.4s
✅ app/apps/portal-e2e-tests/tests/tests_files/organization-switcher.spec.ts
        ✅ Should see registered platforms, subscriptions and trials
✅ 1 ❌ 0 ⏭️ 0 4.4s
✅ app/apps/portal-e2e-tests/tests/tests_files/organizations.spec.ts
        ✅ should perform complete CRUD operations on organizations
✅ 1 ❌ 0 ⏭️ 0 5.2s
✅ app/apps/portal-e2e-tests/tests/tests_files/profile.spec.ts
        ✅ should update user profile information
✅ 1 ❌ 0 ⏭️ 0 4.7s
✅ app/apps/portal-e2e-tests/tests/tests_files/public/redirections.spec.ts
        ✅ should redirect user between public pages and login page
✅ 1 ❌ 0 ⏭️ 0 2.9s
✅ app/apps/portal-e2e-tests/tests/tests_files/registration.spec.ts
        ✅ should register openAEV platform
        ✅ should register openCTI platform
✅ 2 ❌ 0 ⏭️ 0 6.1s
✅ app/apps/portal-e2e-tests/tests/tests_files/service-management.spec.ts
        ✅ should be able to admin service
✅ 1 ❌ 0 ⏭️ 0 9.6s
✅ app/apps/portal-e2e-tests/tests/tests_files/service-pictures.spec.ts
        ✅ should be able to add pictures to a service
✅ 1 ❌ 0 ⏭️ 0 4.2s
✅ app/apps/portal-e2e-tests/tests/tests_files/streams.spec.ts
        ✅ Should add Stream
        ✅ Should delete Stream from the list
        ✅ Should delete Stream from the detailed page
✅ 3 ❌ 0 ⏭️ 0 21.0s
✅ app/apps/portal-e2e-tests/tests/tests_files/taxii-feeds.spec.ts
        ✅ Should add TAXII Feed
        ✅ Should delete TAXII Feed from the list
        ✅ Should delete TAXII Feed from the detailed page
✅ 3 ❌ 0 ⏭️ 0 21.0s
✅ app/apps/portal-e2e-tests/tests/tests_files/third-party-integrations.spec.ts
        ✅ Should add Third Party Integration
        ✅ Should delete Third Party Integration from the list
        ✅ Should delete Third Party Integration from the detailed page
✅ 3 ❌ 0 ⏭️ 0 20.3s
✅ app/apps/portal-e2e-tests/tests/tests_files/user.spec.ts
        ✅ Should perform complete CRUD of users as BYPASS
        ✅ Should only see authorized users
        ✅ Should not edit first and last name as MANAGE_ACCESS user
✅ 3 ❌ 0 ⏭️ 0 15.5s
✅ app/apps/portal-e2e-tests/tests/tests_files/xtm-suite-roadmap.spec.ts
        ✅ Should allow Filigran user to perform a CRUD of an epic
        ✅ Should allow users that are not connected to view the xtm suite roadmap
        ✅ Should allow community user to view the xtm suite roadmap
✅ 3 ❌ 0 ⏭️ 0 15.4s

🎉 No failed tests in this run. | 🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

🔄 This comment has been updated

@codecov
Copy link

codecov bot commented Mar 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 35.34%. Comparing base (5283de8) to head (1c68855).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##           development    #1906   +/-   ##
============================================
  Coverage        35.34%   35.34%           
============================================
  Files              657      657           
  Lines            41423    41423           
  Branches          2381     2381           
============================================
  Hits             14640    14640           
  Misses           26533    26533           
  Partials           250      250           

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5283de8...1c68855. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Antoine-Quintin Antoine-Quintin marked this pull request as ready for review March 20, 2026 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature use for describing a new feature to develop needs feature env Indicate if the PR needs an associated feature environment P2 - Medium Must be fixed during the current release tech Small technical tasks or data maintenance, such as updates, or minor arch fixes handled by devs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant