rangersdo

Playwright E2E Testing Guidelines

Test Structure and Organization

• Store all tests under the tests/ folder
• Name test files based on the system component being tested (conceptual, not React component)
• Group related tests within a single file using test.describe blocks
• Use descriptive test names that explain the functionality being tested
• use test.use({storageState: ...}) for setting auth state across all test in the suite

Locator Strategy

rangersdo

[Project Name]

Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.

Project Context

[Brief description ]

• [more description]
• [more description]
• [more description]

rangersdo

x@x-tp:~/work/ot/libjson-rpc-cpp/build$ cmake ..
-- UNIX_DOMAIN_SOCKET_SERVER: YES
-- UNIX_DOMAIN_SOCKET_CLIENT: YES
-- TCP_SOCKET_SERVER: NO
-- TCP_SOCKET_CLIENT: NO
-- HTTP_SERVER: YES
-- HTTP_CLIENT: YES
-- UNIXDOMAINSOCKET_SERVER: YES
-- UNIXDOMAINSOCKET_CLIENT: YES
-- COMPILE_TESTS: YES

rangersdo

<link rel="import" href="../core-icon-button/core-icon-button.html">
<link rel="import" href="../core-toolbar/core-toolbar.html">
<link rel="import" href="../core-scaffold/core-scaffold.html">
<link rel="import" href="../core-header-panel/core-header-panel.html">
<link rel="import" href="../core-menu/core-menu.html">
<link rel="import" href="../core-item/core-item.html">
<link rel="import" href="../core-menu/core-submenu.html">

<polymer-element name="my-element">