XIO

xWire

Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.

Katalon Community - Latest posts

Latest posts

True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)

Based on the issues reported in this thread, these two questions may help narrow down the cause: Can one Jira work item type be both a requirement type and a defect type in the integration? Does the 400 on issuetypes/metadata mean no defect type was stored, or could it have another cause?

True Platform issues

Monty_Bagati: The executions runs are also not reliable and they get stuck most of the times without any reason. And the worst part is that if the execution gets stuck then the True platform does generate any error log for us to investigate about what was the root cause .

True Platform issues

Monty_Bagati: True Paltform is unable to reason on a simple thing while automating a basic website like Cura health. It is not able to automate any website unless you spoonfeed and hand held every aspect even the minor things in the requirement Yes, I completely agree. Another challenge is that the AI-powered “Analyze” button is not very accurate at the moment. Most of the time (around 95-96%), it labels the issue as an automation bug, even when the real cause lies something else. I created a…

True Platform issues

Some critical issues in True Platform True Paltform is unable to reason on a simple thing while automating a basic website like Cura health. It is not able to automate any website unless you spoonfeed and hand held every aspect even the minor things in the requirement True platform execution is extremely slow , it almost takes 4x more time than it would take using any other open library tool It fails to reason and self heal the steps (Requirement description ) that are described in the…

True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)

There is one more integration issue that has come up recently. If i want to sync all work items as requirements and select everything as below , i wont be able to integrate JIRA with true I have to either uncheck the Bug Mapping from Step 2 or uncheck some of the issue types from requirement fielsa nd value mapping and then check it in defect fields and value mapping

True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)

Environment: Katalon True Platform (beta), instance true-platform-beta-4.katalon.io, project AutoGen (ID 3567815). Jira Cloud integration, project Team Fire (key FB), connection ID 103674, integration ID 127823. Problem: In Executions > History > a failed test run > Tests tab > Report Defect > Create New Defect, the Issue Type shows “Bug” but the form never displays any fields. The text “Select an issue to display fields here” stays on screen, and the Create button stays disabled. I can still…

Authen in web when use Desktop testing

As far as I know, Chrome forwards a new link to the running instance using the same user-data-dir. A link fired by the OS default-browser handler normally goes to the default profile, while the debug instance runs from C:\katalon\chrome-profile, so the login URL may open in a different Chrome than the one Katalon is attached to. Recent Chrome versions also ignore --remote-debugging-port on the default profile, so you can’t just use that. Worth confirming which window the link actually opens in.…

Unable to Inspect Jetpack Compose testTag Elements in Katalon Mobile Spy

I will add couple of points First make sure the change is actually in the build you’re spying on. testTagsAsResourceId is only available in newer Compose versions, so if your dev can’t use it, upgrade Compose first. After adding the flag, ship a new build, reinstall the app and refresh the page source in Mobile Spy.