[Junit] Too many constraints error

[codingsoo]

Hi,

When a swagger file is big, it generates too many constraints error.

I think this is because Junit has limited constraints pool. I tried this project: https://github.com/devgateway/ocvn

[codingsoo]

To solve this problem, I think the number of Junit tests should be limited or the test files should be splitted.

[kerrykimbrough]

Sorry, I don't understand what you mean by "too many constraints error". Can you explain? Better yet, can you show a reproducible test case?

[codingsoo]

tcases_ocvn.zip
Hi, thank you for reply.

The constant pool includes numbers, strings, method names, field names, class names, references to classes and methods. The limit is 65536, so it needs to be split when it exceeds it. I attached the file which is generated by Tcases for the OCVN REST API web service.

• timeout was added by me.

[kerrykimbrough]

The best solution is to control the size of the generated test by controlling the amount of the API that is covered. For example, you might consider generating separate tests for each API path.

# Generate tests only for operations on /myResource
tcases-api-test -P /myResource myApiSpec.json

Or if using Maven:

# Generate tests only for operations on /myResource
mvn tcases:api-test -Dpaths=/myResource -Dproject=myApiSpec

[codingsoo]

Hi,

First of all, thank you for your proposed solution. While I agree with you that exercising each API path should work, unfortunately there are too many end-points in the swagger file (https://github.com/codingsoo/temp_swagger/blob/main/ocvn.json), which would make the proposed solution not suitable for my case.

Would it be possible to add a feature for exercising a fat swagger file's every API path? I would greatly appreciate any help regarding this issue. Thank you very much for all the help!

[kerrykimbrough]

I'm considering adding an option to automatically generate a separate test class for each API path. Would that resolve your problem?

[codingsoo]

Sure! I really appreciate it!

[kerrykimbrough]

@codingsoo, unless you have any further requests, I plan to produce a new release containing the 2 new features you suggested.

[codingsoo]

Thank you very much! I really like this project.

[kerrykimbrough]

Fixed by PR #173

[kerrykimbrough]

@codingsoo, FYI, a new release 3.6.0 containing your suggested features is now available

[codingsoo]

I will use 3.6.0! Thank you very much:) Hope you have a wonderful day.