Skip to content

Mock static methods enables on every change of Test framework or Mocking strategy #2400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tyuldashev opened this issue Jul 11, 2023 · 1 comment · Fixed by #2403
Closed
Assignees
Labels
comp-ui Improvements of plugin UI appearence and functionality ctg-bug Issue is a bug spec-regression Regression

Comments

@tyuldashev
Copy link
Collaborator

Description
Whenever user changes value of Test framework or Mocking strategy Mock static methods becomes marked.

To Reproduce

  1. Install UnitTestBot plugin built from main in IntelliJ IDEA
  2. Open non-Spring project
  3. Invoke test generation dialog
  4. Set
    • Testing framework to Junit 5
    • Mocking strategy to Mock everything outside the class
    • Uncheck Mock static methods
  5. Change Testing framework to Junit 4 - note that Mock static methods has been checked
  6. Uncheck Mock static methods again
  7. Change Mocking strategy to Mock everything outside the package

Expected behavior
Mock static methods stays unchecked no matter what other fields changed.

Actual behavior
Mock static methods checked

Screenshots, logs
image

@tyuldashev tyuldashev added ctg-bug Issue is a bug comp-ui Improvements of plugin UI appearence and functionality spec-regression Regression labels Jul 11, 2023
@tyuldashev
Copy link
Collaborator Author

We may want to change expected behavior considering its usability in Spring projects. So let's discuss it with me and @alisevych before actual fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-ui Improvements of plugin UI appearence and functionality ctg-bug Issue is a bug spec-regression Regression
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants