2.2.3.5 release notes

 2.2.3.5

  • Issue 2190 - Winter '23 introduces a new System.Assert class as an alternative to the traditional System.System.assert* methods. This created a slight resolution ambiguity for IC2 between the System.assert() method and the new System.Assert type which has been addressed in this build.
  • Issue 2191 - Added support for context-based execution of all Apex unit tests under a selected directory. Now if you right-click on a directory that contains at least one Apex unit test class, you will be offered the standard options for unit test execution and run configuration management. This will result in an Apex unit test run configuration based on that directory which, when executed, will find all Apex unit tests in that directory recursively and execute them. Just as with all other types of unit test run configurations, these may be managed under version control.
  • Issue 2192 - Enhanced Apex code coverage directory annotation in the Project view so that coverage information can be displayed on all directories under the corresponding source root (default) or content root. The content root option allows you to view coverage aggregates across source roots in projects with more fine-grained source root configuration. This is configured in Illuminated Cloud > Configure Application > Unit Tests and Code Coverage as Code Coverage > Annotate code coverage on directories beneath [source roots | content roots].
  • Fixed an issue with the recent File contents verification code inspection enhancement to flag top-level type names that exceed the allowed name length which would also flag valid long trigger names.