# windows-utilities-tests **Repository Path**: mirrors_cloudfoundry/windows-utilities-tests ## Basic Information - **Project Name**: windows-utilities-tests - **Description**: No description available - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2021-10-22 - **Last Updated**: 2026-03-15 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # windows-utilities-tests This repo houses tests used to verify Windows Utilities Release functions as expected. # Example configuration You can create a `config.json` file, eg: ```json { "bosh": { "ca_cert": "", "client": "", "client_secret": "", "target": "", "gw_private_key": "", "gw_user": "" }, "stemcell_path": "", "windows_utilities_path": "", "stemcell_os": "", "az": "", "vm_type": "", "vm_extensions": "", "network": "" } ``` And then run these tests with `CONFIG_JSON= ginkgo`. Jobs should be developed in a test driven manner. Writing tests for our test jobs is important because the feedback loop of running unit tests locally is much faster than the feedback loop we get from running the integration tests on a remote vm. Jobs with unit tests can be tested by running `Invoke-Pester` in a job's directory on a windows machine. For example: running `Invoke-Pester` in `windows-utilities-tests/assets/wuts-release/jobs/check_windowsdefender/templates/modules` runs the tests in `CheckWindowsDefender.Tests.ps1`