Taking long time while Moving test cases, objects and renaming moving folders.

Moving test cases, objects and renaming moving folders taking too long time in Katalon studio

2 Likes

I guess, your KS did not finish moving or renaming something. KS hanged. You had to terminate it, didn’t you?

I know Katalon Studio is buggy in moving/renaming testcases, testobjects and folders. :bomb:

See the following previous posts as evidence:

I am not surpised to hear you got a new problem in Katalon Studio while you moved/renamed something. Katalon dev team seems to me not keen on fixing this sort of primitive bugs. They seem to be too busy adding great features like AI-….

My advice

You should not move/rename anything in Katalon Studio. :sunglasses: Seriously. I am not joking.

Instead, you should create a new Test Case with new name, and copy&paste the source code from the old to the new. Then you can safely remove the old one. This procedure is safe.

If you desperately need to move/rename things, before doing it, you should apply the version control system git to take local backups of your project frequently in case KS breaks your project due to bugs. Provided you have applied git, you have a chance to salvage your project out of corruption.

3 Likes

Hi @vachaitanya,
If you are not ready or are unable to use ‘GIT Version Control’ then you can archive/backup your project by using 7-Zip. **7-Zip is free software with open source.

You should always backup your project before doing any Object/Folder/Other refactoring.

Windows 11 (other) steps to backup your Katalon Studio project:

  1. Install 7-Zip from https://www.7-zip.org
  2. Right-click on your Katalon Studio project (e.g., KatDemo).
  3. For Windows 11 systems, click on “Show more options”.
  4. Click on 7-Zip > Add to “KatDemo.zip”.
  5. Once completed double-click on “KatDemo.zip” twice to view the results.
1 Like

@vachaitanya

I have a question to you.

How many Test Objects do you have in your project?
How many Test Cases do you have in your project?

If you have hundredes of them, then Katalon Studio will take long time to process them when you move/rename one of them.

My 2nd advice: You should minimuze the number of Test Objects in the Object Repository. You should not leave unused Test Objects there. You should NOT use the Web Recording tool and the Spy tool, which tends to make the Object Repository folder untidy.

You should minimuze the number of Test Cases as well.

1 Like

Hi @kazurayam

My project nearly 800+ test cases and related objects is available.

Thanka

1 Like

Then you need to be very patient for waiting long while moving/renaming test cases and test objects.

The only countermeasure will be decreasing the number of files as test case and test object.

I guess that you created 800+ Test Cases using Katalon Studio’s Web Recording tool which produced mass of duplicating Test Cases and Test Objects. I guess, you would be able to refactor the project. You would be able to support the same range of usecases with less number of parameterizerd scripts and non-duplicating TestObjects. The refacoring will be very tough, though.

1 Like

I have never created a project with 800+ test cases.

I would be gratefull if you measure how long it takes to move/rename one of 800+ Test Cases/Test Objects and report the result here. I want to to know a practical figure — 80 secs, 800 secs or 8000 secss.

If the figure is remarkable, many users will support you if you raise an request to Katalon for improvment.

1 Like

Hi @kazurayam

Its taking nearly 5 min sometimes more than 5 min.

1 Like

If you have 800+ test cases , then its okay and what is your system config?

|Processor|Intel(R) Core™ i5-8365U CPU @ 1.60GHz 1.90 GHz|
|Installed RAM|16.0 GB (15.9 GB usable)|
|System type|64-bit operating system, x64-based processor|
|Pen and touch|No pen or touch input is available for this display|

1 Like

your system config is good.
Please clean your temp data from local system and also remove unnecessary reports from Katalon project, try once again.

5 min = 300 secs for 800 test cases; 0.375 sec per one test case.

This looks fair enough to me. Not very remarkable, I think. :stuck_out_tongue_winking_eye:

Simply you have too many test cases in a project. Therefore you have to be patient.

1 Like