Method code too large

[kazurayam]

@Ilya_Novak

Recently I realised that splitting a large TestCase source into smaller pieces and re-assembling them using WebUI.callTestCase() does NOT help for working around the “Method code too large” constraint. I edited my previous post at Method code too large - #18 by kazurayam

---

@Russ_Thomas suggested an effective approach to decrease the size of method at Method code too large - #5 by Russ_Thomas

Take your common test code, turn it into Classes/Methods and store them under Keywords

I agree with his suggestion.

---

@Ilya_Novak

why would the error appear in a later but not earlier version of Katalon.

I guess, simply because the version of Katalon Studio is different. The newer the version of a software product is, it introduces more features that could benefit users, and at the same time the binaries tend to get fat internally.

For example see:

Method code too large In Katalon v5.4

Hi there, Upon checking again in our latest version, the root cause is 5.4 introduce Test Listeners which will append the current size of a test case. However, we can’t adjust it accordingly and we also observe that your current test script is quite long, which is really not a good practice in the future. If we try to adjust test script’s size to be adaptive with yours, then in the future there will be someone write a longer test case than you. In this case it is not a really good solution, and…

---

@Ilya_Novak

is there at least some way to know how close a test case is to hitting the JVM limited code length of 65536, other than running it, that is?

Sincerely, I do not know. I have never heard of such thing.