Closed volovyks closed 1 year ago
Before this change, we were not stopping near-sandbox processes in case the test failed. With time it leads to high memory, CPU, and battery usage. afterEach.always(...) solves the problem.
afterEach.always(...)
Before this change, we were not stopping near-sandbox processes in case the test failed. With time it leads to high memory, CPU, and battery usage.
afterEach.always(...)
solves the problem.