improve

src/dev/jest/config.js

@@ -67,15 +67,6 @@ export default {
     '<rootDir>/src/dev/jest/setup/babel_polyfill.js',
     '<rootDir>/src/dev/jest/setup/polyfills.js',
     '<rootDir>/src/dev/jest/setup/enzyme.js',
-
-    /*
-      FIXME: some unit tests in src/ are either running jsdom manipulations after `afterEach` code,
-      by default react-testing-library cleans up DOM after each test to keep unit tests in isolation,
-      we need to fix those tests in `src/` which are manipulating DOM after tests has finished and failing
-      if RTL attempts to clean up jsdom
-      https://github.com/elastic/kibana/issues/59469
-     */
-    '@testing-library/react/dont-cleanup-after-each',
   ],
   setupFilesAfterEnv: [
     '<rootDir>/src/dev/jest/setup/mocks.js',

src/dev/jest/setup/react_testing_library.js

@@ -18,7 +18,15 @@
  */
 
 import '@testing-library/jest-dom/extend-expect';
-import { configure } from '@testing-library/react';
+/**
+ * Have to import "/pure" here to not register afterEach() hook clean up
+ * in the very beginning. There are couple tests which fail with clean up hook.
+ * On CI they run before first test which imports '@testing-library/react'
+ * and registers afterEach hook so the whole suite is passing.
+ * This have to be fixed as we depend on test order execution
+ * https://github.com/elastic/kibana/issues/59469
+ */
+import { configure } from '@testing-library/react/pure';
 
 // instead of default 'data-testid', use kibana's 'data-test-subj'
 configure({ testIdAttribute: 'data-test-subj' });