WASM Testing Station Usage

9. WASM Testing Station Usage#

Refer to the “How to set up scheduled actions?” and “When would I need to use these APIs?” sections to understand the need for file system implementation when executing these APIs. For example, after completing the Python implementation of his background task, Jack wants to test whether his code works correctly after converting it to WASM. If it does not execute correctly, Jack needs to identify where the problem lies. Therefore, Jack compiles the Python file into a WASM file using Py2wasm, then tests it on MailTrigger’s testing station (URL: TBD) using the following steps:

  1. Create a Test Suite: Create a test suite on the testing site and upload your WASM file.
    Example Image Description
  2. Add Email Archives: Add, update, or delete email archives to simulate mailbox activities.
    Example Image Description
  3. Execute WASM: Run your WASM file within the test suite. Check logs (stdout, stderr) to verify execution results.
    Example Image Description

  4. View Test Suite Logs: You can view the logs of the test suite execution to check results (stdout, stderr). Note that when using POST /api/{taskId}/action/execute API in the uploaded WASM implementation on the testing site, you must print the result of that API to view it in the logs. This is because the API does not actually execute any actions on the testing site. A status code of 201 indicates success.