🪲 Not all Maester Tests being tested

[chaoticbeaver06]

Describe the bug

When executing Maester tests, there are a few tests with the status "Not tested" despite the correct permissions.

To Reproduce

Steps to reproduce the behavior:

1. Execute the Maester Tests with the required permissions
2. Filter Status "Not tested"

Expected behavior

The Maester tests should run and skipped if the requirements are not met. Otherwise there should be a description, why the test was not executed

Module Version

• Module Version 2.0.0

Environment Data

Name Value

---

PSVersion 7.5.4
PSEdition Core
GitCommitId 7.5.4
OS Microsoft Windows 10.0.26100
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

Screenshots

[SamErde]

If you look at the details of those tests, you'll see that they're tagged with 'LongRunning.' Tests with those tags do not run by default because they take longer as tenants get more objects to inspect (users, groups, applications, policies, devices, etc). Add the -IncludeLongRunning switch when running Maester to include these.