Test Software Packages
You can evaluate a package on a lab asset before you execute it on production assets. This enables you to avoid any failure in the production environment.
Testing can be done before or after a package is reviewed and approved.
To execute a selected package on test assets, follow these steps:
- Navigate to the Scripts > Software Packages tab.
- Select a package and click Test Package from the Quick Actions menu.
- Select the asset selection mode and assets on which you want to test the package.
- Manual Asset Selection
- Import Assets
a. Manual Asset Selection:
You can manually select the assets you want.
If you want to specify assets, follow these steps:
- In the Add Assets section of the Select Assets page, click the + sign.
- In the Select Assets page, select the assets that you want to include in the script run and then click Apply.
If you want to include asset tags, follow these steps:
-
In the Add Asset Tags section of the Select Assets page, click the + sign.
-
In the Select Tags page, select the tags that you want to include in the script run and then click Apply.
You can add All or Any asset tags.
These options determine how assets are filtered and included for execution based on selected tags.
- Any: When you select Any, the system executes the package on the lab asset if it has at least one of the selected tags.
- All: When you select All, the system executes the package on the lab asset if it has all the selected tags. This means that the asset must have all the tags you have selected.
b. Import Assets:
- Upload a CSV file containing asset names and use those assets to execute a script and schedule it. It helps you quickly target multiple assets at a time.
- Click Browse to upload the CSV file from your destination. Before execution, all imported assets are automatically validated to identify any errors or inconsistencies.
The feature supports both immediate execution and scheduled script execution workflows, providing flexibility in managing asset imports.- CSV file should be in the comma-delimited format.
- CSV files are allowed up to 2 MB in size and support up to 5,000 assets per import.
- The CSV file must contain only unique asset names. Any duplicate asset names found in the CSV file are marked as invalid with the reason Duplicate asset. Ensure each asset name appears only once in the file before uploading.
-
The script runs on the assets listed in the uploaded CSV file. After uploading the CSV file, you can download a report that lists the assets that failed validation. Each entry includes the asset name and a validation message that explains why the asset was excluded.
-
The CSV file includes possible reasons for validation failures and their corresponding conditions:
Validation Message Description Not found The asset name does not exist in your account. Lab asset The asset is a lab asset and is only available in test mode. Blocked asset The asset is in the global exclusion list and cannot be scheduled. Platform is invalid The asset's operating system does not match the script's platform. This is not lab asset In test mode, only lab assets are eligible for validation. Duplicate asset The same asset name appears more than once in the CSV file. Limitations
- Asset names must exist in the database to pass the validation.
- Failed asset download information is available for a limited duration after validation.
4. Enter the Description for testing the packages and click Test Package. A new package job is created and listed under the
Jobs > Software Package Jobs tab. For the test packages, a job is created as: Test-SoftwarePackageName-TimestampEpoch.