Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
playwright-xray
Advanced tools
Publish Playwright test run on Xray
This reporter is based in playwright zephyr from Yevhen Laichenkov https://github.com/elaichenkov/playwright-zephyr Thanks Yevhen for the great contribution
npm i -D playwright-xray
Add reporter to your playwright.config.ts
configuration file
Authenticate with client_id
and client_secret
key. If your Xray instance is in a specified region, the API url can be configured by setting the cloud.xrayUrl parameter. By default, it will point to the US region with URL https://xray.cloud.getxray.app/
// playwright.config.ts
import { PlaywrightTestConfig } from '@playwright/test';
const config: PlaywrightTestConfig = {
reporter: [
[
'playwright-xray',
{
jira: {
url: 'https://your-jira-url',
type: 'cloud',
apiVersion: '1.0',
},
cloud: {
client_id: '',
client_secret: '',
// Optional: xrayUrl: '' if the xray region needs to be specified
},
projectKey: 'JIRA_CODE',
testPlan: 'JIRA_CODEXXXXX',
debug: false,
},
],
],
};
Authenticate with token
key.
// playwright.config.ts
import { PlaywrightTestConfig } from '@playwright/test';
const config: PlaywrightTestConfig = {
reporter: [
[
'playwright-xray',
{
jira: {
url: 'https://your-jira-url',
type: 'server',
apiVersion: '1.0',
},
server: {
token: 'YOUR_SERVER_TOKEN',
},
projectKey: 'JIRA_CODE',
testPlan: 'JIRA_CODEXXXXX',
debug: false,
},
],
],
};
Also, your playwright tests should include unique ID J79
of your Xray test case + |
:
// Xray test case ID + |
test('J79 | basic test', async ({ page }) => {
await page.goto('https://playwright.dev/');
const title = page.locator('.navbar__inner .navbar__title');
await expect(title).toHaveText('Playwright');
});
Is it possible to add some optional values to the Test Execution ticket.
// playwright.config.ts
import { PlaywrightTestConfig } from '@playwright/test';
const config: PlaywrightTestConfig = {
reporter: [
[
'playwright-xray',
{
jira: {
url: 'https://your-jira-url',
type: 'server',
apiVersion: '1.0',
},
cloud: {
client_id: '',
client_secret: '',
// Optional
xrayUrl: '',
},
server: {
token: '',
},
projectKey: 'JIRA_CODE',
testPlan: 'JIRA_CODE-XXX',
debug: false,
// Optional
testExecution: 'JIRA_CODE-YYY',
version: 'v1.0',
revision: '12345',
description: 'This test was executed automatically',
testEnvironments: ['dev', 'test'],
uploadScreenShot: true,
uploadTrace: true,
uploadVideo: true,
markFlakyWith: "FLAKY",
stepCategories: ['test.step'],
summary: `[${new Date().toLocaleString('fr-FR', { timeZone: 'Europe/Paris' })}] - Automated`,
dryRun: false,
runResult: true
},
],
],
};
If you use a proxy to access Jira, you need to configure the proxy. This proxy information will be used by Axios to send the results to Jira.
// playwright.config.ts
import { PlaywrightTestConfig } from '@playwright/test';
const config: PlaywrightTestConfig = {
reporter: [
[
'playwright-xray',
{
jira: {
url: 'https://your-jira-url',
type: 'server',
apiVersion: '1.0',
},
cloud: {
client_id: '',
client_secret: '',
},
server: {
token: '',
},
projectKey: 'JIRA_CODE',
testPlan: 'JIRA_CODE-XXX',
debug: false,
// Optional
proxy: {
protocol: 'http',
host: '0.0.0.0',
port: 80,
auth: {
username: 'USER',
password: 'p@$$w0Rd',
},
},
},
],
],
};
If your proxy server doesn't need authentication, just omit the
auth
part.If no proxy is configured, Axios is forced to doesn't use proxy.
Then run your tests with npx playwright test
command and you'll see the result in console:
-------------------------------------
⏺ Starting the run with 6 tests
⏺ The following test execution will be imported & reported: Chrome
✅ Chrome | XRAYISSUE-2 | another test
✅ Chrome | XRAYISSUE-1 | basic test
✅ Firefox | XRAYISSUE-1 | basic test
⛔ Chrome | XRAYISSUE-3 | another test
⛔ Firefox | XRAYISSUE-2 | another test
⛔ Firefox | XRAYISSUE-3 | another test
-------------------------------------
😀 Successfully sending test results to Jira
⏺ Description: Tests executed with playwright-xray plugin
⏺ Test environments: dev,test
⏺ Version: 3.5.2
⏺ Revision: 12345
⏺ Browser: Chrome
⏺ Test plan: XRAYISSUE-123
⏺ Test execution: XRAYISSUE-324
⏺ Test Duration: 25s
⏺ Tests ran: 3 (including reruns)
⏺ Tests passed: 2
⏺ Tests failed: 1
⏺ Flaky test: 0
-------------------------------------
⏺ Test cycle XRAYISSUE-324 has been updated
👇 Check out the test result
🔗 https://jira.com/XRAYISSUE-324
-------------------------------------
And you'll see the result in the Xray:
If you need to run multiple browsers, you need to use the project switch and run them after each other, e.g.
npx playwright test --project=Chrome
npx playwright test --project=Firefox
If multiple projects are selected in one run, only the first will be reported and imported to Xray.
If you need to send report for more than one test plan, you need to create a config file for each test plan. Create a folder (e.g. configs) in your project and for each test plan, create a new playwright config file in this folder.
// configs/TCK-87.config.ts
import { PlaywrightTestConfig } from '@playwright/test';
import base from '../playwright.config';
const config: PlaywrightTestConfig = {
...base,
testDir: '../tests',
use: {
...base.use,
headless: true,
},
reporter: [
[
'playwright-xray',
{
jira: {
url: 'https://your-jira-url',
type: 'server',
apiVersion: '1.0',
},
server: {
token: 'YOUR_SERVER_TOKEN',
},
projectKey: 'TCK',
testPlan: 'TCK-87',
},
],
],
};
export default config;
Now you can choose which config file you want to use executing the tests, using the command below:
npx playwright test --config=configs/TCK-87.config.ts
If no config file is chosen, the default config file "playwright.config.ts" will be used.
In order to enable IntelliSense to provide useful suggestions and avoid potential typos not being detected, you can import XrayOptions in the "playwright.config.ts" file and use the TypeScript satisfies operator on the playwright-xray configuration block. E.g:
import { PlaywrightTestConfig } from '@playwright/test';
import type { XrayOptions } from 'playwright-xray';
const config: PlaywrightTestConfig = {
reporter: [
[
'playwright-xray',
{
jira: {
url: 'https://your-jira-url',
type: 'server',
apiVersion: '1.0',
},
server: {
token: 'YOUR_SERVER_TOKEN',
},
projectKey: 'TCK'
} satisfies XrayOptions,
],
],
};
To have the steps imported you have to create them in the test issue itself. The steps will be imported by order of execution and inserted into the test.
Xray only permits an upload size of maximum 100 MiB and subsequently playwright-xray will fail to upload the
execution result due to the total size of videos and traces exceeds this limit. In order to still be able to
update the Xray execution status while still being able to view the videos and traces in e.g. Jenkins the
switches uploadScreenShot
and/ or uploadTrace
set to false
as shown below, can be used to exclude evidence from the Xray import file.
Test that will pass after a rerun will be tagged with whatever is defined with the option "markFlakyWith" If this option is not set, the test will be tagged as PASSED. Please note that you have to define the Execution Status you choose in Xray, e.g. FLAKY.
Stepcategories defines how playwright-xray reporter should recognize test steps. The built-in categories in Playwright are the following:
hook
for fixtures and hooks initialization and teardownexpect
for expect callspw:api
for Playwright API calls.test.step
for test.step API calls.If the option stepCategories
is not set, playwright-xray will default to ['expect', 'pw:api', 'test.step']
If e.g. only ['test.step']
is defined, playwright-xray will only record code defined with test.step('This is a test step', async () => { .... });
as a test step.
[${new Date().toUTCString()}] - Automated run
but this can be overidden by the
config file option summary:
The option dryRun
can be used to run the tests without uploading the results to Xray. If this option is set to true, the settings client_id
and client_secret
are ignored, and the reporter will produce a xray-payload.json
file that can be imported separately.
The option runResult
will generate a runresult.json
file containing a summary of the execution if is set to true (the default is false)
[
'playwright-xray',
{
jira: {
url: 'https://your-jira-url',
type: 'server',
apiVersion: '1.0',
},
server: {
token: 'YOUR_SERVER_TOKEN',
},
projectKey: 'TCK',
testPlan: 'TCK-87',
uploadScreenShot: false,
uploadTrace: false,
uploadVideo: false,
markFlakyWith: "FLAKY",
stepCategories: ['test.step'],
summary: `[${new Date().toLocaleString('fr-FR', { timeZone: 'Europe/Paris' })}] - Automated`,
dryRun: true,
runResult: true
},
],
playwright-xray is MIT licensed.
Fúlvio Carvalhido inluxc@gmail.com
Diller https://diller.no/
FAQs
XRAY reporter for the Playwright
The npm package playwright-xray receives a total of 13,656 weekly downloads. As such, playwright-xray popularity was classified as popular.
We found that playwright-xray demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.