Jack Franklin 3b3a782f3a Enable interaction tests ...

This CL introduces the infrastructure and first test for what we're calling
"Interaction tests". These are tests that can be used to test component
behaviour that cannot be tested via Karma unit tests but don't require an e2e
test either.

The best example here is complex user interactions: clicking and dragging a
mouse, or doing multiple tabs to navigate through the UI.

Note that the one interaction test added here for theme_colors isn't the best
example of a complex test, but it's a test that's good enough for now whilst we
get everything set up on infrastructure and make sure it runs without flaking.

Bug: 1153281
Change-Id: Ifb37639a557c459974f703b8954ae68a93d5d368
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2566808
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Paul Lewis <aerotwist@chromium.org>

2020-12-03 10:44:22 +00:00

..

.gitignore

Port shared test runner logic into separate package

2020-04-20 10:32:58 +00:00

BUILD.gn

Enable test_suite to take a configurable server type.

2020-11-27 12:00:26 +00:00

component_hooks.ts

Add component hooks to conductor

2020-09-23 08:35:24 +00:00

custom-query-handlers.ts

Use Puppeteer's built-in pierce/ handler

2020-11-02 14:14:10 +00:00

hooks.ts

Enable interaction tests

2020-12-03 10:44:22 +00:00

mocha_hooks.ts

Enable interaction tests

2020-12-03 10:44:22 +00:00

OWNERS

Add OWNERS for test/conductor

2020-07-07 10:27:12 +00:00

puppeteer-state.ts

Enable interaction tests

2020-12-03 10:44:22 +00:00

test_server.ts

Enable test_suite to take a configurable server type.

2020-11-27 12:00:26 +00:00

tsconfig.json

Port shared test runner logic into separate package

2020-04-20 10:32:58 +00:00