From 809c5d8a98281e3f5960e0d39ccb1d46ccf72092 Mon Sep 17 00:00:00 2001 From: yogabonito Date: Tue, 13 Sep 2022 06:41:42 +0200 Subject: [PATCH] docs: fix typo (#17235) --- docs/src/test-annotations-js.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/test-annotations-js.md b/docs/src/test-annotations-js.md index b4613dcf74..2452df5fc0 100644 --- a/docs/src/test-annotations-js.md +++ b/docs/src/test-annotations-js.md @@ -6,7 +6,7 @@ title: "Annotations" Playwright Test supports test annotations to deal with failures, flakiness, skip, focus and tag tests: - [`method: Test.skip#1`] marks the test as irrelevant. Playwright Test does not run such a test. Use this annotation when the test is not applicable in some configuration. - [`method: Test.fail#1`] marks the test as failing. Playwright Test will run this test and ensure it does indeed fail. If the test does not fail, Playwright Test will complain. -- [`method: Test.fixme#1`] marks the test as failing. Playwright Test will not run this test, as opposite to the `fail` annotation. Use `fixme` when running the test is slow or crashy. +- [`method: Test.fixme#1`] marks the test as failing. Playwright Test will not run this test, as opposed to the `fail` annotation. Use `fixme` when running the test is slow or crashy. - [`method: Test.slow#1`] marks the test as slow and triples the test timeout. Annotations can be used on a single test or a group of tests. Annotations can be conditional, in which case they apply when the condition is truthy. Annotations may depend on test fixtures. There could be multiple annotations on the same test, possibly in different configurations.