![]() To learn more about test executing, you can refer to this document: Test Execution Overview.Īfter every execution, Katalon generates reports for troubleshooting and monitoring test activities. Katalon Runtime Engine is the test execution add-on of Katalon Studio for executing and scheduling tests in CI/CD pipeline or via the command-line interface. ![]() Katalon TestCloud is a cloud-based test execution environment equipped with the most common browsers and operating systems. Katalon TestCloud, Katalon Runtime Engine To learn more about organizing your tests, you can refer to this document: Introduction to organizing tests. ![]() Once done designing your tests, you can organize them in test suites or dynamic test suites in Katalon TestOps or Katalon Studio. To learn more about test creating, you can refer to this document: About Katalon Studio. In Katalon Studio, you can create, execute and view basic reports for your web, API, mobile, and desktop automated tests with both manual view and script view. To learn more about test planning, refer to this document: Introduction to test planning. Katalon also has a seamless integration with Jira to help manage releases and requirements. Although I have to agree that Scriptcase has increased my PHP development efficiency by orders of magnitude, the lack of documentation and other usability issues still frustrate me at times.In Katalon TestOps, you can plan tests with releases and builds, then schedule test runs. This is just one of the many scenarios where I wasted my time on understanding certain behaviour of Scriptcase, or trying to locate certain settings. This may or may not be Scriptcase bug, but in any case, the error message is not helpful at all here. If these errors are later corrected, the display fields will be populated again with the correct entries but the search field list still remains empty, causing the error Search fields undefined. Once errors are detected in the SQL query, the display fields will not be populated and will be filled with some default values while the search field list will be emptied. Another few hours of my development time has just been wasted on a trivial issue ….īut why would the search field list suddenly become empty for this grid? I guess it is because Scriptcase always tries to re-populate the display/search fields in the grid settings when the SQL query changes. ![]() ![]() So the solution is to simply go to the grid search settings and re-configure the fields to be searched. Although these fields are usually auto-generated, a quick check revealed that the search field configuration for this grid was indeed empty: Apparently for every Scriptcase grid, several sets of fields to be shown in list view mode (from the Grid > Edit Fields menu), in record detail view mode (from the Grid > Details > Setting menu), and in search mode (from the Search > Advanced Search/Quick Search/Dynamic Search > Select Fields menu) need to be defined. Where exactly is the Fields Positioning option and what was the cause of the error message in the first place?Īfter several more hours of trial and error, I found the solution. Or perhaps, it was meant for an older version of Scriptcase. So what is the issue? A Google search on the error message returned this thread as the only result containing a hint, The solution: grid_customers…Left:Search…Fields Positioning…middle:the ‘valami’ push right !!!. In other words, there seemed to be no problems with the grid. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |