Is there a way to extract a profile into a csv?

Your list looks leggit.
There is only one problem.
It is opened on your Git account.
To make them more visible to the development team, better rise them at:

I am not willing to do so. The list is inteded just for my own use. It is an index of my outstanding posts that I made since years ago.

All the issues in my list are based on the posts in the Katalon Forum. So I expect (but not verified) that those issues are already acknowledged by the devs. I hope that they have listed those issues in their list.

Their issues list is too long for me. I’m not willing to be concerned about it.

Since you are a veteran on this comunity, I hope you realised up to now that, some devs may look sometime into the forum, but it is not a guarantee.
And they will never look at your personal list :smile:
I learned this with various issues I raised here and there, so I learned to not bother anymore.
If they consider it, fine, if not, also fine.

To my shame, I never rised a Git issue. I was tempted to do it, but looking at the pending list, aside of the fact you already observed, is way too long, I can see there are still opened issues not valid anymore.

So, yeah, I understand your position… somehow

Can we add one for “auto-formatting in Script View can be toggled OFF”

Can we add one for

who are we?

I found the below link that parses an XML file so you can make a cvs file of your profiles. There is no out of box KS method, but you can create a Keyword that allows you to extend or simplify your testing.

How to read XML file in Java - (DOM Parser) - Mkyong.com

Maybe like:

This just prints the Profile contents into the Console tab so you can copy and paste to create your csv file, but it shouldn’t be hard to Google a Java programming, save-to-file routine. I just used a static file pathway, but you can feed your routine any pathway you want.

import javax.xml.XMLConstants
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.ParserConfigurationException;

import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NamedNodeMap
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.xml.sax.SAXException;

//	String pathway = "U:/Mike/Katalon/Profiles/uat.glbl";
	
	@Keyword
	public void createCSVFromXML(String pathway) {
	
		  // Instantiate the Factory
		  DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
		  
		  String myOutLine = ""
		  
		  try {
	
			  // optional, but recommended
			  // process XML securely, avoid attacks like XML External Entities (XXE)
			  dbf.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true);
	
			  // parse XML file
			  DocumentBuilder db = dbf.newDocumentBuilder();
	
			  Document doc = db.parse(new File(pathway));
	
			  // optional, but recommended
			  // http://stackoverflow.com/questions/13786607/normalization-in-dom-parsing-with-java-how-does-it-work
			  doc.getDocumentElement().normalize();
	
//			  System.out.println("Root Element :" + doc.getDocumentElement().getNodeName());
//			  System.out.println("------");
	
			  // get <globalvariableentity>
			  NodeList list = doc.getElementsByTagName("GlobalVariableEntity");
		  
			  for (int temp = 0; temp < list.getLength(); temp++) {
	
				  Node node = list.item(temp);
	
				  if (node.getNodeType() == Node.ELEMENT_NODE) {
	
					  Element element = (Element) node;
	
					  // get the profile main attribute
					  String id = element.getAttribute("GlobalVariableEntity");
	
					  // get text				  
					  String desc = element.getElementsByTagName("description").item(0).getTextContent();
					  String initValue = element.getElementsByTagName("initValue").item(0).getTextContent();
					  String globalname = element.getElementsByTagName("name").item(0).getTextContent();

					  myOutLine = globalname;
					  myOutLine += ",";
					  if (initValue.contains(",")) {
						  myOutLine += '"' + initValue + '"';
					  } else {
						  myOutLine += initValue;
					  }
					  myOutLine += ",";
					  myOutLine += desc;
					  System.out.println(myOutLine)
				  }
			  }
	
		  } catch (ParserConfigurationException | SAXException | IOException e) {
			  e.printStackTrace();
		  }
	
	  }

Their list has the following issue since Jun 2020:

which is based on another post in the Katalon forum at Jan 2018.

Also there is another post similar to this

This is one of the issues outstanding long time. What’s the cause? I guess, Katalon Studio turns a script of Test Case in Script mode into Manual mode, then later it turns the script from the Manual mode back into the Script mode. Unfortunately the code transformation from the Manual mode to the Script mode seem to have some bugs. I guess there might be some technical issues in Groovy, Eclipse or Java which make the issue unable to fix. Especially I have a doubt that the Abstract Syntax Tree Transformation of the Groovy 2.4.x could have some bugs. As you may be aware, Katalon Studio uses very old version of Groovy, Eclipse, Java. If there is any problem in the base layer that blocks Katalon developers, they must starts with overhauling their product.

By the way, just recently @duyluong made a comment in another post in the Katalon forum:

He suggested that Katalon developers are trying to overhaul Katalon Studio at the moment. This must be a big news to us, Katalon users. But we all know, any changes at the base layer may cause new problems. Users should wait and see if the Katalon team could manage it.

Their issue list on GitHub has so many open issues. But why?

The GitHub repository GitHub - katalon-studio/katalon-studio is NOT the one on which Katalon developers work together to develop their product. It is just a download site. I guess, they have their own central repository, which is internal and closed, somewhere else. It’s OK, Katalon is a privately owned enterprise; they are not an open-source project.

So, possibly they are not interested in the issue list on GitHub very much.

Yes. An overhaul would be nice. I would think that Katalon would have concerns for losing market share to tools that pay more attention to their user base.

Feel free to open a feature request and wait for feedback.
I am tired of doing such and being ignored (and I have a strong feeling I am not the only one from the comunity in this regard)

I’m actually a little dismayed there is no staff response to any of the suggestions made in this thread. To me, calling something a “platform” without these facilities is stretching the meaning of the term beyond its accepted usage.

@vu.tran @albert.vu @mike.verinder @Coty

EDIT: I moved this thread to Feature Requests. Let’s see.

Hey Team,
If you submit a feature request or if you report an issue (bug). All of these are reviewed and prioritized by the product team for scoping into future releases. There’s a lot going on at Katalon, from new products and new features to yes, even bug fixes. Scoping these releases takes a quite crafty hand. While it might be comforting to share what is scoped in roadmap, the hesitation in sharing that information is simply sometimes things fall out of scope (for a number of reasons).
(That’s why you never see Apple fixes communicated out until the product is delivered)

That said. As I was reading the above threads I noticed the amazing job some of our community members are doing as it relates to sharing “how to links” and mentoring where they can. thank you all for caring and supporting each other. That’s what community is about.

2 Likes

Hi folks,

Thank you very much for your patience. I have raised a ticket to our product team and will inform you if there is any update or respond from their end.

Thanks :+1:

@mike.verinder Hi Mike,

Let me guess, you are either a new hire in Katalon company or an old member promoted to a certain management position.
My best guess will be Product Manager or Product Owner, altough I started to have some doubts that Katalon is using a certain Agile methodology … but this is just my opinion.

So you have started to take the pulse of the comunity by raising various topics here and there … to get a better understanding of the product and use-cases.
Which is not a bad thing.

As for your answers:

If you submit a feature request or if you report an issue (bug). All of these are reviewed and prioritized by the product team for scoping into future releases

  • Yeah right, we heard that many times

There’s a lot going on at Katalon, from new products and new features to yes, even bug fixes.

  • We are not stupid. We know there is a lot going on. We only doubt the focus is on the rights priorities, from our point of view
  • You may like to either re-phrase that, or take some action.
    Lack of visible feedback is the main concern for us, old members, and for new members too.
    Which can be read also like “Katalon is overhelmed and do not have a clear path”.
    AKA lack of proper management.

That said, welcome to the comunity!

Thanks for your feedback bionel.
A little about me. I’ve been leading Automation teams for a little over 20 years.
for the last 15 years, I’ve also have a small little Selenium User Group I created on Linkedin.
(we have around 190,000 members). The Katalon team knows I’ve always been a fan of Katalon and asked me to come into the Katalon family as the Chief Community Advocate.

Here’s a link to my Linkedin profile if you’d like to know more about me. Feel free to connect with me if you like :slight_smile:

(4) Mike Verinder | LinkedIn

Have a great day !

1 Like

Mr. Bionel,

I believe you’ve effectively made your point. It’s now time to let Katalon act. Continuing to berate the Katalon team accomplishes nothing.

Cheers!

Thanks for the intro Mike. A pleasure to make your acquaintance. It’s always good to know that there’s a user advocate on the tool vendor side.

Regards,

James Irlbeck

bionel is just enough, but thx :slight_smile:

I am sorry to say, but you will have a lot of bad stuff to deal with, with regards to Katalon actual image.
I wish you luck!
you have a lot of stuff to repair, so i already hear your scream.