Testing And Validation
The quickest and easiest way to become familiar with super is to try different options while in test mode. In this mode, super does not perform any Apple software updates, Jamf Pro Policy Triggers, or system restarts. Thus allowing you to test the other features and options of super.
Mode to validate super workflow options including credentials, deferrals, deadlines, dialogs, and notifications.
Command option examples:
--test-mode or -T
Command option disable examples:
--test-mode-off or -t
Configuration profile example:
<key>TestMode</key>
<true/>
When super is in test mode, it does not check for software updates or upgrades. Notifications in test mode only remain open for 10 seconds before super moves on with the workflow. However, you can change this duration via the --test-mode-timeout option as documented later on this page. Also, note that test mode will temporarily override any interactive dialog timeouts.
Because the test mode workflow does not actually check for available updates or upgrades, all macOS version numbers displayed in test mode are based on the current macOS version of the system.
Using super in test mode
As a default, test mode only simulates the macOS minor update workflow dialogs and notifications. Alternately, while in test mode, you can enable the following options individually to simulate other workflow variations, including:
-
Simulate macOS major upgrades:
--test-mode --install-macos-major-upgrades -
Simulate macOS Background Security Improvements (BSI):
--test-mode --install-macos-bsi-updates -
Simulate installing non-macOS software updates without restarting:
--test-mode --install-non-system-updates-without-restarting -
Simulate installing Safari software updates without restarting:
--test-mode --install-safari-updates-without-restarting -
Simulate installing Jamf Pro Policies:
--test-mode --install-jamf-policy-triggers=PolicyTrigger,PolicyTrigger,etc... -
Simulate user-initialed install-now workflows:
--test-mode --workflow-install-now -
Simulate scheduled install workflows:
--test-mode --scheduled-install-days=number
--test-mode --scheduled-install-date=YYYY-MM-DD:hh:mm
--test-mode --scheduled-install-user-choice
The amount of time in seconds to leave dialogs with timeouts and all notifications open while in test mode.
Command option example:
--test-mode-timeout=30
Command option disable example:
--test-mode-timeout=X
Configuration profile example:
<key>TestModeTimeout</key>
<string>30</string>
Using this option overrides the default test mode timeout of 10 seconds. Timeouts less than 10 seconds or more than 120 seconds (2 minutes) are rounded accordingly. Also, note that this timeout will temporarily override any interactive dialog timeouts.
Prior to downloading and installing macOS updates or upgrades, super validates that there is enough free storage space to perform the workflow. The free storage space requirements are automatically calculated by super based on the macOS update or upgrade download size plus an additional overhead of 15 GB for macOS updates and 35 GB for macOS upgrades. However, you can override the free storage space requirements as documented later on this page.
If there is not adequate free storage space, and a user is currently logged in, the workflow is paused while super displays an insufficient storage dialog encouraging the user to remove unnecessary items. This also opens the built-in macOS Storage Settings (or Storage Manager on older macOS systems) to assist the user in removing unnecessary items.
As a default, the super workflow remains paused and the dialog remains open until there is enough free storage space to continue with the workflow. Alternately, you can also set an interactive dialog timeout, in which case a timer is also displayed in the dialog.
If this workflow pauses, times out, or there is no currently logged-in user when super initially detects that there is insufficient free storage space, then the super workflow exits and automatically tries again later based on the error deferral timer.
The insufficient storage dialog
Override the default automatically calculated free storage space requirements.
Command option example for macOS updates:
--test-storage-update=1000
Command option example for macOS upgrades:
--test-storage-upgrade=1000
Command option disable example for macOS updates:
--test-storage-upgrade=X
Command option disable example for macOS upgrades:
--test-storage-upgrade=X
Configuration profile example for macOS updates:
<key>TestStorageUpdate</key>
<string>1000</string>
Configuration profile example for macOS upgrades:
<key>TestStorageUpgrade</key>
<string>1000</string>
You can set the free storage space testing overrides to any whole number (representing gigabytes required), including very large numbers, to easily test the insufficient storage dialog. While changing the default free space storage size is useful for testing workflows, it is not recommended for production.
For portable Mac computers, super validates that the system is either connected to a power adapter or that the battery is sufficiently charged (20% for Apple silicon, 50% for Intel) before attempting to install macOS updates or upgrades. If the battery level is below this requirement, and a user is currently logged in, the workflow is paused and super displays an insufficient power dialog encouraging the user to attach the computer to a power adapter.
As a default, the super workflow remains paused and the dialog remains open until the user connects a power adapter. Alternately, you can also set an interactive dialog timeout, in which case a timer is also displayed in the dialog.
If this workflow pause times out or there is no currently logged-in user when super initially detects that there is insufficient battery power, then the workflow exits and automatically tries again later based on the error deferral timer.
The power required dialog
Override the default battery level percentage (20% for Apple silicon, 50% for Intel) requirement.
Command option example:
--test-battery-level=101
Command option disable example:
--test-battery-level=X
Configuration profile example:
<key>TestBatteryLevel</key>
<string>101</string>
You can set the battery level override to any whole number (representing battery percentage level required), including a number over 100 percent, to easily test the insufficient power dialog. While changing the default battery level percentage is useful for testing workflows, it is not recommended for production.
Delete locally saved configuration in the main super settings file and delete workflow caches.
Command option examples:
--reset-super or -x or -X
Sometimes the main super settings file may contain previously configured options and workflow caches that are causing unexpected results, so resetting this can help resolve issues. This option cannot be set via a MDM configuration profile. However, any other options that are specified via a super MDM configuration profile remain in effect as long as the super workflow remains active.
This option does not delete any local credential options, Jamf Pro API credential options, or advanced alternate configurations. However, you can also use this option along with the --auth-delete-all option to also delete any saved local credential options or Jamf Pro API credential options. Additionally, you can use the --config-delete-all option to disable and delete any advanced alternate configurations.