Bug Bash Fundamentals

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

Scope

https://lite-farm.atlassian.net/browse/LF-4951
https://lite-farm.atlassian.net/browse/LF-4737
https://lite-farm.atlassian.net/browse/LF-4952
This bug bash will concentrate on testing the features included in the current scope, specifically the items shown above: Soil Amendment Products + Product Inventory (LF-4951), Ability to Edit Finished Tasks (LF-4737), and Market Integration (OFN) MVP1 (LF-4952).

Purpose of the Release:

• Soil Amendment Products + Product Inventory (LF-4951):
  This feature enables users to manage soil amendment products directly within their farm’s inventory. It improves tracking, organization, and visibility of available soil inputs, helping users maintain accurate records and streamline field preparation workflows.

• Ability to Edit Finished Tasks (LF-4737):
  This enhancement allows users to update or correct details on tasks that have already been marked as finished. It ensures greater accuracy in farm activity logs, supports better reporting, and provides flexibility when adjustments are needed after task completion.

• Market Integration (OFN) MVP1 (LF-4952):
  This feature introduces the initial phase of integrating with the Open Food Network (OFN), enabling farms to synchronize product and market information. It lays the groundwork for streamlined product listings, improved market visibility, and future e-commerce capabilities.

User Stories

Inventory Management – User Stories

As a LiteFarm user (Farm Manager, Farm Owner, Extension Officer ), I want to:

1. I want to navigate to the Inventory page so that I can view a complete list of all products available on the farm.

2. I want to create a new product from the Inventory page so that I can add new items to my farm’s product list whenever needed.

3. I want to delete a product that is no longer used or was created by mistake so that my inventory remains clean and accurate.

4. I want to duplicate an existing product so that I can quickly create similar items without re-entering all details.

5. I want to review and edit the information of a product so that I can keep product details accurate and up to date.

6. I want to be able to create the Soil Amendment task so that I can record my activity in the Farm.

7. I want to be able to complete/abandon/ delete Soil Amendment Task so that I can accordingly record my Farm activity.

8. I want to be able to filter and Search in the inventory table for a specific product.
   
   

As a LiteFarm User( Farm Worker ), I want to:

1. I want to navigate to the Inventory page so that I can view a complete list of all products available on the farm.

2. I want to create a new product from the Inventory page so that I can add new items to my farm’s product list whenever needed.

3. I want to duplicate an existing product so that I can quickly create similar items without re-entering all details.

4. I want to be able to create the Soil Amendment task so that I can record my activity in the Farm.

5. I want to be able to complete or Abandon Soil Amendment Task so that I can accordingly record my Farm activity.

6. I want to be able to complete/abandon/ delete Soil Amendment Task so that I can accordingly record my Farm activity.

As a LiteFarm user (Farm Manager, Farm Owner, Extension Officer), I want to:

1. Edit completed tasks

   • User Story: I want to edit an already completed task by clicking the “Fix it now” button.

   • Acceptance Criteria:

     • The “Fix it now” button is visible for tasks I have permission to edit.

     • Clicking it opens the task for editing.

2. Save re-completed task information

   • User Story: I want to make sure that all the information provided during re-completion is saved correctly.

   • Acceptance Criteria:

     • Changes made to the task are saved after submission.

     • Previous task data remains intact but is updated with new information.

3. Re-complete a task multiple times

   • User Story: I want to be able to re-complete a task that has already been re-completed.

   • Acceptance Criteria:

     • Tasks can be re-completed multiple times without errors.

     • Each re-completion creates a new revision record.

4. Restrict unauthorized re-completion

   • User Story: I want to make sure that I cannot re-complete tasks that don’t belong to me.

   • Acceptance Criteria:

     • Users cannot see the “Fix it now” button on tasks they don’t own or manage.

     • Attempting to access an unauthorized task shows a permission error.

5. Show revised by information

   • User Story: I want the system to display “Revised by [user_name]” after successfully re-completing a task.

   • Acceptance Criteria:

     • Task history shows the user who performed the latest re-completion.

     • The revised-by information is visible in the task detail view.

As a LiteFarm user (Farm Worker), I want to:

1. Restrict re-completion of completed tasks

   • User Story: I want to make sure I cannot re-complete a task that has already been completed, even if I am the assignee.

   • User Story: I want to make sure that am not able to open the link to re-complete the already completed task.

   • Acceptance Criteria:

     • “Fix it now” button is not visible for completed tasks.

     • Should be re - directed to the main page.

Market Directory – User Stories

As a LiteFarm user (Farm Manager, Farm Owner, Extension Officer), I want to:

1. Add my Market Directory information so that customers and partners can see details about my farm and the products I offer.

2. Edit my Market Directory information so that I can keep my farm’s public marketplace details accurate and up to date.

3. Publish my Market Directory information so that it becomes visible to buyers and other stakeholders on the platform.

As a LiteFarm user (Farm Worker), I want to:

1. Restrict re-completion of completed tasks

   • User Story: I want to make sure I cannot re-complete a task that has already been completed, even if I am the assignee.

   • User Story: I want to make sure that am not able to open the link to re-complete the already completed task.

   • Acceptance Criteria:

     • “Fix it now” button is not visible for completed tasks.

     • Should be re - directed to the main page.

Market Directory – User Stories

Known Issues

https://lite-farm.atlassian.net/browse/LF-4975
https://lite-farm.atlassian.net/browse/LF-5050

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

Session Details

Usability Suggestions:

This section is where you can add your suggestions for improvements for the UX that are not faulty behavior or bugs, but that we’ll take into accout for future iterations

Description	Reporter	Details	Pre-existing?	Priority	Also seen by

Description	Reporter	Details	Pre-existing?	Priority	Also seen by
E.g.: The Upload button is not clickable	E.g.: @Anto Sgarlatta	E.g.: Repro steps Access LiteFarm logged out 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. @Joyce Sato-Reinhold
https://lite-farm.atlassian.net/browse/LF-5057	@Denis Dovganyuk		Yes
Select’s disabled text colour doesn’t match other fields https://lite-farm.atlassian.net/browse/LF-4321	@Sayaka Ono	Repro steps Log in with a user who has created a farm. Select the farm the user created. Navigate to People (/people). Select the user. Observe the Role field. Expected The disabled text colour of the Role select matches the disabled text colour used for other fields. Actual The Role select displays a different disabled text colour. Screenshots/videos Open   Loïc has reviewed and the input disabled is correct; Select needs to be lightened; also see: https://www.figma.com/design/eMffC0h3JPlWtzNttxJpil/Litefarm-Updated?node-id=3112-38063&p=f&t=Ae2QB6OpA6n6p67r-0	Yes	Med	@Joyce Sato-Reinhold oh I also made an entry for this in a different form
No product selection for grains and othershttps://lite-farm.atlassian.net/browse/LF-5076	@Joyce Sato-Reinhold	As a farmer of grains there is no dropdown selection for my crop (only fruit, vegetable) Open   Categories: Herbs (e.g. cilantro ← under vegetable??) Nuts Fungi (under vegetable??) Grains (under dry alongside beans) Legumes / beans @Loic Sans ALSO ALPHABETIZE IT	No	High	@Divya Chayanam
Messed up gradient on consent screen makes unprofessional first impression https://lite-farm.atlassian.net/browse/LF-5078	@Joyce Sato-Reinhold	(I have had my eye on this for more than a year now, please may I fix it) Open Weird gradient above the “I Agree” that doesn’t match background colour Open	Yes		@Sayaka Ono
PNG a bit blurry on OFN tile https://lite-farm.atlassian.net/browse/LF-5079	@Joyce Sato-Reinhold	Open @Sayaka Ono is it from Figma? May I replace it with the SVG version? - Yes, it’s from Figma. Please go ahead! – JS
Although Supplier field is Optional, the leaf icon is displayed near it	@Denis Dovganyuk	Open
The Supplier column in the Product table is misaligned	@Sayaka Ono	/inventory Open   12px padding is being supplied by something		Med-Low	@Joyce Sato-Reinhold ick
Colour of the disabled text inconsistent between product fields	@Joyce Sato-Reinhold	I thought I harmonized these Dry/Liquid is darker than the others. Moisture content looks lighter. Open Also in this view Open
Products should probably be below the logo, not between logo and about?	https://lite-farm.atlassian.net/browse/LF-5081@Joyce Sato-Reinhold	Might have been my mistake originally, or might have been a difference between two Figma screens in terms of which comes first (logo or about); products was placed under “about” (following most recent Figma) but that only makes sense if “About” follows “Logo”… I would recommend the order About Logo Products (note: follows OFN a bit too this way) Products definitely last   Logo / About About / Logo Products Open		Med (easy fix)
The order of fields in the consented to share list does not match the form order or categorizationhttps://lite-farm.atlassian.net/browse/LF-5085	@Joyce Sato-Reinhold	Form headings are: Farm identity Farm representative Farm store contact Online Presence   Consented to share headings are: Farm profile (both “Farm Identity” and “Farm store contact” Contact (= “Farm representative”) Products and services Online presence Open   Either the summary, the form headings (if we like the addition of “Products and services” as a category), or both should be edited so that they are harmonized Headings can stay, except contact → Farm representative Re-order fields in order of the form Product and services can stay as is (subheading of consent but not form)
Contact (shared but not published) should use the Private badge	@Joyce Sato-Reinholdhttps://lite-farm.atlassian.net/browse/LF-5082	This is DEFINITELY my mistake! @Loic Sans I think I misunderstood what you were saying about this – I thought you were suggesting recycling the wording from the “Private” in the form above – but now I'm thinking you were thinking to recycle the badge itself?? i.e. not Open but like this? Open
Ability to open feedback form from beta badge only happens on first navigation	@Joyce Sato-Reinhold	Opening feedback form more might be a more important call to action than the link to the “You can learn more about beta here”? Text is a also a little long for a dropdown (good in the modal) Open Call to action “Send us feedback” only happens once: Open		If easy, add feedback button same as the spotlight model
Should type of support be pre-selected when we open the feedback form?	@Joyce Sato-Reinhold	I’m actually not sure what the best type of support would be – maybe “request a feature” for the marketplace suggestion (nice to have), and “other” for the beta badge ← nothing pre-selected for beta badge I’m not sure and the user might not know what’s the best either Open			@Denis Dovganyuk Also was thinking about that….
Is there is a need to add a “Beta” badge near the Market Directory Tab or Even near the “Farm Settings” tab ???	@Denis Dovganyuk	Open   JS: Relatedly, but opposite – I’m wondering if we should remove the beta from animals (to have just one to focus on)! L: geographically limited so not a good thing to highlight right now. Animals is still in beta