Overview of Testing Strategy

Historically there as been little test code for these extension. This is commonly because tasks tend to interact with external systems, such as file systems or APIs, thus making testing problematic. It has been easier to manually test as part of the release process.

As all CI/CD automation documentation says 'you need to automated testing for efficiency and consistency'. I need to make more of an effort, hence the revised folder structure of the Typescript based tasks. See Issue #202

The aim now is to

1. Have unit tests, written in Pester for Powershell or Chai for Typescript that can be run locally or as part of the VSTS based CI process. Mocking and test data file management will be used as needed.
2. Have functional tests, written in the same tools, Pester and Chai, that interact with real external systems. These will usually be run as part of the VSTS based CD process to the VSTS Marketplace