True AI Tester Certification Progress Stuck at 90%
Hi, thank you so much for confirming this! I’m glad to know that sharing dashboards counts toward the certification progress. I’ll continue Thank you for your help and support!
Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.
Hi, thank you so much for confirming this! I’m glad to know that sharing dashboards counts toward the certification progress. I’ll continue Thank you for your help and support!
Hi @moonlayTech, quick update on this one. Our team has fixed this bug in Katalon Studio 11.6.0. Could you update to the latest version and run the request again with the DJPB CR profile? Let us know if you still see the error. Thanks @kazurayam and @arvind.choudhary for helping us reproduce it! Bella
1. Java compatibility mismatch (first screenshot) geh/data/ViewException was compiled for Java 25 (class file version 69.0), but the runtime executing Katalon supports up to Java 21 (65.0). That run is therefore not using Java 17. • Ask the owner of the JAR containing geh.data.ViewException to rebuild it for the supported execution runtime—e.g. Java 21 with --release 21 if it uses no newer APIs—and replace the incompatible JAR in the project. • Check Java from inside the running Katalon test,…
Hi Team, Good morning, While executing the script, I encountered an error. As part of the troubleshooting, I have already upgraded the Java version to Java 17. However, the issue still persists. Could you please help review the error and suggest the next steps for resolution?

While executing the script, I encountered an error. As part of the troubleshooting, I have already upgraded the Java version to Java 17. However, the issue still persists. Could you please help review the error and suggest the next steps for resolution?

Hi team, While executing the script, I encountered an error. As part of the troubleshooting, I have already upgraded the Java version to Java 17. However, the issue still persists. Could you please help review the error and suggest the next steps for resolution?

Hi Monty, thank you for sharing your feedback with us. We want to make sure we address this properly. Could you share a bit more about your specific use case for configuring the same work item type for both requirements and defect reports? Understanding your workflow will help us find the best solution for you.
I created a small utility for this tha would give recommendation and all details. Let me know if you need it and i will open source it

Hi, just checked and see that sharing dashboards does count. it updates your process. So please share more dashboard results with your team members or stakeholders. You will get the cert soon. @e41230243
are you able to access other links apart from katalon invitation?
Hi @qurzunta.kaab, thanks for the detailed report and the API evidence, it saves the team a lot of digging. I’ve logged this with our team as KSR-12493 (Jira). I’ll update this thread when I hear back on the defect issue type config and whether the missing Severity field plays a part.
I reproduced this on Katalon Studio 11.6.0 and measured where the time goes. Setup: one test suite with 4 short API test cases (one POST and a status check each). I ran it three times back to back, changing only the suite’s Execution Information. The public Petstore server returned HTTP 500, so the tests failed, but each test still made its one request, so the timing is valid. Setting Real time (run start to last process exit) Duration in Katalon’s JUnit_Report.xml Parallel off 28.0 s 9.5 s…

kazurayam: I found, that all test cases that use WebDriver are very resource-hungry(network, external browser processes, cpu, memory). Within a single PC, each of them demands instantly the full resources of my PC, consequently the resource contentions force the test cases to run effectively sequentially or evely slower. This makes sense to me, thanks for the explanation.
Thanks for the update @nghi.phan
to speed things up, could you take a screenshot of the invitation email or forward it to support@katalon.com? That way we can check which organization the invite came from.
hayaniamny.mohdkhair: the page keeps loading indefinitely and I am unable to access or join the organization. We are on it, will update you ASAP
Hi everyone, I accidentally created my own organization previously and became the owner. Recently, I received an invitation to join my company’s Katalon organization. However, when I click the invitation link, the page keeps loading indefinitely and I am unable to access or join the organization. I have also tried opening the organization URL directly but it remains stuck on the loading screen. Has anyone encountered this issue before? Would appreciate any advice on whether I need to remove my…

Thanks @anh.chu for your response. We would then wait for more updates related to true platform including the UI part.
Hi, I’d like to share the Analytics & Trends dashboard with you for review. Please let me know if you can access the dashboard successfully. Thank you! https://platform.katalon.com/share/NFTfzXvxTk
kindly share the requested details ASAP @e41230243
Hi @e41230243 it seems like a bug in tracking execution result sharing. I’m verifying with the team. In the meantime, could you try sharing dashboards instead?
Dear Akshay, A ticket has been created, I will share updates to you when we have any information.
akshay_sartabe: I believe the whole purpose of parallel execution within suite is to reduce the overall time, but … I agree with you. I don’t know how the recent versions of Katalon Studio implement the parallel execution of tests within a suite. I don’t know it at all. Previously in 2021, I tried to implement “concurrent execution of test cases” for my own. See my previous post: Run concurrent tests within a test suite - #3 by kazurayam While doing it, I found that concurrency does not promise…
Hmmm… i did not look closely into the timings… This does seems misleading now… as the longest suite took 52 seconds to run and total time shows 25 seconds. Seems like katalon is just showing the average. @nghi.phan this could easily break the trust if shown to some new users, maybe katalon should fix.
This looks odd. The log viewer tells us — the Test Suite Collection “TSC_metraAssist_API” finished in 25 seconds; and the Test Suite “TS_Digital_Auth”, which is a component of the TSC, finished in 31 seconds. How come a Test suite collection can finish faster than its component!? It’s ridiculous. There must be something cheating us. Possibly the log view lied; it took longer than 60, but pretended to be faster and reported 25seconds. I don’t trust this log view. Though I know that writing a…

akshay_sartabe: In this post, I’m highlighting the parallel execution of test cases within a specific test suite, the latest feature that Katalon has shipped. OK. I did not recognize your point correctly.
Could you message me a recording of the step you take to complete this requirement? This might be a tracking issue. @e41230243
Hi @Monty_Bagati. Thank you for taking the time to go through the product and giving us feedback! I do agree with the shortcomings you have noticed. What I can offer right now is some context and tease some upcoming changes. For why our agents don’t seem as “autonomous” as the normal coding agents, part of the design decision was focused more on explicit and reproducible behavior, especially for regulated customers, more than absolute “task achievement.” Additionally, our aim was to uplift…

However, In my case, The parallel execution of the Test Suite Collection has been helpful at least in the run that I’m executing. It looks like Katalon has improved since you post. For sequential execution of test suite collection - 2 mins For parallel execution of test suite collection - 25 seconds

@kazurayam I read your post, and those are mostly around the Test Suite collection. In this post, I’m highlighting the parallel execution of test cases within a specific test suite, the latest feature that Katalon has shipped. I’m assuming that the same (logic/explanation) would be applicable for the parallel execution within the test suite.