/
Bug Bash - 2024-09 Translation Release [de, hi, pa, ml]

Bug Bash - 2024-09 Translation Release [de, hi, pa, ml]

Bug Bash Fundamentals

Orientation meeting:
Video link
Passcode:

What is a bug bash?

It’s a collaborative event where the whole team, no matter what their role is, comes together to try to “break” the application in creative ways ahead of a release. The goal is to find as many bugs as possible in a short period of time, and since every person in the team will have their own unique perspective and use the application in different ways, there are better chances of uncovering issues, defining how severe they are and if needed fixing them ahead of the release. It’s also a great opportunity for people to spend some time familiarizing themselves with the application and putting themselves in the shoes of one of our users. And last but not least, breaking things can actually be fun! By doing bug bashes often, we’re cultivating a blame-free culture where we take bugs as a chance to bond as a team, learn and improve.

How do I participate?

  1. If you’re willing to collaborate with this bug bash, please write your name down in the Participants section. If possible add details about what language(s) you’re using when testing the app, as well as which user role(s) you’re logging in as. This will help us know if there are any languages or roles not currently being covered by anyone.

  2. Read through the scope of what we’re testing in the Scope section. The scope will usually be defined based on what kind of changes we are pushing out on the upcoming release and it’s a guidance on which are the main things to keep an eye on. That being said, if you do find any bugs that are unrelated to the scope, feel free to report them anyway.

  3. If the bug bash is done synchronously, there’ll be a meeting where we all come together and test at the same time with a time box. If it’s done asynchronously, we’ll aim to have the session open for enough time that people in different timezones are able to participate. In that case, feel free to participate whenever you can and have the time and to time box depending on what your schedule looks like. Everything helps, so even if you only have limited time to test, you might discover something that nobody else has found before. Information on the timing of the meeting or asynchronous session can be found in the Session details section

What do I do if I find a bug?

First off, congratulations on finding it! To report the bug, head over to the Bugs section and add a new row in the table. The row should include your name and a brief description of the bug, on the Details field please add as much information as possible. Please provide reproduction steps and expected/actual behavior, and if you have the time, screenshots or video recordings of what you encountered will be extremely helpful. You don’t need to fill out the Pre-existing, Priority or Blocker fields as those will be filled out once the session is over.

If you spot a bug and you see someone else has already reported it and it’s on the table, you can go ahead and just add your name to the “Also seen by” column to mark that the bug is encountered frequently, without having to write down all the details again.

What happens after the bug bash?

Once the bug bash session is over, the team will go over the list of bugs that were found and prioritize them. For each issue, we’ll try to answer these three questions:

  • Was this bug caused by the change we’re aiming to push out on this release, or does it currently exist in production?

  • How severe and how frequent is this bug, or in other words, what’s the priority for fixing it?

  • Should this bug block the upcoming release?

No matter the result, if the issue found is something we’d like to fix eventually, we’ll create the corresponding ticket in Jira and add it to the Backlog. If we come to the conclusion that one or more bugs are actually blocking the upcoming release, we’ll add those tickets to the current sprint and give them the highest priority. If no bugs are found that are blocking, we’ll proceed with the release process as normal and work on the reported issues in future sprints depending on their priority.

Participants

Name

Language(s)

User role(s)

Name

Language(s)

User role(s)

E.g.: @Denis Dovganyuk

E.g.: Spanish, English

E.g.: Farm Owner, Farm Worker

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Scope

This bug bash will be focused on testing Language release. The purpose of the patch is to add 4 new languages to the LiteFarm app: Hindi, Punjabi, German and Malayalam.

[Jira links]
https://lite-farm.atlassian.net/browse/LF-4398

The primary focus of this session will be a comprehensive review of various workflows within the LiteFarm app. Here's how we'll structure the testing:

  1. Verify Absence of "Missing" Tags:

    • Ensure that all content within the app displays correctly, with no placeholder text or “Missing” tags across all workflows and screens.

  2. Language Localization Check:

    • Validate that all strings are correctly translated and displayed in the selected LiteFarm language.

    • Cross-check that no text appears in the wrong language or reverts to the default language.

  3. Functional Testing:

    • Ensure each feature and functionality within the app works as expected.

    • Test various user actions, such as data entry, navigation, and form submission, ensuring no unexpected behavior.

  4. Visual and UI Testing:

    • Confirm that there are no visual glitches or layout issues (e.g., misaligned buttons, overlapping elements, broken images).

    • Test the responsiveness of the app across different screen sizes and devices, ensuring the UI remains intact and visually consistent.

In addition to these key points, we’ll document any bugs or inconsistencies and provide feedback to the development team to ensure a smooth user experience across the board.

[Link to appropriate sections of the Sanity Script here if there are any] Sanity Script

 

Known Issues

 

Session Details

Bug Reports

Reporter

Description

Details

Pre-existing?

Priority

Needs native speaker translation

Blocker?

Also seen by

Reporter

Description

Details

Pre-existing?

Priority

Needs native speaker translation

Blocker?

Also seen by

E.g.: @Anto Sgarlatta

E.g.: The SSO button is not clickable

E.g.:

Repro steps

  1. Access LiteFarm logged out

  2. Click on the Google SSO button

Expected

Should navigate to the Google page to choose an account

Actual

Nothing happens

Screenshots/videos

 

E.g.: No

E.g.: High

 

E.g.: Yes

E.g. @Joyce Sato-Reinhold

@Joyce Sato-Reinhold

Days of the week component (repeat crop plan) is not understandable in Punjabi or Hindi

Hindi:

(I think those are the full name for each day of the week?)

Punjabi:

That spells out “es, em, tee, dublyoo, …” (i.e. S, M, T, W … ) in Gurmukhi. It needs to instead have something like ਸੋਮ, ਮੰਗਲ, ਬੁੱਧ, ਸ਼ੁੱਕਰ (Mon, Tues, Wed, Fri …)

I don’t know if a one-character version of days of the week exists in Hindi, Punjabi, or Malayalam. If not, the component needs adjustment to accommodate more letters.

 

Google search / AI for shortest version

Kinda – we can default to English letters if necessary

 

@Joyce Sato-Reinhold

Year calendar (crop plan flow) does not exist in Hindi, Punjabi, or Malayalam

(This has a ticket https://lite-farm.atlassian.net/browse/LF-4422 and I would like to get an assessment of priority)

This year calendar does not have support for hi/pa/ml and will appear in English in those languages (ignore the top string, that’s a different bug)

 

Low

Probably not, unless we are going to implement a package that requires adding locales manually (not recommend)

No

 

@Joyce Sato-Reinhold

Never translated string on crop flow

In languages that do have a translated year calendar (all but three listed above), we have had date strings that always appeared in English:

Yes

Medium

No

No

 

@Joyce Sato-Reinhold

Gender dropdown (which, by default, has “prefer not to say” selected) does not update when changing language

 

 

Yes

Medium

No

Yes

@Denis Dovganyuk
Also saw this

@Denis Dovganyuk

The information is cut of on the mobile device once the user enters the crop plan the name of which consists more than 7 letters

Here I will just link this ticket: https://lite-farm.atlassian.net/browse/LF-4367

(Note from Joyce: I’m worried this will be more obvious now that we have more crops with long names in new languages)

 Yes

 High

 

For now we can truncate or reduce font or go to two lines

No. Code.

 Yes

 @Joyce Sato-Reinhold

 

 

Please discuss with @Loic Sans when he returns

 @Denis Dovganyuk

The date in the main page is not displayed correctly on Chrome desktop in the Punjabi language

 

Repro steps

  1. Open the website LiteFarm

  2. Login with your personal account

  3. Navigate to the My Profile > My Information

  4. Change the language to Punjabi

  5. Navigate to the main page.

 

Actual Result:

The date is displayed in a bit strange way.
Happens only on the laptop. On mobile device looks great

Expected Result:

The information should be displayed in the Punjabi language.

(Additional notes - Joyce)
Also occurs here in tasks:

And is specific to Chrome desktop, Punjabi. Does not occur in Firefox, Safari, or Chrome mobile. Does not happen in other new languages. This is the native Intl.DateTimeFormat() that is not able to return the month correctly in this specific browser, which is why I suspect we will not be able to address this.

 

 

No.

Probably unfixable without package-importing refactor. Would like to discuss need.

 No

 @Joyce Sato-Reinhold


 @Denis Dovganyuk

 During the repeating of the crop plan one of the strings is written in English ( Happens in all languages)

 Repro steps

  1. Open the website LiteFarm

  2. Login with your personal account

  3. Navigate to the My Profile > My Information

  4. Change the language to Punjabi

  5. Navigate to the crops.

  6. Repeat an already existing crop.

Expected Result:

All the strings should be displayed on the current LiteFarm Language.

(Additional notes - Joyce):
This part of the flow is also controlled by rrule:


Translations are needed. I’m also not sure the way the package sets up the translation is going to work very well in our new languages, but we should be able to get something passable.

This PR adds the needed translation strings to what is tracked in CrowdIn:

https://lite-farm.atlassian.net/browse/LF-4399

 

 High

No – use AI

 

@Divya Chayanam will AI Hindi

@Joyce Sato-Reinhold will AI Punjabi

 

@David Trapp will AI German

 

Malayalam at end if nec

 Yes

 @Joyce Sato-Reinhold

 @Denis Dovganyuk

 The information of the crop plan is cropped( happens on Hindi language)

 

Repro steps

  1. Open the website LiteFarm

  2. Login with your personal account

  3. Navigate to the My Profile > My Information

  4. Change the language to Hindi

  5. Navigate to the Farm map section

  6. Click on the Area that has some planned crop plans.

 

Actual Result:

The information is cropped. And it is not readable.

 

Expected Result:

The text should be readeable.


Additional notes:

  • English text of that banner is planned

  • We could adjust the styles or look for a shorter way to indicate the same meaning in Hindi

  • @Denis Dovganyuk for me it fits on that same map > crops view, but maybe that’s something arbitrary like system font?



 

 Medium

 

Devs – please just remove the badge in all languages

No

 Yes

 @Loic Sans please check our solution when you return

@Denis Dovganyuk

The export of the Certification documents fails if the LiteFarm language is the new one.

Repro steps

  1. Open the website LiteFarm

  2. Login with your personal account

  3. Navigate to the My Profile > My Information

  4. Change the language to Hindi

  5. Navigate to the Certifications

  6. Export your documents


Actual Result:

The Сertification documents are not send to your email address.

 

Expected Result:

User should recieve his certification documentation.

 

 

no

 

 

@Denis Dovganyuk

The website layout in German language is cut off on the mobile device.

  1. Open the website LiteFarm using your mobile device

  2. Login with your personal account

  3. Navigate to the My Profile > My Information

  4. Change the language to German

  5. Navigate to the crops page.

 

Actual Result:

The layout of the crops page is a bit cut off. The user needs to manually change the zoom of the page, however once he does this and navigates all over the flows, the zoom won’t be saved.


Expected Result:
The page is not cut off

 

 

 

High (especially crop page)

No

Yes

 

@Joyce Sato-Reinhold

Untranslated crop name

Pomegranate

 

 

 

No – @Joyce Sato-Reinhold will AI this [DONE]

No

 

@David Trapp

Out of date string in PT, ES, FR – please remove in all languages

This is no longer true

 

Yes

Low

 

No

 

@Joyce Sato-Reinhold

Last language in the dropdown is not visible without scrolling

Also @Divya Chayanam do you have a preference for how the languages are ordered (we can also check with @Loic Sans when he returns)

Ordering Option 1:
Old Litefarm languages, then new LiteFarm langagues

Ordering Option 2:
All languages using roman alphabet, alphabetical by language code, then all other languages, alphabetical by language code



But any order is possible (e.g. Malayalam at top of Indic languages for our research partners; it’s up to us)

@Anto Sgarlatta suggests dropdown opening up

 

 

 

 

 

@Joyce Sato-Reinhold

Transliteration of LiteFarm is not consistent in Malayalam

LiteFarm was once transliterated as

ലൈറ്റ്‌ഫാമു (“litefarm” according to ChatGPT and Google Translate) - 1 string


but usually as
ലൈറ്റ്‌ഫോം (“litefoam / litefom”) - 8 strings

or

ലൈറ്റ്‌ഫോമിലേക്ക് - 3 strings; I think this is the form for “to LiteFarm” and says “litefomilekku”


This is a word that should have a consistency across the translated app. Of the two, the top one should be preferred, no?

OR

@Denis Dovganyuk suggests it could perhaps just appear in English characters “LiteFarm” as a brand name (although I don’t know how that would work with attaching the correct suffixes as above)

No