get_results
Retrieve test run results for a project to analyze performance and identify issues.
Instructions
Get all test run results for a project
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ||
| limit | No | ||
| offset | No | ||
| status | No | ||
| from | No | ||
| to | No |
Implementation Reference
- src/operations/results.ts:45-48 (handler)The core handler function implementing the logic for the 'get_results' tool. It pipes the bound Qase client results.getResults method through the toResult transformer utility.export const getResults = pipe( apply(client.results.getResults.bind(client.results)), toResult, );
- src/operations/results.ts:12-19 (schema)Zod schema defining the input parameters for the 'get_results' tool: project code, optional limit, offset, status filter, and date range.export const GetResultsSchema = z.object({ code: z.string(), limit: z.string().optional(), offset: z.string().optional(), status: z.nativeEnum(TestStepResultCreateStatusEnum).optional(), from: z.string().optional(), to: z.string().optional(), });
- src/index.ts:145-149 (registration)Registration of the 'get_results' tool in the MCP server's ListToolsRequestSchema response, specifying name, description, and JSON schema derived from Zod schema.{ name: 'get_results', description: 'Get all test run results for a project', inputSchema: zodToJsonSchema(GetResultsSchema), },
- src/index.ts:281-293 (handler)MCP CallToolRequestSchema handler dispatch case for 'get_results': validates input with schema, builds query filters, and delegates to the getResults implementation..with({ name: 'get_results' }, ({ arguments: args }) => { const parsedArgs = GetResultsSchema.parse(args); const filters = parsedArgs.status || parsedArgs.from || parsedArgs.to ? `status=${parsedArgs.status || ''}&from=${parsedArgs.from || ''}&to=${parsedArgs.to || ''}` : undefined; return getResults([ parsedArgs.code, parsedArgs.limit, parsedArgs.offset, filters, ]); })