Setting up your WAPT development and test environnement

Prerequisites

Attention

  • it is required to be a Local Administrator of the machine to use WAPT’s integrated environment for developing WAPT packages;
  • Disable UAC on your development computer;
  • we advize you to create / edit packages in a fully controlled environment, that is safe and disposable;
  • the usage of a disposable virtual machine (like Virtualbox) is recommended;

Disabling UAC

Note

Disabling UAC is only necessary on the packaging computer only.

  • open the Windows Configuration Panel;
capture d'écran du panneau de configuration Windows avec l'option des comptes utilisateur sélectionnée

Windows Configuration Panel

  • select :me,uselection:User Accounts;
capture d'écran du panneau de configuration des comptes utilisateur

User Accounts

  • modify User Account Control settings;
capture d'écran du panneau de configuration des comptes utilisateur

Changing UAC Settings

  • switch on Never notify;
capture d'écran des paramètres UAC

Changing UAC Settings

  • click on OK to confirm;

Attention

A computer reboot is required for the new configuration to apply correctly.

Make sure that you have your private key stored on the development computer

In the WAPT console, the fields private key and prefix must be filled …

Install the tis-pyscripter WAPT package

  • import the tis-pyscripter package in your local repository and install it on your development computer;

PyScripter

Pyscrypter project explorer

capture d'écran de l'explorateur de projets Pyscripter

Pyscrypter project explorer

Run Configurations Panel

capture d'écran des options de Run dans l'explorateur de projets Pyscripter

Run options in PyScripter project explorer

Editor panel

capture d'écran de la zone d'édition de Pyscripter

PyScripter edition panel

Python Console

capture d'écran de la console python de Pyscripter

PyScripter Python console

Recommendations regarding the test environment

The recommended method to correctly test your WAPT packages is to use a representative sample of machines in your inventory. So the more heterogeneous your installed base of machines, the larger your sample must be.

This method consists of testing the installation of the package on as many plateforms and configurations as possible, so to improve its reliability, before the WAPT package is transfered to production repositories.

Testing method

Operating systems and architectures

  • Windows XP;
  • Windows 7;
  • Windows 10;
  • Windows Server 2008 R2;
  • Windows Server 2012 and R2;
  • x86;
  • x64;
  • Physical and virtual machines;
  • laptops;

Hint

When possible, RC and Beta version of Operating Systems should be tested (ex: Windows 10 Creators Update)

State of Windows Updates

  • Microsoft Windows machine without any Windows update installed: the objective is to detect Windows updates that are required for the software to work properly and to adapt the WAPT package accordingly;
  • Microsoft Windows machine with all the latest Windows updates: the objective is to detect Windows updates that break the package and to adapt the WAPT package accordingly;

State of software installatations

  • Machines with many installed packages: the objective is to detect a possible dependency with an existing application;
  • Machines with many installed packages: the objective is to detect a possible conflict with an existing application;
  • Install older versions of the software: it is possible that the software installer does not support uninstalling a previous version of the software, in this case, the package will have to take to itself to remove older version of the software before installing the new version;