Feature #33236
openStatic Package Unit Testing and Bug Fixing
Added by Muhammed Jaseem P 2 months ago. Updated about 2 months ago.
90%
Updated by Jabeel Roshan P 2 months ago
- Status changed from Assigned to In Progress
Updated by Jabeel Roshan P 2 months ago
- % Done changed from 0 to 100
Completed unit testing for the static package and fixed bugs.
Updated by Muhammed Jaseem P 2 months ago
- Due date changed from 02/10/2026 to 02/12/2026
Updated by Jabeel Roshan P 2 months ago
- Status changed from In Progress to Fixed not Tested
- % Done changed from 90 to 100
Today I completed the unit testing for the Static Packages module and fixed the bugs in it.
Updated by Jabeel Roshan P 2 months ago
I’m currently working on unit testing for the static package and have fixed a few bugs. I also faced some confusion while integrating the date selection feature, which I will complete in the coming days.
Updated by Jabeel Roshan P about 2 months ago
- Status changed from Fixed not Tested to In Progress
- % Done changed from 100 to 90
I fixed the bug on the Static Package Details page. As per the API team’s suggestion, the static package date selection calendar should be enabled for all pages, and I have implemented that.
For the action buttons, I am checking the flags isEnquiryOnly, isEnquiry, and canBook. Only when these values become true, the Book Now and/or Enquiry buttons should be visible.
For the Pax type selection UI, I am following the same condition as the web version. The Adult/Child selection dropdown card is shown only when both isBasedOnPackageTotalPrice and isPackageBasedOnPlanner are false.
Currently, all button-related flags are coming as false from the API, so the buttons are not visible. I have added a support task for the API team to verify and update these values.
Updated by Jabeel Roshan P about 2 months ago
Fixed the button issues using proper condition checks. If both isEnquiry and canBook are false, no buttons are shown, and if either or both become true, the UI displays the relevant button(s) accordingly. If isEnquiryOnly is true, only the Enquiry button is displayed. Also handled the scenario where all three conditions become false, the user to get stuck on the details screen user can't proceed to further. Additionally, the UI was updated as per the Figma design and alignment issues were corrected.
Updated by Jabeel Roshan P about 2 months ago
- Status changed from In Progress to Fixed not Tested
- % Done changed from 90 to 100
Completed unit testing and bug fixing in the Static Package module. Today, I fixed the issue in Static package where the payment URL was empty or returned "NoUrl" by showing an error screen with the message “Payment Failed” and a Try Again button that routes the user back to the Home screen.
Updated by Jabeel Roshan P about 2 months ago
- Status changed from Fixed not Tested to In Progress
- % Done changed from 100 to 90
Today, I fixed the date selection container issue on the Static Package Details screen where the date picker was not opening. During debugging, I identified that the validFrom and validTo values were causing a crash due to a date format error on a few specific devices, and I have resolved that issue. Additionally, I completed the key implementation for Google Sign-In on iOS for social media login, similar to the previous projects using Firebase Authentication.
Updated by Jabeel Roshan P about 2 months ago
After reviewing the module, i identified an issue with the total price calculation.
The total amount on the payment screen does not match the total amount on the ticket screen.
On the payment screen, we manually calculate the total amount by summing all available components.
However, on the ticket screen, we directly fetch the total amount and fare details from the API.
The total amounts are mismatched.