Skip to content

Commit f63d19a

Browse files
committed
2 parents b8d3c68 + 5fa196d commit f63d19a

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@
1313

1414
I hope you enjoy it. Please give me a star if you like my work. Thank you!
1515

16+
# Video Demo:
17+
![jenv](https://user-images.githubusercontent.com/55546882/162501231-b2e030bf-1194-4a1d-8565-ccd503b63402.svg)
18+
1619
## Installation
1720
1) **Clone this repository**
1821
2) **Add it to the path**
@@ -83,4 +86,4 @@ https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powersh
8386
Be careful you have to run it as pwsh and not as powershell
8487
Then you have to install Pester. This is only for tests: `Install-Module -Name Pester -Force -SkipPublisherCheck`
8588
You could use your already installed powershell as well. However it has an old Pester Module already installed which you can not use and I could not figure out how it can be updated: https://github.com/pester/Pester/issues/1201
86-
Navigate into the test folder and run the `test.ps1` file. It will backup your env vars and your jenv config while testing and automatically restore them later. But you should always let the tests finish else your vars and config wont be restored
89+
Navigate into the test folder and run the `test.ps1` file. It will backup your env vars and your jenv config while testing and automatically restore them later. But you should always let the tests finish else your vars and config wont be restored

0 commit comments

Comments
 (0)