The QA Settings Configuration Tool helps to create and customise your configuration settings for your environment. Editing large INI files can be time consuming and error prone, this tools helps to solve this issue.

To start the QA Settings Configuration Tool, right click the QA-Settings-Configurator.ps1 file and select Open with PowerShell from the menu. After a few seconds the following window will appear...

Click the Set Check Location button and locate the folder where your scripts are located. Once done, you will be able to change the language (if any) and a base settings file (if any others exist). Click Import Settings when done.

The tool will then scan the scripts folder and load the selected settings file.

Once the scripts folder has been scanned, the next page is shown. This allows you to view all the checks available and to select which ones you want to enable for your environment. By default a couple of checks are disabled, however they can be enabled by ticking the check box next to their name.

Once you have selected the checks for your environment, click the Set Values button.

The third page shows a second row of tabs, one for each of the sections. Within each of the these is a list of the checks you selected, as well as the required settings for each check. Double-click each of the settings and change the values that suit your environment.

When you are happy with your selected settings and their values, click the Complete button to move onto the last page.

Now that you have completed your changes, enter a short code for your QA script file. This will be the unique code that the QA compiler will use to name your QA script file. For example, a short code of ACME will generate a QA script called QA_ACME_v3.xx.xxxx.ps1. Also enter a company name for the HTML reports that are generated.

Click Save Settings when you are ready, and enter a filename to save your settings as. Generate a compiled QA script from this page too by clicking the Generate QA Script button.

You will find two script files in the same folder as the tool, ready to be copied into your environment and run against one or more servers.