You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 21, 2025. It is now read-only.
Hi all! I am encountering a bug and I might have also diagnosed the cause.
Whenever I try to generate tests with tkltest-unit -cf tkltest_config.toml -vb generate evosuite or tkltest-unit -cf tkltest_config.toml -vb generate randoop, the generation fails with "The command line is too long." error.
As far as I understood, the issue is very clear: in tackle-test-generator-cli\tkltest\unit\generate\generate_standalone.py, the script calls a Java command to invoke Randoop or Evosuite. In case the complete classpath is too long (>8192 chars), windows refuses to execute the command.
This is a hard limit of Windows, hence the solution would be to implement in generate_standalone.py whatever you implemented in the core jar, when ctd-amplified generates the basic tests with randoop/evosuite.
Hi all! I am encountering a bug and I might have also diagnosed the cause.
Whenever I try to generate tests with
tkltest-unit -cf tkltest_config.toml -vb generate evosuiteortkltest-unit -cf tkltest_config.toml -vb generate randoop, the generation fails with "The command line is too long." error.As far as I understood, the issue is very clear: in
tackle-test-generator-cli\tkltest\unit\generate\generate_standalone.py, the script calls a Java command to invoke Randoop or Evosuite. In case the complete classpath is too long (>8192 chars), windows refuses to execute the command.This is a hard limit of Windows, hence the solution would be to implement in
generate_standalone.pywhatever you implemented in thecorejar, when ctd-amplified generates the basic tests with randoop/evosuite.