Skip to content

Testing of UI checklist 2.0 #954

Closed
Closed
@tyuldashev

Description

@tyuldashev

UI plugin checklist - copy from #475

Install plugin

Make the following checks for IntelliJ, Maven, Gradle projects with different JDK 8/11

Open dialog

  • Open the utbot-sample/src/main/java/org/utbot/examples/algorithms/ArraysQuickSort.java file
  • From Project view. Right-click on one class, select Create tests with UTBot... => Dialog is opened. All non-private methods from class are listed and selected
  • From code. Open context menu, select Generate..., select Create tests with UTBot... => Dialog is opened
  • Shortcut. Cursor on the class and outside all methods, press Alt+Shift+U => all class methods are selected
  • Shortcut. Cursor on/inside one method, press Alt+Shift+U => correct method is selected
  • Shortcut. Not working from build.gradle file, Java class file in test sources root, resources, etc.
  • Context menu item is disabled for --||--

Dialog. Members

  • From Project view. Right-click on a package with several classes, select Create tests with UTBot... => Dialog is opened. All classes from package are listed and selected
  • From Project view. Select several classes, right-click, select Create tests with UTBot... => Dialog is opened. Selected classes are listed and selected
  • From Project view. Right-click on one class, select Create tests with UTBot... => Dialog is opened. All methods of the class are listed and selected (except private)
  • Create a public class with 4 different methods: private, without access modifier, protected, public. Open UTBot test generation for the class => all methods except private are in list.
  • Make the class package-private (remove "public") => check the same

Dialog. Settings

Verify tests are generated with all these options

  • Dialog. Test source root is defaulted (if test source root is set in project)
  • Dialog. Test source root (if no test sources root set in project) => suggests to create a new one (red) - create => verify created
  • Dialog. Test framework => is defaulted to JUnit5 // change request:
    UI. Test framework. Set default to the existing one in project #499
  • Dialog. Test framework (for project with JDK 8) => JUnit4, JUnit5 only // change request:
    Install appropriate version of TestNg in user project depending on JDK version #309
  • Dialog. Test framework (for project with JDK 11) => JUnit4, JUnit5, TestNG (not existing in project dependencies must have red text "(will be installed)")
  • Dialog. Mock strategy => 1) Do not mock, 2) Mock package environment, 3) Mock class environment
  • Dialog. Mock strategy "No mocks" is selected => Mock static is set to "No static mocking" and disabled
  • Dialog. Mock strategy - select 2) and 3) options => Mock static options: 1) No static mocking, 2) Mockito static mocking.
  • Dialog. Mock strategy (for a project without Mockito in dependencies) => 2), 3) options have red text "(will be installed)"
  • Dialog. Timeout for class => default to 60 sec, only natural numbers can be saved, up and down arrows work
  • Dialog. Timeout for class => minimize, check on ArrayQuickSort or some other code with conditions and loops
  • Dialog. Parametrized test => 2 options: Not parametrized / Parametrized
  • Dialog. Parametrized test - select "Parametrized" => "No mocks" and "No static mocking" are chosen and both disabled
  • Dialog. Destination package. Check not present // change request:
    UI. IDEA plugin dialog. Hide UI possibility to change destination package #488

SARIF report

  • Dialog. Set "Not parametrized" , generate tests => SARIF report is generated into resources folder
  • do this for a single class => check place, package, file
  • do this for several classes in different packages
  • Dialog. Set "Parametrized" , generate tests => no SARIF report is generated

File -> Settings... -> UTBot

  • Force static mocking. Add a class...
  • Code analysis. Select Simplest, Deepest, 1st mark from left, 1st mark from right, somewhere in the middle...

Metadata

Metadata

Assignees

Labels

ctg-qaIssue is related to QA process

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions