-
Notifications
You must be signed in to change notification settings - Fork 45
Open
Labels
comp-springIssue is related to Spring projects supportIssue is related to Spring projects supportcomp-uiImprovements of plugin UI appearence and functionalityImprovements of plugin UI appearence and functionalityctg-enhancementNew feature, improvement or change requestNew feature, improvement or change requestspec-uxIssue is influencing user experienceIssue is influencing user experience
Description
Description
With Spring Unit and Integration tests UI has become too complex.
When Spring configuration
is selected, Mocking strategy
, Mock static methods
and Parameterized tests
controls are just informative and thus useless.
Expected behavior
TBD
- Investigate IntelliJ platform guidelines in search for best practices
Environment
IntelliJ IDEA 2023.1+
Potential alternatives
If project has Spring dependencies:
- Display dialog. Which type of test generation to use: Spring-specific or Java regular?
- Display action dialog with set of controls based on user choice.
For Spring based choice:Spring configuration
,Tests type
andActive profile(s)
For Java regular choice:Mocking strategy
,Mock static methods
andParameterized tests
That will simplify controls behavior.
Context
Currently if Spring dependencies are found, there appear 3 additional controls and there is logic to set Mocking strategy
, Mock static methods
and Parameterized tests
based on them.
Metadata
Metadata
Assignees
Labels
comp-springIssue is related to Spring projects supportIssue is related to Spring projects supportcomp-uiImprovements of plugin UI appearence and functionalityImprovements of plugin UI appearence and functionalityctg-enhancementNew feature, improvement or change requestNew feature, improvement or change requestspec-uxIssue is influencing user experienceIssue is influencing user experience
Type
Projects
Status
Todo