Feature idea
When running integration tests (all-tests.sh) locally, the test runner produces side effects on the user's environment that are only partially cleaned up. Shell RC files (~/.bashrc, ~/.zshrc) are currently backed up and restored via an EXIT trap, but ~/.ide/.license.agreement is force-created via touch and never restored. On Windows, IDEasy's installer writes variables like IDE_ROOT and PATH modifications into the registry, where they persist across sessions.
The integration tests should fully preserve the user's pre-existing state. Before the run, all relevant files and environment variables that the tests or IDEasy itself may modify should be backed up and restored after the run.
Related issue: #1337
Additional context
No response
Feature idea
When running integration tests (
all-tests.sh) locally, the test runner produces side effects on the user's environment that are only partially cleaned up. Shell RC files (~/.bashrc,~/.zshrc) are currently backed up and restored via an EXIT trap, but~/.ide/.license.agreementis force-created via touch and never restored. On Windows, IDEasy's installer writes variables likeIDE_ROOTandPATHmodifications into the registry, where they persist across sessions.The integration tests should fully preserve the user's pre-existing state. Before the run, all relevant files and environment variables that the tests or IDEasy itself may modify should be backed up and restored after the run.
Related issue: #1337
Additional context
No response