Closed rarebreed closed 7 years ago
Actually, I changed how this works. The configuration service tests will run in their own describe() suite. There will be a beforeEach and afterEach to do setup/teardown.
I implemented this for file clean up by invoking the cockpit.spawn library.
When running the integration test to test the configuration interface, we need to "clean" any changes that happen via setRhsmConf commands.