npmpackage.info

Gathering detailed insights and metrics for cypress-msteams-reporter

Other packages similar to cypress-msteams-reporter

cypress-mochawesome-reporter

3.8.2

Zero config Mochawesome reporter for Cypress with screenshots

cypress-circleci-reporter

0.3.0

Cypress test reporter for CircleCI

cypress-msteams-allure-2

1.1.1

A microsoft teams reporter for allure reports generated by cypress

cypress-image-snapshot

4.0.1

Cypress bindings for jest-image-snapshot.

Gathering detailed insights and metrics for cypress-msteams-reporter

cypress-msteams-reporter

1.0.4

ISC

JavaScript

13.87 kB

320,157 2.7

Installations

npm install cypress-msteams-reporter

Pull Requests

Open

2

Total

3

Closed

0

Merged

1

Issues

Open

7

Total

13

Closed

6

Releases

Unable to fetch releases

Developer

maritome

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

14.15.3

NPM Version

6.14.9 Statistics

14 Stars

39 Commits

4 Forks

2 Watching

1 Branches

2 Contributors

Updated on 14 Mar 2024

Bundle Size

41.67 kB

Minified

13.87 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

320,157

Last day

-11.5%

330

Compared to previous day

Last week

1.5%

2,093

Compared to previous week

Last month

-2%

8,988

Compared to previous month

Last year

-5.4%

132,785

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

commander dotenv ms-teams-webhook

Dev Dependencies

@shelex/cypress-allure-plugin cypress

Versions

cypress-msteams-reporter

npm GitHub npm

Cypress Microsoft Teams Reporter

A Microsoft Teams reporter of your test results.
It uses the allure report generated by cypress-allure-plugin (or any other allure reporter) to send a message in a team channel of your choice with the status of the test run. Everyone gets a fast, short and well-organized feedback of the latest test execution.
The message sent to ms-teams include:

Test run status
How many test cases failed (if there are any)
The list of the test cases that failed (if there are any)
How many test cases are broken (if there are any)
The list of the test cases that are broken (if there are any)
A link of the allure report generated, which includes all the necessary details

How ms-teams message looks like

All test cases passed Some test cases failed Some test cases are broken

Installation

npm install cypress-msteams-reporter --save-dev

Prerequisites

allure-commandline
cypress-allure-plugin (or any other allure reporter)

Configuration

Create an incoming webhook for the team channel where you want to get the report. Copy the WEBHOOK URL and add it to your .env file:

MS_TEAMS_WEBHOOK_URL = 'yourWebhookUrl'

To add the images that you see in the above screenshots as part of your ms-teams messages, copy the folder assets/images in the root of your project.

To display in the ms-teams message the name of the application under test and its version when the tests were executed, create a environment.properties file within your allure-results folder. In the file add:

Application=Application Under Test
Version=vx.x.x

Usage

$ npx cypress-msteams-reporter

Usage: index [options]

Options:
  -v, --version          output the version number
  --verbose              show log output
  --report-path [type]   define the path of allure report file (default: "./allure-report/widgets/status-chart.json")
  --testEnv-path [type]  define the path of allure report environment properties file (default: "./allure-report/widgets/environment.json")
  --report-url [type]    provide the link for the Test Report (default: "")
  -h, --help             display help for command

If the allure report is uploaded somewhere, provide the link using the option --report-url. A button 'Open Test Report' will be part of ms-teams message. Onclick it, the allure test report will be opened.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.7

/10

Last Scanned on 2024-11-18

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More