Dmitry Gozman 0ade6af689
api(trace): introduce artifacts options (#3914)
api(trace): introduce artifacts options

This introduces launch({ artifactsPath }) and newContext({ relativeArtifactsPath, recordTrace }) options.
- artifactsPath option controls the directory where all artifacts go. If not passed, artifacts are not collected.
- relativeArtifactsPath can be used to put context-specific artifacts into a subfolder. If not passed, shared artifactsPath is used.
- recordTrace controls trace recording.

We also expose trace types under playwright/types/trace.d.ts.

In the follow up:
- videos will be put into artifactsPath;
- downloads will be put into artifactsPath, or keep using existing downloadsPath when artifactsPath is not specified.
2020-09-18 11:54:00 -07:00
..
2020-07-31 11:58:12 -07:00
2020-07-08 08:59:58 -07:00
2020-07-31 11:58:12 -07:00

Documentation

Capabilities

Playwright is a library to automate Chromium, Firefox and WebKit with a single API. Playwright is built to enable cross-browser web automation that is ever-green, capable, reliable and fast.

  • Ever-green browser engines
  • Headless execution
  • Scenarios that span multiple pages, domains and iframes
  • Auto-wait for elements to be ready before executing actions (like click, fill)
  • Reliable signals instead of timeouts (like network response, popup, navigation)
  • Intercept network activity for stubbing and mocking network requests
  • Emulate mobile devices, geolocation, permissions
  • Support for web components via shadow-piercing selectors
  • Native input events for mouse and keyboard
  • Upload and download files

Table of contents

  1. Introduction
  2. Guides
  3. Tutorials
  4. Integrations
  5. Reference
  6. Get help