Skip to main content
Gain Insights from the Languages Report
Aaron Collier avatar
Written by Aaron Collier
Updated over 3 weeks ago

Get a clear overview of the distribution and usage of languages in all testing tasks in a single place with the Languages report. Track key indicators to determine if they are sending any signals that require action or further investigation.

Find the report in the Testlio Platform under Reports > Coverage > Languages. You can filter the data for a specific date range and/or specific workspaces.

The Languages report brings indicators tracking key metrics related to language diversity, task distribution, and time allocation, enabling teams to evaluate language-specific testing coverage and identify areas requiring additional linguistic resources. This report is valuable for understanding language-specific contributions to testing efforts and ensuring inclusivity and comprehensive coverage across multilingual projects.

The Languages report in the Testlio platform showing key indicators with example data.

Indicator

What It Tracks

What Signals It Might Bring

Total Language Tasks

The total number of tasks started in different languages. Automatically compares with the number during the prior period.

This indicator reflects the overall volume of activity. It's a great place for an overview of where the workspace is with available testers and languages, helping to track current language coverage and availability.

Unique Languages

The number of distinct languages represented in testing. Automatically compares with the number during the prior period.

This metric offers insight into the diversity of linguistic coverage. It is a good place to start comparing the languages requested and those currently in the system. It helps the team quickly identify any gaps in language coverage and ensure that the testing aligns with client requirements.

Average Tasks per Language

The average number of tasks for each language. Automatically compares with the average during the prior period.

This metric provides a measure of how tasks are distributed across languages. Review how tasks are distributed across languages.

  • If certain languages are under-tested, redistribute tasks to ensure a balanced testing effort.

Tasks by Language vs. Unique Languages

A visual comparison of the task volume for specific languages and the number of distinct languages over time.

Monitor language testing trends and see if the number of languages aligns with the task volume.

  • If certain languages have consistently higher volume, reassess the scope to ensure they’re adequately covered.

Tasks by Language

The total number of tasks started in each language.

This metric enables a focused view of language activity distribution. Identify which languages are receiving the most tasks. If scope changes or additional languages are requested, adjust resources to meet those needs.

Hours by Language

The total number of testing hours spent for each language.

This metric provides insight into effort allocation. Compare task volume to the total hours spent per language.

  • If certain languages use more time, allocate resources to maintain balanced testing across all languages.

Run by Language

The total number of test runs associated with each language.

This metric highlights the extent of language usage in testing efforts. Examine the frequency of test runs for each language.

  • If a language is getting fewer runs but many tasks, ensure it’s tested thoroughly by adjusting the number of test runs.

Did this answer your question?