TestEnvironment

Three earlier posts are the pieces the module grew out of: Active Directory Test Data That Doesn’t Suck, From Plain Text Passwords to PowerShell SecretStore: Securing Your AD Test Environment and Seeding an Okta Test Tenant When You Only Get Ten Users.

Title card: Test Data That Breaks Scripts on Purpose

01Test Data That Breaks Scripts on Purpose

I built a lab by hand to test an RC4 migration script, and every run came back clean. The two accounts it should have caught were invisible, because my fixture held the same wrong assumption as the filter.

Title card: Active Directory Test Data, a Year and Six Providers Later

02Active Directory Test Data, a Year and Six Providers Later

In August 2025 I published a module that filled a lab domain and tore it down again. Its three commands still run, and almost nothing underneath them survived the move into TestEnvironment.

Title card: Seeding Entra ID When There Is Nothing to Paste

03Seeding Entra ID When There Is Nothing to Paste

Okta, Authentik, FreeIPA, PingOne and OneLogin all hand me a token to paste into a config file. Entra hands me nothing, so the seeder has to solve its own access problem before it can create a single user.

Title card: Eight Okta Users, and Everything That Changed Around Them

04Eight Okta Users, and Everything That Changed Around Them

I opened the Okta provider expecting to write the ten-user post again with better numbers. The eight users are the same eight users. Nearly everything around them has been replaced.

Title card: Seeding Authentik, Where the Directory Is Only the Floor

05Seeding Authentik, Where the Directory Is Only the Floor

Authentik was already in my homelab doing single sign-on, so there was no license cap to design around. Of everything the provider seeds, the three hundred users are the least interesting.

Title card: Seeding FreeIPA, Where Teardown Starts Revoking

06Seeding FreeIPA, Where Teardown Starts Revoking

My seed asks the FreeIPA realm’s own CA for ten real certificates, and a CA has no delete. Teardown revokes them, so every seeded realm keeps a record of the run, next to HBAC and sudo rules built to be misread.

Title card: A Directory Full of Question Marks: Seeding PingOne

07A Directory Full of Question Marks: Seeding PingOne

The first PingOne seed I ran from Windows PowerShell 5.1 turned every accented and Han name into question marks. The fault was in how 5.1 encodes a request body, and all six providers in the module had it.

Title card: A Role With Nothing but a Name: Seeding OneLogin

08A Role With Nothing but a Name: Seeding OneLogin

OneLogin gives a role, a group and a policy nothing but a name, and a Smart Hook not even that. Teardown still has to delete only what my seed made, so each object is proved by what it holds.