Skip to content

Handle empty testcase values in results#543

Merged
matsduf merged 1 commit into
zonemaster:developfrom
tbleckert:handle-empty-testcase
May 27, 2026
Merged

Handle empty testcase values in results#543
matsduf merged 1 commit into
zonemaster:developfrom
tbleckert:handle-empty-testcase

Conversation

@tbleckert

Copy link
Copy Markdown
Contributor

Purpose

This PR fixes rendering of result entries where the backend returns an empty testcase value.

Context

Fixes #541

The reported timeout result is one example of this response shape: the backend can return a valid result entry with testcase: "". The GUI previously failed to display that entry correctly.

Changes

  • Treat empty testcase values as Unspecified when grouping results.
  • Make niceName() tolerate empty input safely.
  • Add FR26 e2e coverage for a result response containing an empty testcase.
  • Add a mocked empty-testcase-response result fixture for the e2e test.

How to test this PR

Run:

npm run e2e -- e2e/FR26.e2e-spec.ts

Or manually by testing a domain that results in a timeout.

@matsduf matsduf added this to the v2026.1 milestone May 18, 2026
@matsduf matsduf added V-Patch Versioning: The change gives an update of patch in version. RC-Fixes Release category: Fixes. labels May 18, 2026
@tgreenx tgreenx changed the base branch from master to develop May 19, 2026 08:00
tgreenx
tgreenx previously approved these changes May 19, 2026
@tgreenx tgreenx dismissed their stale review May 19, 2026 15:22

@tbleckert Thanks for this, LGTM! Could you just rebase this PR on top of latest develop branch so that CI passes?

@tbleckert tbleckert force-pushed the handle-empty-testcase branch from 1470f30 to e006df9 Compare May 20, 2026 08:49
@tbleckert

Copy link
Copy Markdown
Contributor Author

@tgreenx Done!

@matsduf matsduf requested a review from tgreenx May 20, 2026 09:11

@matsduf matsduf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks fine after update. To trigger timeout I had to lower the value in backend_config.ini. The "test zone" xp.cn was too quick today.

@marc-vanderwal

Copy link
Copy Markdown
Contributor

Looks good to me as well. On my test environment where I lowered the timeout to 60 seconds, testing xp.cn now displays correctly:

image

@matsduf matsduf merged commit 6135e38 into zonemaster:develop May 27, 2026
1 check passed
@marc-vanderwal marc-vanderwal added the S-ReleaseTested Status: The PR has been successfully tested in release testing label Jun 16, 2026
@marc-vanderwal

Copy link
Copy Markdown
Contributor

Successfully tested for the upcoming 2026.1 release. The test run with npm run e2e -- e2e/FR26.e2e-spec.ts succeeds, and when testing with a slow zone and a lower timeout in Backend, I get a proper error in GUI that looks like the screenshot I’ve posted before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

RC-Fixes Release category: Fixes. S-ReleaseTested Status: The PR has been successfully tested in release testing V-Patch Versioning: The change gives an update of patch in version.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Regression: New GUI breaks when test is aborted due to timeout

4 participants