tencent cloud

Serverless Cloud Function

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Related Concepts
How It Works
Strengths
Scenarios
Related Products
Purchase Guide
Billing Overview
Billing Mode
Billable Items and Billing Modes
Function Computing Power Support
Free Tier
SCF Pricing
Billing Example
Payment Overdue
Getting Started
Creating Event Function in Console
User Guide
Quota Management
Managing Functions
Web Function Management
Log Management
Concurrence Management
Trigger Management
Function URL
A Custom Domain Name
Version Management
Alias Management
Permission Management
Running Instance Management
Plugin Management
Managing Monitors and Alarms
Network Configuration
Layer Management
Execution Configuration
Extended Storage Management
DNS Caching Configuration
Resource Managed Mode Management
Near-Offline Resource Hosting Model
Workflow
Triggers
Trigger Overview
Trigger Event Message Structure Summary
API Gateway Trigger
COS Trigger
CLS Trigger
Timer Trigger
CKafka Trigger
Apache Kafka Trigger
MQTT Trigger
Trigger Configuration Description
MPS Trigger
CLB Trigger Description
TencentCloud API Trigger
Development Guide
Basic Concepts
Testing a Function
Environment Variables
Dependency Installation
Using Container Image
Error Types and Retry Policies
Dead Letter Queue
Connecting SCF to Database
Automated Deployment
Cloud Function Status Code
Common Errors and Solutions
Developer Tools
Serverless Web IDE
Calling SDK Across Functions
Third-Party Tools
Code Development
Python
Node.js
Golang
PHP
Java
Custom Runtime
Deploying Image as Function
Web Framework Development
Deploying Framework on Command Line
Quickly Deploying Egg Framework
Quickly Deploying Express Framework
Quickly Deploying Flask Framework
Quickly Deploying Koa Framework
Quickly Deploying Laravel Framework
Quickly Deploying Nest.js Framework
Quickly Deploying Next.js Framework
Quickly Deploying Nuxt.js Framework
Quickly Deploying Django Framework
Use Cases
Overview
Solutions with Tencent Cloud Services
Business Development
TRTC Practices
COS Practices
CKafka Practice
CLS
CLB Practice
MPS
CDN
CDWPG
VOD
SMS
ES
Scheduled Task
Video Processing
Success Stories
Tencent Online Education
Online Video Industry
Tencent Online Education
Best Practice of Tencent IEG Going Global
API Documentation
History
Introduction
API Category
Making API Requests
Other APIs
Namespace APIs
Layer Management APIs
Async Event Management APIs
Trigger APIs
Function APIs
Function and Layer Status Description
Data Types
Error Codes
SDK Documentation
FAQs
General
Web Function
Billing FAQs
Network FAQs
Log FAQs
SCF utility class
Event Handling FAQs
API Gateway Trigger FAQs
Related Agreement
Service Level Agreement
Contact Us
Glossary

Testing a Function

PDF
Focus Mode
Font Size
Last updated: 2024-12-02 19:46:29
After creating a function, you can directly test it in the following ways to understand the function execution conditions and check the code execution process.

Test Events and Templates

Functions are executed in an event-triggered method. Different triggers pass different event data structures when they trigger functions. The function testing method is to trigger the function by sending a simulated test event.
The SCF console provides the following event templates to simulate corresponding events:
Hello World event template: it contains simple data structure and content that can be used to trigger functions created by the hello world template.
COS file event template: it simulates file upload/deletion events in COS.
CMQ topic event template: it simulates message receiving events in a CMQ topic.
API Gateway event template: it simulates API request receiving events in API Gateway.
CKafka event template: it simulates message receiving events in a CKafka topic.
By clicking Change on the template management page in the console, you can change the currently used test template to another system-defined or custom template. For more information on message structures in event templates, please see Trigger Event Message Structure Summary.

Custom Template Configuration and Usage

In addition to the system-provided event templates, you can create more custom templates. By clicking Configure on the template management page in the console, you can modify an existing template and save it as a custom template, or directly enter a test event designed by yourself and save it as a custom template.

Notes

When using the test event template feature, you need to pay attention to the following:
The test event template name can contain letters, digits, hyphens, and underscores and must begin with a letter.
On the same page, the created custom test templates can be deleted if they are no longer needed.
Up to five custom test templates can be configured for one single function. After the limit is reached, to configure a new one, please first delete an old one that is no longer in use.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback