Namespace Serenity.SystemConfiguration.Tests.Editor.Builder

Classes

CreateSystemConfigurationSettingsWindowRealRunDriver

Runs CreateSystemConfigurationSettingsWindow for real: a system configuration settings asset is created in the fixture folder, picked as the window's target and updated in place — the shape CreateSystemConfigurationSettingsWindowUpdateInPlaceTests drives.

CreateSystemConfigurationSettingsWindowReloadSafetyTests

EditMode tests proving CreateSystemConfigurationSettingsWindow re-attaches to its surviving scratch draft after a domain reload instead of rebuilding from disk and losing unsaved edits. A real script recompile cannot be driven from this suite, so Serenity.SystemConfiguration.Infrastructure.Editor.Builder.CreateSystemConfigurationSettingsWindow.SimulateDomainReloadForTests reproduces only what a reload leaves behind (the non-serialized wrapper gone, the [SerializeField] mirror untouched) — see that seam's own remarks for what stays unverified.

CreateSystemConfigurationSettingsWindowUpdateInPlaceTests

Proves CreateSystemConfigurationSettingsWindow against the shared UpdateInPlaceRoundTripContract: reopening the wizard on an already-configured asset and confirming with zero edits must leave every field untouched. Every test targets a fixture asset under a private temp folder, mirroring SystemConfigurationSettingsCreatorTests's own scaffolding.

SystemConfigurationSettingsCreatorTests

EditMode tests for SystemConfigurationSettingsCreator. Every test targets a fixture asset path under a private temp folder via Input.SettingsAssetPath — the real project's own UnitySystemConfigurationSettings asset(s), if any, are never touched, so these tests stay hermetic regardless of what the project already has configured.