@@ -287,6 +287,22 @@ describe.each(secureContextValues)("useClipboard - secure: %j", (isSecure) => {
287
287
setSimulateFailure ( true ) ;
288
288
await act ( ( ) => result . current . copyToClipboard ( "dummy-text-2" ) ) ;
289
289
expect ( result . current . copyToClipboard ) . toBe ( initialCopy ) ;
290
+
291
+ /**
292
+ * Trigger a successful clipboard interaction
293
+ *
294
+ *@todo For some reason, using the assertClipboardUpdateLifecycle
295
+ * helper triggers Jest errors with it thinking that values are being
296
+ * accessed after teardown, even though the problem doesn't exist for
297
+ * any other test case.
298
+ *
299
+ * It's not a huge deal, because we only need to inspect React after the
300
+ * interaction, instead of the full DOM, but for correctness, it would
301
+ * be nice if we could get this issue figured out.
302
+ */
303
+ setSimulateFailure ( false ) ;
304
+ await act ( ( ) => result . current . copyToClipboard ( "dummy-text-2" ) ) ;
305
+ expect ( result . current . copyToClipboard ) . toBe ( initialCopy ) ;
290
306
} ) ;
291
307
292
308
it ( "Always uses the most up-to-date onError prop" , async ( ) => {