Add early exit condition for message retrieval in Teams workflows

[kooomix]

PR Type

Enhancement

---

Description

• Added optimization to Teams workflow tests by implementing early exit condition
• When all required message types (misconfiguration, security risk, vulnerability) are found, the message retrieval loop terminates early
• Improves test efficiency by avoiding unnecessary API calls and iterations

---

Changes walkthrough 📝

	Relevant files
Enhancement	teams_workflows.py Add early exit optimization for Teams message verification tests_scripts/workflows/teams_workflows.py Added early exit condition in assert_messages_sent method when all required messages (misconfiguration, security risk, vulnerability) are found Optimizes test execution by avoiding unnecessary message retrieval iterations +2/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Logic Bug The early exit condition is placed after the loop counter increment but before retrieving messages, which means the last successful iteration's messages won't be processed. Consider moving the exit check to the end of the loop after processing messages.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Ensure at least one message retrieval attempt is made before checking exit conditions Move the early exit condition check to the end of the loop to ensure at least one iteration is performed and messages are retrieved at least once. tests_scripts/workflows/teams_workflows.py [209-213] for i in range(attempts): - if found_misconfiguration and found_security_risk and found_vulnerability: - break try: messages = self.test_obj["getMessagesFunc"](begin_time) + # ... process messages ... + if found_misconfiguration and found_security_risk and found_vulnerability: + break Suggestion importance[1-10]: 8 Why: Moving the exit condition check after message retrieval is crucial for test correctness, as the current implementation might exit prematurely without making any API calls, potentially missing important validation steps.	8

[github-actions]

Failed to generate code suggestions for PR