Page MenuHomePhabricator

Include translation test results in server response
Closed, ResolvedPublic

Description

A possible (test-driven-development-like) Web2Cit workflow is:

  1. Find a target URL that returns unexpected results in Citoid
  2. Confirm Web2Cit returns unexpected results as well
  3. Write a test for the target URL
  4. Write a template for the target URL until all domain tests pass. Write patterns if needed.
  5. Repeat

To support this workflow, we need a way to check how test results change after making configuration changes. This will be supported by the Web2Cit-Editor.

In the meantime, consider providing an additional endpoint (maybe just the debug endpoint T301748 with a search query ?tests) that shows these results.

Event Timeline

The test endpoint should have the option to: (1) show test results for a single target URL, and (2) show test results for all tests configured for a domain.

diegodlh renamed this task from Consider providing an additional "tests" endpoint to Include translation test results in server response.Apr 13 2022, 8:27 PM
diegodlh moved this task from Backlog to To do on the Web2Cit-Server board.
diegodlh moved this task from To do to Doing on the Web2Cit-Server board.

Instead of having a separate /test/ endpoint, include tests (expected outputs and test scores) along with translation outputs, and provide a query string parameter (see T305750) to either enable or disable including these tests.

We now have a placeholder for expected outputs in our result tables.

diegodlh claimed this task.
diegodlh moved this task from To do to Done on the Web2Cit-Server board.

Implemented on the translation-tests branch.