New in Hutte: Effortlessly select test classes for deployment and more
Are you tired of dealing with the hassle of manually typing test class names during Salesforce deployments? Hutte's deployment functionality offers a seamless solution. But that's not all – we continue to refine our features to provide even greater convenience and efficiency.
Table of contents
From resetting revision numbers in sandboxes to specifying Apex classes to run post-refresh, our latest updates aim to streamline your development process. Read on to explore these enhancements and get a glimpse of what Hutte can offer you.
Easily select test classes to run during your deployment
You might have found Salesforce's change set UI frustrating, as it requires you to type class names for tests during deployments. However, with Hutte's deployment functionality, this is no longer an issue. You can conveniently select the test classes to run from a list in your deployment target organization.
Reset revision number of a sandbox feature
The revision number signifies the point from which this feature starts tracking changes. By default, it matches the most recent revision of metadata in the connected organization when the feature was initiated.
There are two scenarios when you might want to change the revision number of your feature:
- Updating it to the latest if you made changes in your sandbox after creating your feature, which you prefer not to track (default).
- Adjusting it to an earlier one if changes were made in your sandbox before you started your feature and want to include them. All revisions of the sandbox are listed with the revision number and revision date.
Specify Apex class to run after sandbox creation or refresh
We've added the ability to select a post-copy sandbox class to run after the creation or refresh process is complete. Typically, we recommend using our Sandbox Pool and refreshing Pool Orgs from your Developer Integration sandbox (often referred to as SIT). Ideally, this should contain all the necessary configuration and data for your fresh development sandboxes.
✅
However, there are scenarios where running a post-refresh Apex class is useful. Therefore, you can now select one of the classes from the org you are refreshing from and specify it as post-refresh.
By Salesforce's design, the chosen class must implement the "System.SandboxPostCopy" interface, which is why we only offer those for selection.
Additional enhancements
- Speed improvements to the sandbox feature and scratch org detail view.
- Fixed bug that occasionally – on the “Take Scratch Org from Pool –” did not select a default Pool Org to take.
- Minor UX improvements to the new “Pull Changes” UI when used on projects with multiple package directories.
- Navigation context remains when visiting “Profile Settings.”
Explore these transformations firsthand
Get in touch with us to discover how we can customize a superior user experience for you!
Authors
