Skip to content

test for Xsup 67244#44183

Closed
BEAdi wants to merge 1 commit into
masterfrom
ae-update-crypto-4526
Closed

test for Xsup 67244#44183
BEAdi wants to merge 1 commit into
masterfrom
ae-update-crypto-4526

Conversation

@BEAdi
Copy link
Copy Markdown
Contributor

@BEAdi BEAdi commented May 4, 2026

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

Description

Test for #44123

Must have

  • Tests
  • Documentation

@BEAdi BEAdi added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label May 4, 2026
@content-bot
Copy link
Copy Markdown
Contributor

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 4, 2026

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/CommonScripts/Scripts/CertificateExtract
   CertificateExtract.py1343276%44–46, 48–50, 87–90, 92, 135, 138, 162, 179–180, 188, 207, 212, 374–375, 377–378, 386, 394, 468, 471, 477, 496–499
Packs/CommonScripts/Scripts/PFXAnalyzer
   PFXAnalyzer.py18012232%34–37, 42–46, 48–49, 55–56, 63, 65–69, 98, 100–102, 104–112, 124–129, 131, 144–151, 156–166, 168, 170–174, 179–182, 187–188, 190, 192–196, 213, 218, 220, 226–230, 232–233, 235–238, 240–248, 250–253, 255–256, 259, 272–273, 275, 277–278, 280–281, 283, 285–286, 288, 298, 304, 319, 329–330
Packs/Microsoft365Defender/Scripts/MS365DefenderAddComment
   MS365DefenderAddComment.py22672%23, 36–38, 40–41
Packs/MicrosoftCloudAppSecurity/Integrations/MicrosoftCloudAppSecurity
   MicrosoftCloudAppSecurity.py3812094%127–130, 139–140, 236, 252–253, 261–262, 267, 269, 341, 347, 752, 756–758, 796
Packs/MicrosoftGraphAPI/Integrations/MicrosoftGraphAPI
   MicrosoftGraphAPI.py47295%110–111
Packs/MicrosoftGraphSecurity/Integrations/MicrosoftGraphSecurity
   MicrosoftGraphSecurity.py112432571%101–102, 105, 108–109, 112–114, 117–119, 122–123, 126–128, 131–133, 136–138, 141–144, 147–148, 162–163, 166–167, 170–171, 174–175, 178–179, 182–183, 186–189, 192–193, 198–199, 212, 216–217, 222, 225–228, 231–233, 236–237, 243, 257–260, 263–264, 267–269, 272–274, 276–278, 280, 290–292, 295, 297, 300–301, 322–323, 328, 345–346, 372–373, 377, 400–403, 420–421, 438–441, 458–459, 492–493, 503–504, 515, 522, 525, 528, 533, 538, 545, 548, 555, 558, 564, 567–569, 574–579, 581, 598, 620–621, 660, 670, 673, 687, 713–716, 740–741, 743, 747, 817, 825–828, 830–831, 844, 872, 1091, 1123, 1161–1168, 1204–1208, 1363, 1387–1389, 1396–1397, 1402–1405, 1434, 1437, 1448–1450, 1459–1460, 1465–1473, 1478–1486, 1491–1495, 1500–1508, 1525–1527, 1530–1531, 1536–1544, 1561–1575, 1579, 1594–1600, 1633–1634, 1675, 1678, 1682–1683, 1703–1704, 1708–1709, 1717, 1726, 1735, 1745, 1754–1757, 1761, 1765, 1782, 1784, 1894, 1903–1904, 1907–1908, 1919, 1994, 2068, 2115, 2200, 2208, 2216, 2240–2241, 2452, 2522–2524, 2526, 2563, 2596, 2629, 2660, 2673, 2681, 2725–2726, 2730–2731, 2805–2810, 2818, 2820, 2822, 2824, 2826, 2828, 2830, 2832, 2834, 2838, 2841, 2846–2847
TOTAL188850773% 

Tests Skipped Failures Errors Time
115 0 💤 0 ❌ 0 🔥 4.628s ⏱️

@content-bot
Copy link
Copy Markdown
Contributor

Validate summary
The following errors were thrown as a part of this pr: RN103, DO106.
The following errors cannot be ignored: RN103, DO106.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: RN103, DO106.

Verdict: PR can be force merged from validate perspective? ✅

@BEAdi BEAdi changed the title test test for Xsup 67244 May 4, 2026
@content-bot
Copy link
Copy Markdown
Contributor

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: 581d2d7774e7d3c8

📋 Triage Report
💡 Resolutions are available in the full report.

⚠️ AI-generated triage. Validate before acting.

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

Labels

ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants