Skip to content

DevClate/Custom-Maester-Tests

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

44 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Custom Maester Test Collection

A collection of customs tests that can be quickly dropped into Maester and customized to your enviroment where needed.

This repository is still in it's beginning stages and I plan to add many more tests to this repository that just aren't 365 focused as well. I welcome any contributions, please make sure you create all 3 files per test so that it works smoothly for everyone - Creating Tests

There is also a webversion at Custom Maester Tests

Introduction

What are custom Maester tests?

Custom Maester tests are tests that fully integrate into Maester's framework to test your Microsoft 365 tenant and anything else you want to using Pester tests. Also providing PowerShell scripts to resolve any issues where possible.

Why custom Maester tests?

These are tests that aren't standard in Maester, but integrate into it.. Ensure that your tenant is always followning company standards. You may want to run tests that the current Maester framework doesn't have on your tenant or network and want a nice way to display those results as well as keeping it under one umbrella.

How do custom Maester tests help?

Allows you to have all of your tests under a single pane of glass that are specific to your company while gaining all of the benefits of Maester.

Getting Started

Step 1: Download Tests from GitHub

Download all tests needed from the repository. There should be 3 files for each test( .ps1, .tests.ps1, .md )

Step 2: Copy to your Custom folder

Copy the test files into your Maester Custom folder.

Step 3: Run the tests

Now when you run your custom tests folder these tests should show

Step 4: Customize to your company

For all files, run the Find and Replace in VSCode for "Contoso" with your company name. I have this as the last step to ensure the test works correctly in your enviroment before changing the name.

Using your own company standards

Step 1: Locate validation.json

By default, the validation.json is location in the tests/Entra/Validating folder

Step 2: Update config file

Update and or remove any fields that aren't necessary, or you can add more as well.

Step 3: Save config file

Save the config file

Step 4: Run tests

Run your tests again and see how the results change.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

No packages published