Details
Assignee
UnassignedUnassignedReporter
Varun JavalkarVarun JavalkarPriority
P3Development Team
FolijetRelease
Not ScheduledTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Varun Javalkar
Varun JavalkarPriority
Development Team
Folijet
Release
Not Scheduled
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created April 7, 2021 at 6:43 PM
Updated August 10, 2023 at 6:35 AM
Purpose/Overview:
During data import testing in PTF, we came up with a PostgreSQL query that will give all instanceId that does not have any holdings and items. This will be helpful to troubleshoot and create holdings and items for those instances with missing holdings and items.
This is just an example - below Postgresql query gives all instanceIds that does not have any holdings and items. This Postgresql query will be different for different job profiles.
My point is we should show these failed instances in UI logs which will be helpful in troubleshooting.
So in data import, when you select the filename which open logs in UI, should first show all failed instance with details as to why it failed. This feature will be helpful when loading large data import jobs such as 50K, 100K or 500K. That way, we don't have to find a needle in a haystack.
Acceptance criteria:
Data import UI log shows failed instance, holdings, items after data import job fails or completes with an error