Skip to content

Latest commit

 

History

History
31 lines (21 loc) · 1.13 KB

ReadMe.md

File metadata and controls

31 lines (21 loc) · 1.13 KB
Raw

The spec folder

Overview

Each integration test consists of one or more specs, or specifications.

Launching tests

  • Double click the test file, e.g. GUIDGenerator.spec.vbs, or
  • From a powershell or cmd.exe console, type
   cscript /nologo .\GUIDGenerator.spec.vbs

output:

--------- GUIDGenerator class -------------------------------------------------
Pass      should return a valid GUID on Generate call
Pass      should return a valid GUID on default property call

'Suites' or collections of tests may be run using the TestLauncher* files in the suite folder.

Different kinds of tests

  • Files named *.spec.sk.vbs use the SendKeys method and should be used with caution because the tests simulate user input/keystrokes.
  • Files named *.spec.elev.vbs are intended to be run from an elevated command prompt.
  • Files named *.spec.std+elev.vbs are intended to be run from either an elevated command prompt or from a non-elevated command prompt.
  • Files named *.spec.wow.vbs are intended to be run on a 64-bit system to test the specified class with the 32-bit executable(s).