MCP getTestStatus fails with Cannot read properties of null (reading 'toLowerCase')

App Feedback
,
1

Hello,

I managed to connect Codex to the MCP of my selfhosted instance of testiny v1.38.0 (c51d1ac62@HEAD)
I managed to create a few test cases, but when I tried to play with test runs, codex ran into an error when trying to list the tests runs. Here is the report it managed to extract.

Regards,

What is it about

The Testiny MCP tool getTestStatus fails when reading results from an existing test run. listTestCases and listTestRuns work for the same project.

Environment

Testiny MCP connector used through Codex, observed on 29 September 2026. MCP server version unknown. The run contains test cases with both passed and not-run results; the UI shows them as unassigned.

Steps to reproduce

  1. List the project’s cases with listTestCases({“project”:“”}).
  2. List its runs with listTestRuns({“project”:“”}).
  3. Call getTestStatus({“project”:“”,“testRunId”:}), without a status filter.
  4. Repeat with testCaseId set to a case marked as passed.

The error also occurs when identifying the project by its numeric ID or name.

Expected result

Return the test case results, step results and comments for the run or the selected case.

Actual result

Both getTestStatus calls fail. The call targeting a passed case fails too, so the issue does not appear limited to not-run results.

Error logs and/or visual proof

tool call failed for testiny/getTestStatus
Mcp error: -32603: Cannot read properties of null (reading ‘toLowerCase’)

setTestResultBatch and result comments were accepted, but this error prevents reading the results back. Project and run IDs can be provided privately for investigation.

3 Answers

3
2

Hi and welcome to the Testiny forum!

Thanks for the detailed report — we could reproduce the problem.

What happens
Every test result is stored through the built-in Result field. In your instance that field is not active for the project (or is disabled overall). In that state Testiny silently drops the result when it is written: setTestResultBatch reports success, but the test case is stored without any result. getTestStatus then fails on that empty result, which is the Cannot read properties of null (reading 'toLowerCase') error. This is a bug on our side: the built-in Result field should never be possible to deactivate, and a missing result should never make the MCP call fail.

How to fix it now

  1. As a tenant admin, re-activate the Result field for the project.
    • In the UI: open the project’s settings, go to the Custom fields tab and make sure Result is ticked as active.
    • Or via the REST API: call GET /api/v1/custom-field/all?visibleOnly=false and find the entry with "name": "result_status" and "is_builtin": true. Then send PUT /api/v1/custom-field with that field’s id and its unchanged options, except "visible": true and your project id added to "projectIds".
  2. Set the affected results again (e.g. re-run setTestResultBatch). Results written while the field was inactive were not stored and cannot be recovered.

After that, getTestStatus works again.
We will disallow deactivating the Result field with out next release and try to also fix organizations with that broken setting.

Best regards,
Alex

3

Hello, thanks for the fast reply.

I checked this morning the configuration of the project and indeed in the Fields view of the project properties (and not custom fields) the Result Status checkbox was unticked.

I don’t know how it happened and the agent states that it didn’t modify the project properties. The others existing projects have this checkbox ticked, so the problem was only on my new project.

The getTestStatus works again now.

Regards,

Thanks for the feedback!

 –
5

This is now fixed with the latest release Testiny v1.42.0.

Best regards,
Alex