Remove now-outdated section on testing changes on watchOS

Contributing.md

@@ -37,10 +37,3 @@ To run macOS tests locally, you'll need to do the following in the Valet Xcode p
 You can now run all macOS tests locally. Note that you will be required to enter your computer password _many_ times in order for the tests to successfully complete. Failing to enter your password will cause a test to fail. Make sure not to commit these project configuration and code changes after testing your change.
 
 If you encounter entitlement errors when running tests after following the above steps, you can address by opening `/System/Applications/Utilities/Keychain\ Access.app` and deleting all entries that start with `VAL_VAL`. Note that this will delete any secrets from your macOS applications that utilize Valet, so this step should be taken only as a last resort.
-
-
-### Testing changes on watchOS
-
-When making changes that change how the keychain works on watchOS, you must test this change locally. Unfortunately, Apple doesn't yet ship a native XCTest library on watchOS, which means we currently cannot easily run these tests in CI. We have, however, hooked up [a custom implementation of XCTest](https://github.com/dfed/XCTest-watchOS) to enable running tests locally. If you're interested in helping us get this test suite running in CI, check out issue [#128](https://github.com/square/Valet/issues/128).
-
-To run tests against watchOS, you'll need to select the `Valet watchOS Test Host App` target, select an Apple Watch simulator, and then run the target. You'll know that tests have succeeded because the application run will not hit an assertion failure and will print `ALL TESTS PASSED` to the Xcode console.