arrow-left Back to topicQuizAnnotationsCheck yourself1.There's a known bug in Safari — the date picker component crashes. You want to track the test but not break CI. Which annotation do you use?test.fail — run the test and expect it to failtest.fixme — mark as known failure, don't runtest.skip(browserName === 'webkit') — skip only on Safari2.You annotate a test with test.fail(). The underlying bug gets fixed and the test now passes. What does Playwright do?The test is marked as passed — expected behaviorPlaywright reports an error — the test was expected to fail but passedPlaywright skips the test since it's annotated3.What does test.skip() do when called without any condition argument?It skips the test only on CI environmentsIt marks the test as skipped unconditionally — it will never runIt skips only the next expect() assertion inside the testIt runs the test but ignores any failures4.What is the difference between test.skip() and test.fixme()?They are identical — fixme is just an alias for skiptest.fixme() runs the test but suppresses failure output; test.skip() doesn't run it at allBoth skip the test, but test.fixme() signals intent — 'this is a known broken thing that needs to be fixed', not just 'skip for now'test.fixme() only works inside test.describe() blocks5.What does test.slow() do to the test timeout?It sets the timeout to a fixed 120 seconds regardless of the global configIt triples the default timeout for that specific testIt doubles the default timeout for that specific testIt disables the timeout entirely for that test6.How do you apply a tag to a test so it can be filtered with --grep @smoke on the CLI?Add @smoke as a JavaScript decorator above the test functionEither include @smoke in the test title string, or pass { tag: '@smoke' } as the second argument to test()Register the tag in playwright.config.ts tags[] arrayUse test.tag('@smoke') before the test body7.What is the purpose of test.info().annotations in a test body?It returns the list of annotations attached to the currently running test, useful for conditional logic inside the testIt adds a new annotation to the test at runtimeIt sends the annotation to the HTML report server immediatelyIt reads annotations from the playwright.config.ts file8.You want to prevent test.only() from ever being accidentally committed and breaking CI. What config option achieves this?disableOnly: true in playwright.config.tsAdd a lint rule that bans test.only in all filesforbidOnly: !!process.env.CI in playwright.config.tsSet only: false in each project's use blockSubmit answersRetriesNext arrow-right