# `Sp_Task_doTest` (procedure)

> 定时过程执行


- **Type:** PROCEDURE
- **Deterministic:** NO
- **SQL data access:** CONTAINS SQL

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sBrId` | `varchar(100)` |
| 2 | IN | `sSuId` | `varchar(100)` |
| 3 | OUT | `sCode` | `int` |
| 4 | OUT | `sReturn` | `varchar(5000)` |

## Body

_Body is not pre-cached. To inspect: `mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURE `Sp_Task_doTest`'`._

## Narrative

**Business context:** Diagnostic / smoke-test procedure (COMMENT `'定时过程执行'`). Acts as the canonical reference implementation for the `Sp_Task_*` quartz-job family — `QuartzTask` hardcodes it as the dev fixture (`procedure.setsProcedureName("Sp_Task_doTest")`).

**What it does:** Inserts one row into table `test` with `(NewId(), sBrId, sSuId, '测试插入数据')`. Confirms scheduler→procedure plumbing without business side-effects.

**Invocation:** Reachable through `TaskServiceImpl.doProOne()` whenever a scheduled job names `Sp_Task_doTest` as `sProcedureName`. Wired directly into `QuartzTask` as the test fixture. Not bound to any `gdsmodule`/form-master entry.