add trigger integration test example

[hjlarry]

Related Issues or Context

This PR contains Changes to Non-Plugin

• Documentation
• Other

This PR contains Changes to Non-LLM Models Plugin

• I have Run Comprehensive Tests Relevant to My Changes

This PR contains Changes to LLM Models Plugin

• My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking)

• My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node)

• My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.)

• My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.)

• My Changes Affect Structured Output Format (JSON, XML, etc.)

• My Changes Affect Token Consumption Metrics

• My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.)

• Other Changes (Add New Models, Fix Model Parameters etc.)

Version Control (Any Changes to the Plugin Will Require Bumping the Version)

• I have Bumped Up the Version in Manifest.yaml (Top-Level Version Field, Not in Meta Section)

Dify Plugin SDK Version

• I have Ensured dify_plugin>=0.3.0,<0.6.0 is in requirements.txt (SDK docs)

Environment Verification (If Any Code Changes)

Local Deployment Environment

• Dify Version is: , I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration.

SaaS Environment

• I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration

[gemini-code-assist]

Summary of Changes

Hello @hjlarry, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the reliability of the telegram_trigger plugin by introducing a dedicated set of integration tests. These tests are designed to thoroughly validate the plugin's core functionality: accurately processing incoming Telegram webhook payloads and dispatching them to the correct internal events. By covering various scenarios, including valid message and callback queries, as well as error conditions like invalid secret tokens and unrecognized payload structures, this change ensures the trigger mechanism is robust and behaves as expected under diverse operational circumstances.

Highlights

• New Integration Tests: Introduced a comprehensive suite of integration tests for the telegram_trigger plugin to ensure robust webhook dispatching.
• Webhook Dispatch Logic Verification: Tests cover the correct parsing of Telegram webhook payloads and their routing to appropriate events, such as message_received and callback_query_received.
• Error Handling and Edge Cases: Added tests to validate secret token mechanisms and ensure proper handling of invalid tokens, as well as scenarios with unknown payload types.
• Pytest Fixture for PluginRunner: A new pytest fixture plugin_runner was added to efficiently manage the lifecycle of the PluginRunner for the telegram_trigger plugin across test modules.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a good set of integration tests for the Telegram trigger, covering different event types and error conditions. The tests are well-structured. I've provided a few suggestions to improve the tests by following pytest best practices, such as using fixtures to reduce code duplication and using pytest.raises for exception testing. These changes will make the tests more maintainable and readable.