Skip to main content

Backend Error Handling

This test is about submissions within the GCC backend, which are in an error state. This has been observed, for example, when trying to send a submission with instructions containing characters from the Supplementary Multilingual Plane (SMP).

Alternative Scenario: The given manual test steps "mock" this state, as we cannot ensure that an error persists over time. If you want to test the real-life behavior, you may choose using the "default" rather than the "mock" type and instead of using mock.scenario, you may use the submissionInstruction.characterType setting. Set it to unicode and add some SMP characters to the instructions (thus, workflow notes), like for example, the dove emoji: 🕊.

Advantage: The advantage of the real-world scenario is, that you may also test, that a submission in an error state may still be canceled.

  • Connector Type: mock
  • Key Type: irrelevant

Quick Steps​

  1. Log in as Rick C.
  2. Use mock type.
  3. Set mock.scenario to submission-error.
  4. Start a translation of an article.
  5. Open the started workflow process.
  6. Expect a user-task "Download error" and accept it.
  7. Validate that a localized error message like "General submission failure" is shown.

Detailed Steps​

  1. Log in as Rick C.

  2. Open the GlobalLink settings /Settings/Options/Settings/Translation Services/GlobalLink

    1. type is set to mock
    2. mock.scenario is set to submission-error

  3. Start a translation for an article.

  4. Open the workflow in Workflow App via nagbar shown in the article.

  5. Wait until the current task is "Download error" and offered to you.

  6. Accept the task.

  7. Click the error issue information and see a "General submission failure."