Illuminated Cloud Announcements

2.3.1.4 (hotfix) This is effectively  2.3.1.3  with a hotfix for the customer-identified deployment issue described below. Issue 2570  - Fixed an issue that would result in  Check Only  (aka, "Dry Run") deployments actually updating the requested metadata in source format projects. This was due to the  sfdx  command's  -c  argument not being properly migrated to the corresponding  sf  command's  --dry-run  argument in the recent update to use the newer command set.

  2.3.1.3 I've posted a  demonstration video  detailing all of the recent Apex unit testing and code coverage enhancements including those described below. Issue 822  - Implemented another round of improvements around execution of dependent Apex unit tests. Now most Apex unit test run configuration types can be optionally configured as  Changed Only  which will execute only the Apex unit test classes from the run configuration that are either themselves changed or are (transitive) dependents of changed production (i.e., non-test) Apex source files. To be specific,  changed  in this context is with regard to the project's configured  version control system , so  Changed Only  is applicable only to VCS-enabled projects. Enabling it for a run configuration in a non-VCS-enabled project will simply result in all of that run configuration's tests being executed as if that option was disabled. The  Changed Only  option can be enabled for all Apex unit test run configuration types 

  2.3.1.2 Issue 579  - Both of the aforementioned limitations of the new  Deploy before running unit tests  feature have been addressed: Multi-module  projects are now  properly supported , with out-of-date (transitive) dependencies from all dependency modules for the requested unit tests being deployed in dependency order before those tests are executed. Because unit test run configurations are associated with a  single connection , only dependencies for modules also configured for that connection are included. If  conflicts  are detected during the pre-test deployment and the user chooses to overwrite the org with the local files, the deployment  proceeds  and unit tests are executed after the successful deployment. Additionally tests executed against non-source-tracked orgs  not  configured for  shared login conflict detection  now only deploy  modified dependencies  and not all modified files. Issue 822  - Implemented another new feature for Apex unit test execution, specifically t

  2.3.1.1 (reissue of  2.3.1.0  with a critical bug fix) Fixed an NPE that would occur when configuring a brand new project for its connection, resulting in a blank IC2 project configuration screen. Sincere apologies for such a heinous oversight! Also note that I have already addressed both described shortcomings of the new deploy-before-test feature described below. Next week's build will fix the issue with a push cancelled due to conflict detection and add support for multi-module projects. 2.3.1.0 Issue 579  - Added a new Apex unit testing configuration option,  Illuminated Cloud | Configure Application | Unit Tests and Code Coverage | Unit Tests | Deploy before running unit tests  ( disabled  by default), that, when enabled, attempts to bring the Salesforce organization up to date before starting unit test execution for the requested set of Apex test classes/methods. The Salesforce organization is updated according to the project type and connection configuration as follows: So

  2.3.1.0 Issue 579  - Added a new Apex unit testing configuration option,  Illuminated Cloud | Configure Application | Unit Tests and Code Coverage | Unit Tests | Deploy before running unit tests  ( disabled  by default), that, when enabled, attempts to bring the Salesforce organization up to date before starting unit test execution for the requested set of Apex test classes/methods. The Salesforce organization is updated according to the project type and connection configuration as follows: Source-tracked orgs  are updated using  Push Metadata . Non-source-tracked orgs  that are  not  configured to use  conflict detection  or are configured to use  conflict detection  with  dedicated logins  are updated using  Deploy Modified Metadata . Non-source-tracked orgs  that are configured to use  conflict detection  with  shared logins  — which is incompatible with  Deploy Modified Metadata  as both mechanisms use the same timestamp comparisons for different purposes — are updated using  Dep