For the complete documentation index, see llms.txt. This page is also available as Markdown.

Count Project Test Cases

Description

Returns the number of test cases allocated to one AttackForge project. A project test case is a per-project instance of a library test case - it carries the testing state for that project: status, who it is assigned_to, which project scope items it covers, and whether it is locked. Use this when you only need a total - call find_project_testcases to retrieve the test cases themselves.

The caller must have access to the project's test cases; if not, an access-denied error is returned. See Test Cases and Methodology.

How To Enable

  1. Go to Users

  2. Select the user you would like to provide access to this tool

  3. Click on Access > MCP

  4. Click on Add Tools

  5. Select the tool count_project_testcases and click Add

Example Prompts

  • How many test cases are in project X?

  • How many test cases in project X are still not tested?

  • How many test cases are assigned to me on this project?

  • How many test cases in project X are unassigned?

  • How many test cases have been locked on this project?

Parameters

Parameter
Type
Required
Description

project_id

string

Yes

Id (24-hex) of the project whose test cases you want to count. Source: find_projects. The caller must have access to this project's test cases.

filter

object

No

A MongoDB-style filter. Supported fields are listed below.

Supported filter fields:

Field
Type / Values

id

ObjectId('<24 hex>') - the project test case id

created, modified

ISO-8601 datetime

status

one of 'Tested', 'Not Tested', 'Testing In Progress', 'Not Applicable'

assigned_to

ObjectId('<24 hex>') - the user the test case is assigned to

locked

boolean - supports $eq, $ne and $exists only

custom_fields

array of { key: string, value: string or array }

testcase_id

ObjectId('<24 hex>') - the parent library test case

user_id

ObjectId('<24 hex>')

Disallowed inside filter: project_id (use the parameter), and title, details, code, tags, sort_order, testsuite_id - these live on the parent library test case. To narrow by them, call find_testcases first and filter on the resulting testcase_id values.

Example Response

Last updated