Welcome, Guest Login

Support Center

Quality Assurance

Last Updated: Sep 08, 2017 10:29AM CEST
Quality Assurance is a feature built in both Memsource editors. It detects errors in translation by comparing source and target segments. Keep in mind that software Quality Assurance is not intended to replace human Reviewers, it helps translators to detect formal errors and improve the overall translation quality. The total amount of 27 checks covers all types of possible errors from spelling to tag issues or inconsistent terminology. The list of all check with a brief description can be found in our Memsource Cloud User Manual, Quality Assurance section.

QA Checks Setup

General settings can be accessed from your account Setup under Server Settings, Quality Assurance section. All selected checks will become a default QA setting for all project. If needed, these settings can be later adjusted on project level.

Running a QA

In the Editor, click on QA tab in the right bottom corner and then Run at the top. This will launch a QA check based on the project settings. For more details, click here.

It is possible to run QA across the whole file, or run QA partially, by selecting/unselecting specific types of checks from the drop-down menu next to the Run button.

Numbers in the QA pane does not represent numbers of segments. Simply click on the QA warning and you will be taken to the segment where the problem has been detected. If you spot any false warning, you can mark it as ignored. The warning will still be displayed in the QA pane but it will be greyed out. If you prefer, you can hide ignored warnings by ticking “Hide ignored” option.

QA warnings can be sorted by clicking on Type. You can also select multiple warnings and mark them as ignored at once.

Job's QA Status

Whenever a QA is launched for a job, the outcome of the QA is saved with the translation job. If you hover over jobs’ confirmed percentage, an info box appears that includes the QA status related to the job, for instance:
  • QA Warnings: Not launched
    • The QA has not been launched for this job.
  • QA Warnings: Incomplete
    • The QA has been launched only for part of a job (e.g. the user did not click the "Show more" link at the bottom of the QA warnings list).
    • Or the QA has been launched for the entire job but the job was later edited.
  • QA Warnings: 2 (1 ignored)
    • The QA has been launched and it includes a total of 2 warnings of which 1 was marked as ignored.

Issues which can be solved by running a proper QA

Export failed, File could not be generated error messages
There are missing or misplaced tags in your file. Run quality assurance with the following options selected in your project:
  • Tags & formatting
  • Tags - joined segments
  • No text between tags
Correct the problems identified by the quality assurance check and re-export.

Unresolved QA warnings error message
Project owners can prevent linguists from setting jobs with QA warnings to completed. As a linguist, you will see this error message when you try to set a job as completed without running QA or leaving some warnings unresolved.
Proceed like this:
  1. In Memsource editor click on the QA panel, located at the bottom right.
  2. Click on the Run button at the top.
  3. Resolve all QA warnings that get displayed; If you get a false warning, you can also ignore the warning by clicking on the "i" symbol.

Translation and Terminology inconsistencies
Inconsistent Translations check can detect following inconsistencies:
  • A segment with an identical source but a different target precedes the checked segment
  • A segment with an identical target but a different source precedes the checked segment
There is a feature in TB, where you can choose whether or not you want to have a certain term base included in QA. See details here.

Terminology check can detect following inconsistencies:
  • The terms in the source do not have a corresponding term translation in the target
  • A forbidden term is used for the translation (Forbidden terms in the source are ignored)
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found