-
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d5b9506
commit 682af51
Showing
1 changed file
with
43 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# Developing with Sampler set up | ||
|
||
Super quick introduction. | ||
|
||
We are using Sampler here for development and deployment | ||
|
||
It means that we are using the Sampler build and test process to ensure that we are __always__ using a clean build of the code we are writing and testing. :-) | ||
|
||
So to develop you need to understand the following: | ||
|
||
The code in the source directory is the code that will be built and deployed to the PowerShell Gallery. The the source directory is your working development directory. Any additional files or directories that are required can be added to the build.yaml CopyPaths | ||
|
||
The code in the output directory is the code that is built by Sampler. It is in the gitignore file so that it is not committed to the repo. It is deployed to the PowerShell gallery. The advantage is that the Sampler build process will create a clean environment and add the built module into the PSModulePath. | ||
|
||
# Workflow | ||
|
||
## Once in a session | ||
- Run `.\build.ps1 -ResolveDependency -Tasks noop` to download all required dependencies and set up the environment. | ||
|
||
## Coding | ||
|
||
- Code in the source directory | ||
- Save the files | ||
- Run the build.ps1 script | ||
- with Tasks build `./build.ps1 -Tasks build` | ||
- This will build the code and copy it to the output directory. | ||
<img width="741" alt="image" src="https://user-images.githubusercontent.com/6729780/204135400-c324ef33-c7c2-4031-a408-d70d174fecd5.png"> | ||
|
||
<img width="588" alt="image" src="https://user-images.githubusercontent.com/6729780/204135445-9f071e4e-ef36-4e15-8357-9da7d541285f.png"> | ||
|
||
<img width="259" alt="image" src="https://user-images.githubusercontent.com/6729780/204135493-2f51c768-51b1-440a-9e2b-1559dd854f22.png"> | ||
|
||
Once you have finished doing some coding and want to test | ||
- With Tasks build test `./build.ps1 -Tasks build,test` | ||
- This will build the code and run the Pester Tests. | ||
<img width="854" alt="image" src="https://user-images.githubusercontent.com/6729780/204135632-e3918657-60b0-4f8b-9c29-65beb4c5a391.png"> | ||
- if you have failed tests, you can | ||
- Run Pester manually `Invoke-Pester tests` | ||
<img width="922" alt="image" src="https://user-images.githubusercontent.com/6729780/204135673-78751e7b-cb5c-46c8-961d-07e5f25652c0.png"> | ||
- You can check the test results in the browser by creating a html page | ||
`.\tests\extent.exe -i .\output\testResults\NUnitXml_dbachecks_v2.0.18.Linux.PSv.7.3.0.xml -o .\output\testResults\reports -r v3html` and then __outside of the container__ `ii .\output\testResults\reports\index.html # outside of container` | ||
<img width="1172" alt="image" src="https://user-images.githubusercontent.com/6729780/204135720-775f4932-05a1-464a-9323-e0d5fe8a2210.png"> | ||
- Fix the broken tests or add more code and rinse and repeat. |