review comments

Author: LFDanLu

packages/@react-aria/test-utils/src/combobox.ts

@@ -119,7 +119,7 @@ export class ComboBoxTester {
   }
 
   /**
-   * Returns a option matching the specified index or text content.
+   * Returns an option matching the specified index or text content.
    */
   findOption(opts: {optionIndexOrText: number | string}): HTMLElement {
     let {

packages/@react-spectrum/picker/test/Picker.test.js

@@ -1085,8 +1085,7 @@ describe('Picker', function () {
       expect(picker).toHaveTextContent('Two');
     });
 
-    // TODO: re-enable after merge
-    it.skip('can select items with the Enter key', async function () {
+    it('can select items with the Enter key', async function () {
       let {getByRole} = render(
         <Provider theme={theme}>
           <Picker label="Test" onSelectionChange={onSelectionChange}>

packages/dev/docs/pages/react-aria/testing.mdx

@@ -29,8 +29,7 @@ for each aria pattern and how they can be used to simulate common user interacti
 ## Introduction
 
 Running automated tests on your application helps ensure that it continues to work as expected over time.
-You can use testing tools like [Enzyme](https://enzymejs.github.io/enzyme/) or
-[React Testing Library](https://testing-library.com/docs/react-testing-library/intro) along with test runners like
+You can use testing tools like [React Testing Library](https://testing-library.com/docs/react-testing-library/intro) along with test runners like
 [Jest](https://jestjs.io) or [Mocha](https://mochajs.org) to test applications built with React Aria Components or hooks. These generally
 work quite well out of the box but there are a few things to consider to ensure your tests are the best they
 can be.
@@ -67,18 +66,6 @@ let tree = render(<MyComponent />);
 let option = tree.getByRole('button');
 ```
 
-### Enzyme
-
-In Enzyme, you can [use CSS selectors](https://enzymejs.github.io/enzyme/docs/api/ReactWrapper/find.html) to find
-elements. You can query by role using an attribute selector:
-
-```tsx
-import {mount} from 'enzyme';
-
-let wrapper = mount(<MyComponent />);
-let option = wrapper.find('[role="option"]');
-```
-
 ## Test ids
 
 Querying by semantics covers many scenarios, but what if you have many buttons on a page? How do you find the specific button
@@ -92,7 +79,7 @@ through to their underlying DOM nodes, which allows you to use an attribute like
 a particular instance of a component. For example, you could add test ids to the two input elements
 in a login form and use them to find the username and password fields.
 
-This example uses React Testing Library, but the idea could be applied in a similar way with Enzyme or other
+This example uses React Testing Library, but the idea could be applied in a similar way with other
 testing libraries.
 
 ```tsx

packages/dev/docs/pages/react-spectrum/testing.mdx

@@ -24,8 +24,7 @@ query the DOM tree for elements and simulate user interactions.
 ## Introduction
 
 Running automated tests on your application helps ensure that it continues to work as expected over time.
-You can use testing tools like [Enzyme](https://enzymejs.github.io/enzyme/) or
-[React Testing Library](https://testing-library.com/docs/react-testing-library/intro) along with test runners like
+You can use testing tools like [React Testing Library](https://testing-library.com/docs/react-testing-library/intro) along with test runners like
 [Jest](https://jestjs.io) or [Mocha](https://mochajs.org) to test React Spectrum applications. These generally
 work quite well out of the box but there are a few things to consider to ensure your tests are the best they
 can be.
@@ -72,18 +71,6 @@ let tree = render(<MyComponent />);
 let option = tree.getByRole('button');
 ```
 
-### Enzyme
-
-In Enzyme, you can [use CSS selectors](https://enzymejs.github.io/enzyme/docs/api/ReactWrapper/find.html) to find
-elements. You can query by role using an attribute selector:
-
-```tsx
-import {mount} from 'enzyme';
-
-let wrapper = mount(<MyComponent />);
-let option = wrapper.find('[role="option"]');
-```
-
 ## Test ids
 
 Querying by semantics covers many scenarios, but what if you have many buttons on a page? How do you find the specific button
@@ -97,7 +84,7 @@ through to their underlying DOM nodes, which allows you to use an attribute like
 a particular instance of a component. For example, you could add test ids to the two input elements
 in a login form and use them to find the username and password fields.
 
-This example uses React Testing Library, but the idea could be applied in a similar way with Enzyme or other
+This example uses React Testing Library, but the idea could be applied in a similar way with other
 testing libraries.
 
 ```tsx