Description

We added Python and JavaScript tests generation.

UI

To expand UtBot UI functionality we added next new modules:

• utbot-ui-common module:

  • in this module we used no language-specific IntelliJ SDK API
  • this gradle module contains common to all languages logic formutbot-intellij to avoid cyclic dependencies in project building
  • LanguageAssistant access to dynamically connect API from language dependent modules. Now exists Python, JS and JVM assistants.
  • BaseTestModel - parent class forPythonTestModel,JsTestModel andGenerateTestModel. This class was created becauseGenerateTestModel use JVM specific functions

• utbot-intellij-python,utbot-intellij-js modules:
  These modules contain language-specific implementations ofLanguageAssistans,BaseTestModel,DialogWindow and other classes.

Code generation

Previous solution of the problem with different logic for different languages (Java and Kotlin) in code generation which usedCodegenLanguage should not be used with new languages.

Our solution suggest to use abstract classCgLanguageAssistant which contains information about code generation language (e.g.languageKeywords, getters forCgNameGenerator,CgMethodConstructor...). In language-specific modules we can create implementations with language-specific logic.

We did not deleteCodegenLanguage.JAVA andCodegenLanguage.Kotln, but it is possible if our solution will be approved.
Base implementation forJava andKotlin we have already added inorg.utbot.framework.plugin.api.

Analogically we addedLanguageTestFrameworkManager to organize test framework logic for different languages.

CLI

Modulesutbot-cli-python andutbot-cli-js contain command line generation and run tests interface for Python and JavaScript. They depends onutbot-cli module.

Main language modules:

Modulesutbot-python andutbot-js can be used from IntelliJ-plugin and from CLI. They contain independent of PSI logic, for example, languageUtModels, fuzzing and code generation declarated there.

Fixes#1197

Type of Change

Please delete options that are not relevant.

• Refactoring (typos and non-functional changes)
• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Automated Testing

We have code examples for testing how UtBot works:

• utbot-python/samples/
  There are scriptgenerate_test_samples.sh for automatic run generation test from cli andrun_test_samples.sh for run generated tests.
• utbot-js/samples/

Manual Scenario

• Open Python-, JavaScript-project in IDEA and run UtBot plugin.
• Or, generate and run test with CLI.

Checklist (remove irrelevant options):

• The change followed the style guidelines of the UTBot project
• Self-review of the code is passed
• The change contains enough commentaries, particularly in hard-to-understand areas
• New documentation is provided or existed one is altered
• No new warnings
• New tests have been added
• All tests pass locally with my changes