Hi Bill,

Thank you for contacting us with this issue.

May I please clarify with you if you are working with The Welkin Suite IDE for Windows? The reason for my question is that currently we have the different mechanisms of deployment to Organization on Windows and Mac version of the IDE. It is already changed and improved in The Welkin Suite Nova (for Mac) and will be changed in TWS Spire (for Windows) soon. 

I kindly ask you to check the status for your deployment from TWS on your Salesforce Org. You can find this information in the Setup mode -> Deploy section -> Deployment status.

Please share it with us. 

Thank you,

Kate

Hi Kate,

I am working with The Welkin Suite IDE for Windows.

When I checked the Deployment Status in Salesforce, I discovered that the deployment had run all of my test classes and there were 18 failures.

By default, Salesforce does not run test classes when deploying to a sandbox.  But apparently TWS is requesting that Salesforce run all tests.  TWS should not do this unless reqeusted by the users.  How can I prevent TWS from running all test classes when deploying to a sandbox?

Thanks,

Bill...

Hi again Bill,

Thank you for your quick response.

Right now, TWS runs all the tests from your target Organization during deployment process by default and there is no ability to change it. This applies to both Sandbox and Production environments. You can fix tests or comment them if this won't affect your Code Coverage greatly.

Our developers have already started to change the deployment mechanism in The Welkin Suite for Windows. After their changes will be released, you will have an ability to abort test run or run separate tests when you deploy to another Sandbox. This will be available for you in one of the nearest versions of The Welkin Suite Spire.

You can read more about the implemented deployment to organization in The Welkin Suite for Mac and how this will be released in TWS for Windows here.

Regards,

Kate

Hi Kate,

After your previous reply, I did an Internet search for "welkin sandbox deploy tests" and found the TWS deployment info for the Mac version that you referenced.  This is the exact functionality I need in my deployments.  I will have to wait for TWS Spire before I can begin using your product, as I need to be able to deploy to sandboxes without running any test classes.

Thanks for you assitance.

Bill...

Hi Bill,

I'm writing to inform you that the advanced abilities for the 'Deploy to another org' functionality are already available for you in The Welkin Suite for Windows.

Yesterday we released the Spire R12 of the IDE with these changes.

We will be glad to hear your feedback after updating to the latest version of The Welkin Suite IDE.

Best regards,

Kate

Hi Kate,

I looked at the new "Deploy to organization" feature in TWS Spire 12, but there are problems.

First, "Deploy to organization" does not detect which files have changed and it does not check those selection boxes.

I have attached a screenshot example of how a deployment looks in Eclipse with the Force.com IDE.  The changed files are highlighted in yellow, the action is Overwrite and the selection box is checked.  The UNchnaged files are highlighted in gray, the action is Overwrite and the selection box is NOT checked.

In TWS Spire 12, ALL files in the project have an action of overwrite, but none of them are selected.  You have to figure out for yourself which files have changed and check the selection box for those files.  For a large project like mine, this becomes a very difficult task.

In addition, all files that exist in the target Salesforce instance but not in the project, appear in the deployment list with an action of Delete.  None of these files are selected, so obviously they won't be deleted.  But in the Eclipse Force.com IDE, files that exist in the target Salesforce instance, but not in the projejct, to not appear in the deployment list.

If a file that did exist in the project was deleted from the project (not removed, but deleted), only then should is appear in the "Deploy to organization" with the Delete action.

The second problem has to do with the screen colors.  I was using the blue color theme.  This resulted in the "Deploy to organization" list having a white background with yellow text.  This was impossible for me to read.  I had to switch back to the dark color theme.

Bill...

Hi Bill,

Thank you for your feedback about the new Deployment process in The Welkin Suite. We highly appreciate it.

First of all, I'd like to ensure you that we will fix the issue with the deployment wizard in the Blue theme as well as we will review the colors in the Light theme as well. This should be done in the next release.

Regarding the cases that you've described:
     - About the changed files and 'Overwrite' option: Comparing files content requires much more time than "high-level" comparison. In the Force.com IDE this is done immediately when the wizard opens, so it requires more time to show you at least general overview of the deployment plan. In The Welkin Suite you have an option to execute 'Deep comparison' which will compare files content and change status to 'No differences' for files which are the same in both your project and target organization.
     - Regarding the checkboxes not checked by default - in TWS you have the option to filter this table by the Action column, so, for example, you can filter only files with 'Overwrite' action and select all of them at once. In general, in such a sensitive process as deployment we'd like to make less default selections if possible, so all the changes would be specifically selected by those who are deploying.
     - If we speak about the 'Delete' action for files which are not present in the project, but present in the organization - we believe that this approach is more flexible and we are going to keep it, at least for a while. Also, all destructive changes should be performed with additional care, so they won't be selected in the wizard by default.

You can find detailed explanations of how this process works in The Welkin Suite Spire in our latest release notes article - https://welkinsuite.com/blog/salesforce-deployment-in-spire-r12/

Thank you once more for your feedback,
Kate

Hi Kate,
Thank you for the information on the "Deep comparison" button.  That gives me a result very similar to what I see in the Eclipse Force.com IDE.  For me, the "Deep comparison" was very fast, even though I have 76 Apex class files in my project, many files with thousands of lines of code in them.
Thanks you also for the tip on using the filter feature.  This also allows me to filter out all the the "Delete" files.  I understand your logic for not checking the selection boxes by default, and as I thought about this, I agree that it's a good idea.
Thanks again for your assistance and for your excellent and very fast response!
Bill...

Hi Bill,

Thank you for your response and for your words.

I'm glad that now you can use all the possibilities of the deployment functionality.

If you would have questions or suggestions, please contact us. We will be happy to hear them.

Have a nice day!

Best Regards,

Kate

Hi Bill,

I want to inform you that yesterday we released the updated version of The Welkin Suite IDE - Spire R13.

This version contains some fixes for the deployment functionality. 

Also, the UI issue which you were faced with on the Blue color scheme is solved.

I'll close the current topic, however, please feel free to contact us when you would have any questions or suggestions.

Best Regards,

Kate