search

pester / vscode-adapter

Run PowerShell Pester Tests with Visual Studio Code
MIT License
58 stars 14 forks source link

Shore up Supported Run Scenarios #176

Open JustinGrote opened 1 year ago

JustinGrote commented 1 year ago

Right now the way the run works is a bit of a hodgepodge, I would like to very definitively define the following run scenarios (with the bolded already implemented)

  1. Separate Process, Main Window, Std In/Out, Reuse Process - Ideally would go away for runspace approach
  2. Separate Process, Main Window, Std In/Out, Restart Process - Ideally would go away for runspace approach
  3. Separate Process, Reuse Runspace - Fastest but may be subject to artifacts
  4. Separate Process, Reset Runspace on every run - Slower but less likely to have artifacts, will not refresh for binary modules
  5. Separate Process, Restart Process on every run - Slow but best for binary modules
  6. PS Extension using RunCommand [Debug Profile] (Implemented Debug Only) - Run just does the same as mirror today
  7. Temporary PS Extension using RunCommand [Debug Profile] (Implemented Debug Only)
  8. PS Extension with runspace running Pester