PrzemyslawKlys
commented
1 year ago The tests are defined in Sources folder:
- 1 file per test
- 1 variable per test
- 1 scope (notice it can be Forest, DOmain, DomainController (all 3 being treated as AD), or anything else - and that gets treated as separate section/scope (so in your case could be PKI).
- 1 scope gets it's own TAB so if you want to have PKI split into two tabs, two sections you can have multiple Scopes for PKI - PKIServers, PKIClients or whatever
- That one variable is used in TEstimoCOnfiguration, which is located in TestimoConfiguration.ps1
- The left side is how it's going to be called by users
- The tests are in Sources folder, because Sources folder are "read" first when using Get-ChildItem -Recursive meaning variables will be available for TestimoConfiguration to use them. That's the one of the reasons those are separate folder
- ActiveDirectory in that hashtable in TestimoConfiguration is the only thing that has special consideration within Testimo to allow for Forest, Domain and DomainControllers. It's a single section in TestimoConfiguration (it used to be separate ones) but whether it's Forest,Domain or DC it's up to the Scope that's part of the test.
- Generally SCOPE is what the section is going to be called.
As part of Testimo I've also added external support of tests and tests for different technologies so I believe another Section such as ActiveDirectory (or how Office 365 is commented out called PKI or something it should just start working.
- Testimo now supports external tests that are taken from a folder. What's different about those ist that when defining those tests as hashtable you don't assign them to variable but simply define it as hashtable in a folder.
- Based on the Name and Scope it will either overwrite what's already existing (say you don't like how I did ForestBackup) or add something completely new based on Scope. It can be any scope, not only O365 and AD.
That means if you want to use private tests - you can.
- There is also DSC comparison built in, that's part of the examples
- And there's also Authorization process by using special Variables
I only wonder if there should be some kind of "modularized" support added. Because today is PKI, tomorrow something else. But that's something for the future. One thing to add is I will probably add some sort of "check if module is available" functionality and drop direct dependencies because people wanting PKI or O365 don't want AD module installed and vice versa.
PatrickOnGit
I would like to add PKI related tests. Do you have a template and some light documentation on where to put the tests, where to add configuration? There is a lot on how to use Testimo and also how to customize output, but nothing that I'm aware of on how to build new test.
I do understand that tests are in
\private
And folders are
..\Sources
It gets more tricky in how all the names relate to each other.
Modules required to test PKI would be PSPKI from Vadims Podans (now PKI Solutions) and PKIAudit.
Thank you for your support.
Best regards Patrick