works on Utest Website as Software Testing
تفاصيل العمل
Description
1. What is the product about?
Candy Crush Saga is a free-to-play match-three puzzle video game released by King on April 12, 2012, for Facebook; other versions for iOS, Android, Windows Phone, and Windows 10 followed.
2. Who is the typical end user / target audience?
Mobile users who are interested in gaming - of all ages
3. What does the target audience use the application for? Why do they use it?
Target audience use the application to leisure and gaming
4. Which main business objective(s) does the customer have (e.g. increase revenue, decrease cost, strengthen brand.) How can crowd testing help?
Increase speed of launch - Increase the customer base of those that play the games by testing in the language the games are present in to ensure quicker launch times for the teams
Increase game quality - Build up teams of testers who have experience of the playing games in the King portfolio and become more knowledgeable on game workflows and usability
Increase efficiency - Ensure a more efficient approach to testing the games with core teams of native speakers validating new strings and features on releases in order to capture more issues
5. What are examples of bugs that were of high value for this client? And why?
The character creation don't save the creation for croatian league
NO - MT -CCS_CC_APP_vote_popular: Missing Translation
In Scope
Welcome to this localization cycle for King
In this round we are testing Candy Crush Saga
=== IMPORTANT INFORMATION - MAKE SURE TO CHECK IT ===
This is a quick overview through the overview items. Under no circumstances skip reading through the whole - it's just to give you a quick peek of the most important areas of the instructions.
You HAVE TO check the strings in the game - you are not supposed to check the string solely in the spreadsheet. Anyone caught not testing in the game will be removed from the team.
If you can't trigger a string, check with the TTL team for any tips or tricks. Please block a string only after confirming with the TTL there's no way to trigger it
You have to be a NATIVE SPEAKER to test the strings
Native means you were born in that country and lived there for a considerable amount of time (15-18 years or more)
Each string failed MUST be reported (as long as the overview instructions are followed)
SCOPE
We are NOT testing the actual translation - this is a PSEUDOLOCALIZATION where we are testing quickly created to ensure there no UI issues.
Ensure to review out of scope area to not report anything that is not in the cycle interest
How to test:
Use this sheet as your guide - https://platform.utest.co...
It contains a lot of strings which you can find in the game
Trigger the areas like teams, seasons, vending machine etc and perform exploratory testing for the strings you can find in the game (even those which are NOT listed in the spreadsheet)
Report any VALID bug you find (see the instructions below as well as Out of Scope section). If you see some potential issue, check out if the string is listed in the sheet and then ensure the bug you are going to report is proper one (see out of scope section as well as example of good bugs sheet which is listed below). In case the string is not seen on the sheet - please use use your judgement whether report that or not.
Once you report a bug, go to the sheet (https://platform.utest.co... and mark it as 'Yes' and leave a comment as well as bug ID
DO NOT overwrite other testers name, you may add your name next to other tester's name if you find an issue for already checked string
If you wish, feel free to update the sheet and mark strings which you were able to find even if no bugs are found for those. Thanks!
Test the builds and check:
Flipped UI issues:
UI elements of the game (like progress bars, tables, tiles ets) that are flipped incorrectly
We have set up a form for reporting any suspicious activities and issues with builds / strings / cycle. Please use the form below to speed up the process of fixing those up:
Devices to test on
Mobiles ONLY - phones & tablets
Android & iOS
Test in portrait mode
Out of Scope
OUT OF SCOPE
Anything EXCEPT flipped parts of the UI like tablets etc
Strings that needs to be flipped (LTR instead of RTL for Arabic language)
Placeholder texts
Truncations
Technical strings (e.g. '[saga_cr_title]' instead of proper Arabic text)
English text instead of target language or English mixed with target language
Translation issues - The actual translations, some of these texts will make no sense or will surely be wrong as we added random texts sometimes this is a PSEUDOLOCALIZATION cycle and translations ARE NOT correct on purpose
Duplicates - If several bugs are found on the same screen, please do not report more than one issue per report. Instead please raise one report per bug/issue found, as this makes it easier to keep track of the total amount.
Some words will not be translated to Arabic (own names of some characters, events etc) - DO NOT report them
Uppercase instead of lowercase, or vice-versa: do not report unless it doesn’t match the spreadsheet
Anything outside the game (e.g. Google Play store pages etc)
Problems with installation of the game or other technical problems not related with the flipped UI / flipped texts in the game
Setup Instructions
Download the build from the URLs below
iOS - https://app-store.king.co...
Android 32-bit - https://app-store.king.co...
Android 64-bit - https://app-store.king.co...
Issue Reporting Instructions
HOW TO REPORT A BUG
Your report should be written in English and contain:
Your language
Description of your action performed
Description of the error you found
Screenshot(s) / video
Please type the text you see on the screenshot.
Please type the English original for this text (if known, text should be typed in full).
Please type the name of strings triggered (if known).
Please suggest a fix or type a text which will fix the issue (text should be typed in full)
Please give a strong/elaborate reasoning for the suggested change
Area where the bug was found
Bugs must be fully detailed and steps to reproduce should start from the beginning and detail all steps you took to reproduce error, not just error itself, numbered 1,2,3 etc.
Bug Title Naming Convention
E.g. Language - TO - Key Name: Description of Issue
E.g. Language - OG - Key Name: Description of Issue
TO - Trunctions & overlap
OG - Other/General
IT - Incorrect translation
MT - Missing translation
For example:
AR - OG - metagame_house_zone38: The text needs to be flipped
AR - TO - All texts in Settings screen are truncated - this kind of issue can be reported for screens / areas where all texts need to be flipped
The key names can be found in the Coverage sheet.
Bug Report Custom Fields - Language field
One of the custom fields to fill out is the Language field. This must be populated with one of the exact strings for your particular language.
It must correspond with the language you are reporting the issue for, including the correct locale!
Make sure you choose the correct language string from the dropdown menu!
LOCALIZATION RULES - IMPORTANT
1. DO NOT report issues for languages that you are not a native speaker of.
2. Rules when reporting issues:
Example: Poor translation of sentence can be reported separately if for different languages
Example: Missing translation and translations that are generic across all languages (like missing characters) should be reported once and the +1 Feature used for other languages
Example: Truncation, overlap of sentence should be reported once and the +1 Feature used for other languages
Reproduction assistance
Please use the +1 Confirm button on any issue you see raised that you can reproduce.
You should use this and use comments if you can recreate the same issue in another language that would be considered a duplicate if raised.