Bug Bash Sensor/ Soil Sampling Task v2 release

Bug Bash Sensor/ Soil Sampling Task v2 release

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

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

@Duncan Brain

English

Farm Owner

@Joyce Sato-Reinhold

English, Punjabi

Farm Worker, Extension Officer

@Sayaka Ono

English

Farm Owner

@Divya Chayanam

English

Farm Owner

@Navdeep Dhammu

English, Punjabi

Farm Owner

@Denis Dovganyuk

French

Farm Owner, Farm Worker

 

 

 

 

 

 

 

 

 

Scope

https://lite-farm.atlassian.net/projects/LF/versions/10025/tab/release-report-all-issues

This bug bash will concentrate on testing the features introduced in the release which introduces an ability to add a Sensor from our Partner ESCI Ensemble Scientific https://lite-farm.atlassian.net/browse/LF-4684 and also creating a Soil Sampling Task. https://lite-farm.atlassian.net/browse/LF-4821

Purpose of the Release:

This update enables users to visualize Ensemble sensors deployed on their farm, along with real-time sensor readings. Additionally, it introduces the ability to create and assign soil sampling tasks with geolocated sampling points, improving precision and traceability in field data collection.

User Stories

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

  1. Review sensor information to ensure I have accurate data about my farm’s conditions.
    https://lite-farm.atlassian.net/browse/LF-4685

  2. Connect the Ensemble Scientific Add-on to integrate it with my farm’s monitoring system.
    https://lite-farm.atlassian.net/browse/LF-4683

  3. Have fields detected automatically if they overlap with a sensor, ensuring sensors are recognized as part of a field.
    https://lite-farm.atlassian.net/browse/LF-4688

  4. See the Ensemble Scientific sensor list displayed correctly once the Ensemble Add-on is connected. View the full sensor setup by clicking "See full sensor setup" in Settings or on the Add Sensors screen.
    https://lite-farm.atlassian.net/browse/LF-4685

  5. See individual sensors and sensor arrays displayed correctly on my farm map.
    https://lite-farm.atlassian.net/browse/LF-4685

  6. View readings from sensors by clicking on a sensor or sensor array on the farm map.
    https://lite-farm.atlassian.net/browse/LF-4686

  7. Disconnect the Ensemble Add-on when needed, removing it from my farm setup.
    https://lite-farm.atlassian.net/browse/LF-4687

  8. See an online/offline status badge for each Ensemble Scientific sensor, ensuring I know when a sensor is disconnected or not transmitting data.
    https://lite-farm.atlassian.net/browse/LF-4686

  9. Soil Sampling Enhancements: Users can now create geolocated soil sampling locations and directly create soil sampling tasks from the LiteFarm UI, simplifying the process and improving data collection accuracy. (Note: soil sample tasks can be created, viewed, and completed, but a soil sample results file cannot yet be associated with the task during completion)
    https://lite-farm.atlassian.net/browse/LF-4825|
    https://lite-farm.atlassian.net/browse/LF-4826

Known Issues

 

Session Details

Synchronous or asynchronous?

Asynchronous

When?

 

Where to test?

LiteFarm Beta

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

 

Reporter

Description

Details

Pre-existing?

Priority

Also seen by

 

Reporter

Description

Details

Pre-existing?

Priority

Also seen by

E.g.: @Anto Sgarlatta

E.g.: The Upload 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. @Joyce Sato-Reinhold

@Duncan Brain

Add task button still missing from locations tasks tab - where is that ticket again?

The add a task floating action button is still missing. I cannot find the ticket for it.

Yes

High

 

@Joyce Sato-Reinhold

Farm worker shown manage ESci Link, but doesn’t have that section in Farm Settings

Farm Worker sees link at the bottom of the sensor readings:

But doesn’t have the Addoon Partner section in Farm Settings, since they can’t edit / add Partners:

No

low

 

@Joyce Sato-Reinhold

Farm Worker cannot see the full list of Ensemble Sensors

Farm workers have no way to access the full list of sensors as the link to the full sensor list exists only in Addon Partner block of Farm Settings, and in Map > Add Location > Sensor.

Farm works have permissions to view the full list of sensors, but no access to either of the above.

 

read above issue

 

@Joyce Sato-Reinhold

Columns on Field Technology don’t line up

Offset of 2nd + 3rd column will vary depending on the letters in the ESID

 

 

 

 

@Sayaka Ono

 

When inviting a user, the page is reload

Repro steps

  1. Go to /people

  2. Click on the Invite User button

Expected

The “invite a user” form is displayed seamlessly.

Actual

The app refreshes. (The URL becomes /invite_user?. The button type is probably submit?)

Screenshots/videos

Yes

low

 

@Joyce Sato-Reinhold

Icon on the Field Technology tab indicates the ability to reload (maybe?), but it’s not clickable

Could totally be mistaken here, but the clock with arrow makes me think I can refresh the data by clicking on it; yet in fact icon is not clickable.

(This might be my misunderstanding/mis-reading of the icon)!

 

med

 

@Joyce Sato-Reinhold

Depth is displayed with a very high level of precision on imperial farms!

(cm → inches depth conversion is not rounding in KPI)

Correct in list view:

No

Joyce to be looking into this

 

@Divya Chayanam

Map zoom level when sensor added for first time

Ideally, the zoom level if we are looking at map with an intention to view added sensor, it should be zoomed in

Steps:

  1. Map > Add sensor > Add org id

  2. List of sensor > click ‘see on map’ for any sensor

Intended result

See the sensor in the map at a closer zoom level

Actual result

Map is quite zoomed out

 

Yes

Not an issue

 

@Joyce Sato-Reinhold

No way to get from ESci sensor list to sensor readings view

Including for prioritization because this was brought up by 2 out of 2 developers who didn’t work on the feature

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


Steps to reproduce:

  1. Navigate to the full list of Ensemble sensors

  2. Click on everything (ESID, record, see on map)… no way to get to sensor readings view

  3. (Need to return to farm map and click on an icon to get to sensor readings view)

 

Expected result:
“See on map” sensor icon or record in sensor list view table routes to that sensor’s data

No

High

 

@Sayaka Ono

Sensor list is sometimes empty for a while after connecting to Ensemble

It doesn't always happen, and I'm not sure when this happens. It took a few tries to capture this, but I've seen longer delays than what's shown in the recording.

 

No

low

 

@Divya Chayanam

Confusing user journey for soil sampling

Soil sampling flow, if initiated from tasks, can be improved.

Steps:

  1. Go to tasks > soil sampling

  2. You have no soil sampling locations ‘create new’. Clicking on that takes user to map.

  3. As a user, I am zooming in and clicking inside a field, expecting to be picking soil sampling locations. It is only after I click a field, I realize that I should have clicked on ‘add location’ again to add soil sample locations. Is it possible to fast forward one step and directly go to the next step of adding the location?

No

Not an issue

 

@Divya Chayanam

Map locations in a soil sampling task

It is good to show all locations in a soil sampling task, while making only sampling locations ‘selectable’. This helps a user understand which sampling locations belong to which field. Since there is no other association of a sampling location with a field, this step becomes important. Filter at selection, not at display.

No

High

 

Ensemble

Sensor KPIs + sensor readings tooltips should be to one decimal place, not two

Requested on call Monday June 9, 2025

 

med

 

Ensemble

Show irrigation system name somewhere on the sensor list, e.g. alongside profile (array) name

Requested on call Monday June 9, 2025

 

 

 

 

Regression testing

Regression testing ensures that recent code changes have not negatively impacted existing functionality. It involves testing key features to identify any unexpected issues and maintain software stability..

Farm Map

  • Ensure that users can still create areas on the farm map.

  • Ensure that users can still edit areas on the farm map.

Tasks

  • Ensure that users can still create tasks related to other areas.

  • Ensure that users can still complete, abandon, or delete tasks.

.

Bug Reports

 

Reporter

Description

Details

Pre-existing?

Priority

Blocker?

Also seen by

 

Reporter

Description

Details

Pre-existing?

Priority

Blocker?

Also seen by

E.g.: @Anto Sgarlatta

E.g.: The Save button is disabled.

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

@Denis Dovganyuk

400 Error When Saving Soil Sample Task with Decimal Value

Environment : Beta

Repro Steps
1. Open the website LiteFarm
2. Login with your personal account that has a “Soil Sample” location or create a “Soil Sample” location
3. Navigate to the tasks page
4. Create a Soil Sample task.
5. In the field “Number of samples per location” enter a decimal value ( for ex. 1.4)
6. Fill all the required fields
7. Click on the “Continue” button
8. Click on the Save button

 

Actual Result:
User receives a 400 error when attempting to save a Soil Sample task that includes a decimal value.

Expected Result:
Decimal values should not be allowed, in the field “Number of Samples per location”. Once you enter the value that has a decimal a field validation error should be displayed.

Video_250606160337.mp4

Content of 400 message:

 

No

Highest

Yes

@Joyce Sato-Reinhold I’ll add the 400 to the context. It’s a descriptive model validation error so backend could be left as is

@Denis Dovganyuk

Broken Mobile Layout During Soil Sampling Task Creation Flow

Steps to reproduce:

1. Open the website LiteFarm

  1. Login with your personal account that has a “Soil Sample” location or create a “Soil Sample” location

  2. Navigate to the tasks page

  3. Create a Soil Sample task.

Actual Result:

The website layout breaks or becomes misaligned when the user initiates the Soil Sampling task creation flow on a mobile device.

Expected Result:

The layout should remain responsive and properly formatted throughout the Soil Sampling task creation flow on mobile devices.

Screenshot_20250606_180248_Chrome.jpg

 

No

Low

No

 

@Duncan Brain

Is this usability?

Soil water content graph not discernible for North | Sensor array

Screenshot 2025-06-06 at 10.19.14 AM.png

Also full year for temperature and SWC:

Screenshot 2025-06-06 at 12.28.40 PM.png



No

Low- medium

No

 

@Duncan Brain

Render lag/flicker for irrigation tab and soil sample task type tab.

Thought I fixed but still present…

Go to task type selection page, or field with irrigation tab for the first time. See the new tiles or tabs pop in a half second later.

No

Low

No

@Denis Dovganyuk Saw that as well.

@Duncan Brain

Adding an image to the animal batch overlays on top of default image

Screenshot 2025-06-06 at 10.06.16 AM.png

 

No

Low

No