you54f / cypress-plugins Goto Github PK

Hi, I am not sure how I can use this to only report on slack. I have the slack webhook , but all i want is that when I run npm test
to run all the specs and generates a report on its own at the end and posts it on slack.
I followed this
https://medium.com/@you54f/slack-reporting-for-cypress-io-421064865a83
You say I do this $ export SLACK_WEBHOOK_URL=yourWebhookUrlHere
I dont have a CI or anything.
"reporter": "cypress-multi-reporters", "reporterOptions": { "reporterEnabled": "mochawesome", "mochawesomeReporterOptions": { "reportDir": "cypress/reports/mocha", "quite": true, "overwrite": false, "html": false, "json": true } }

and in my package.json I have
"cy:run": "CYPRESS_RETRIES=3 cypress run "", "clean:reports": "rm -R -f cypress/reports && mkdir cypress/reports && mkdir cypress/reports/mochareports", "pretest": "npm run clean:reports", "scripts": "cypress run", "combine-reports": "mochawesome-merge cypress/reports/mocha/*.json > cypress/reports/mochareports/report.json", "generate-report": "marge cypress/reports/mochareports/report.json -f report -o cypress/reports/mochareports", "posttest": "npm run combine-reports && npm run generate-report", "test" : "npm run cy:run|| npm run posttest"

"dependencies": { "cypress": "^5.2.0", "cypress-cucumber-preprocessor": "^2.5.4", "cypress-file-upload": "^4.0.7", "cypress-multi-reporters": "^1.4.0", "faker": "^4.1.0", "mocha": "^8.2.1", "mochawesome": "^6.2.1", "mochawesome-merge": "^4.2.0", "mochawesome-report-generator": "^5.1.0" },

Currently if I pass--report-dir it appends the path/filename to the --custom-url option. The problem I have is the report- dir folders are deployed to the root, so the folder structure doesn't exist on the environment and therefore the resulting link is broken.

If I don't pass report-dir then the reports aren't found.

Is there a workaround for this?

Hi @YOU54F

On v1.1.8-alpha I am seeing failed runs resulting in green slack posts, as if they have passed.

We are only using SLACK_WEBHOOK_URL but I have seen this working previously, reflecting passed/failed runs correctly.

Is there a need to also supply SLACK_WEBHOOK_FAILED_URL to handle failed runs?

Thanks

Hi!

Thanks so much creating this plugin! 🥇 💯 👍

I'm having issues running the execution part npx cypress-slack-reporter

npx cypress-slack-reporter Error: Cannot find test report @ /Users/ronakchovatiya/Documents/Work/.../mochareports

Specifically
Set the following environment variables in your localhost or CI configuration. 🤔

i've created config.env.test file with my slack webhook
$SLACK_WEBHOOK_URL - The full URL you created in the last step
where does the export go?
$ export SLACK_WEBHOOK_URL=yourWebhookUrlHere -

Execution
$ npx cypress-slack-reporter --help - this works

Steps performed

• yarn add cypress-slack-reporter --dev
• yarn add mocha @5.4.2 (instead of the latest 6 which gave error)
• yarn Added all of mochawesome reports (if i add the --reporter flag it works and i do get a html report)
• Created Slack app and Webhook URL / Oauth
• added code snippets for cypress.json and reporterOpts.json
• I'm not using CIRCLE CI - need it to just run locally for now then will add gitlab later

Guess the main issue I'm faceing not know how to hook up the config.test.env file in my react app and error message for not finding mochareports i even created folder with same name in the specified place.

P.S - i've tried the same steps for the example repo you've created react-ts-testing-example Which has all setup - i am able to run the website locally and normal cypress test pass.. But 😓 not able to run npx cypress-slack-reporter

System Info

MacOS
Cypress : 3.3.0
"cypress-slack-reporter": "^0.2.6",
"mocha-multi-reporters": "^1.1.7",
"mochawesome": "^3.1.2",
"mochawesome-merge": "^1.0.7",
"mochawesome-report-generator": "^3.1.5",

--

Thanks again! 🙏

Hi!
I'm facing with issue that slack message sends empty message in chanell because of those err messages
"Multiple html reports found & cannot determine filename, omitting html report from message
Cannot find test report, so sending build fail message
I have mochareports folder related to package.json
also here is my merge\marge commands - similar to what you suggesting in previous github issue
"combine-reports": "mochawesome-merge cypress/reports/*.json > mochareports/mochawesome.json",
"generate-report": "marge mochareports/mochawesome.json -f report -o mochareports"
"create-report": "npm run combine-reports && npm run generate-report"

tried to move mochareports folder to cypress folder - didn't get luck with that
any advice? thanks

Hi @YOU54F

I'm getting an error using this config:

gocd-test:
	source .env && rm -rf ./cypress/reports/ && yarn cy:run:pr && npx cypress-slack-reporter  --ci-provider custom --custom-url "https://gocd.com" --vcs-provider bitbucket --report-dir '.' --verbose true

Output

✨  Done in 152.92s.
 ciProvider:- custom
 customUrl:- https://gocd.com
 vcsProvider:- bitbucket
 reportDirectory:- .
 videoDirectory:- cypress/videos
 screenshotDirectory:- cypress/screenshots

{"level":40,"time":1614963391577,"pid":12750,"hostname":"UK04128","msg":"Multiple html reports found & cannot determine filename, omitting html report from message"}
{"level":40,"time":1614963391683,"pid":12750,"hostname":"UK04128","msg":"Multiple json reports found, please run mochawesome-merge to provide a single report, using first report for test status"}
/Users/robin/rg/cypress-web-tests/node_modules/cypress-slack-reporter/bin/slack/slack-alert.js:161
        throw new Error(e);
              ^

Error: TypeError: Cannot read property 'suites' of undefined
    at Object.exports.slackRunner (/Users/robin/rg/cypress-web-tests/node_modules/cypress-slack-reporter/bin/slack/slack-alert.js:161:15)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
npm ERR! code 1
npm ERR! path /Users/robin/rg/cypress-web-tests
npm ERR! command failed
npm ERR! command sh -c cypress-slack-reporter "--ci-provider" "custom" "--custom-url" "https://gocd.com" "--vcs-provider" "bitbucket" "--report-dir" "." "--verbose" "true"

Using the || operator, the tests run but cypress-slack-reporter does not get executed

source .env && rm -rf ./cypress/reports/ && yarn cy:run:pr || npx cypress-slack-reporter  --ci-provider custom --custom-url "https://gocd.com" --vcs-provider bitbucket --report-dir '.' --verbose true

The .env file contains

export SLACK_WEBHOOK_FAILED_URL=https://hooks.slack.com/services/xxx
export SLACK_WEBHOOK_PASSED_URL=https://hooks.slack.com/services/xxx
export BUILD_DISPLAY_NAME=#2991
export BUILD_ID=2991
export BUILD_NUMBER=2991
export BUILD_TAG=DEPLOY-staging-api-2991
export BUILD_URL=https://gocd.com
... etc

So it would be good to get some help on why the first command (using &&) is failing. Thanks.

Hi @YOU54F

Theres a warning for cypress-slack-reporter:

npm WARN [email protected] requires a peer of mochawesome@^3.1.1 but none is installed. You must install peer dependencies yourself.

I created an issue here too.

Vulnerabilities

DepShield reports that this application's usage of lodash.merge:4.6.1 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)
• (CVSS 6.5) [CVE-2018-3721] lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutabl...

Occurrences

lodash.merge:4.6.1 is a transitive dependency introduced by the following direct dependency(s):

• jest-stare:1.13.2
        └─ diff2html:2.7.0
              └─ lodash.merge:4.6.1

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Who would you want to see?

Bear in mind we need to consider

• the available env vars that give us info about the project
• the location where build artefacts are stored
• where the build reports are stored

also people may want to serve up their assets from else where, but we still need access to the test report, to work out what type of message we need to send (build failed/tests passed/tests failed)

Hello,

This is more a question than a issue..I've been trying all ways to find way to send a new line \n via custom-text field but it always sends the plain string . Do you know how can i achieve the new line via custom-text message?

Thanks,

Hi thanks for the awesome work!

The links to assets in my slack notifications are of the form:

https://78-undefined-gh.circle-artifacts.com/0/cypress/videos/imageSlugGenerator/ImageSlugGenerator.tsx.mp4

I'm not sure why theres an undefined in there.. does anybody know?

Thanks!

Hi @YOU54F, I'm also seeing this issue, which doesn't seem to be resolved?

When using

--ci-provider custom --custom-url "${GOCDURL}"

the resulting video artifact path in Slack is

https://xxxx/files/test_DOCKER_core_cypress_debug/7/run_all/1/run_all//var/go/rg_cypress/cypress/videos/PR/xx.spec.js.mp4

note the //var/go/rg_cypress is not needed, the relative path should work.

Also if --video-dir 'rg_cypress/cypress/videos' is added, there are no video urls output to Slack at all.

Please could this be looked into? Thanks

Hi, thanks for this great program. After running my cypress program i ue the clie for merging the mocha files and then running the slack alert. How can i configure to send to slack message only in case the test failed. I want to run the test every 15 mionutes to see that the site is o, and want to get in slack alerts only when there is a problem.
thanks

• npm publishing
• codeclimate
• coveralls
• travisci
• commitlint

Vulnerabilities

DepShield reports that this application's usage of lodash.memoize:3.0.4 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)

Occurrences

lodash.memoize:3.0.4 is a transitive dependency introduced by the following direct dependency(s):

• cypress-cucumber-preprocessor:1.11.0
        └─ @cypress/browserify-preprocessor:1.1.2
              └─ browserify:16.2.2
                    └─ browser-pack:6.1.0
                          └─ combine-source-map:0.8.0
                                └─ lodash.memoize:3.0.4

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Vulnerabilities

DepShield reports that this application's usage of debug:2.6.9 results in the following vulnerability(s):

• (CVSS 7.5) CWE-400: Uncontrolled Resource Consumption ('Resource Exhaustion')

Occurrences

debug:2.6.9 is a transitive dependency introduced by the following direct dependency(s):

• cypress:3.2.0
        └─ extract-zip:1.6.7
              └─ debug:2.6.9

• lint-staged:8.1.7
        └─ micromatch:3.1.10
              └─ extglob:2.0.4
                    └─ expand-brackets:2.1.4
                          └─ debug:2.6.9
              └─ snapdragon:0.8.2
                    └─ debug:2.6.9

• mocha-junit-reporter:1.22.0
        └─ debug:2.6.9

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Hi,
I have a couple of questions about the tool:

1. When using npx cypress-slack-reporter or index.ts is it possible to run only a subset of tests from package.json? E.g.
   "cy:run:pr": "cypress run --spec 'cypress/integration/PR/*'"

2. Is there a way to pass in the Slack channel results are posted to?

Thanks,
Robin

@YOU54F I have a question about, how I can create a custom message and if is possible add at what stage of my ci pipeline is running this and who triggered it (idk if with Gitlab this is possible). as for I have is
"slack-report": "npx cypress-slack-reporter --report-dir './cypress/report/output.json' --custom-url './final-report/output.html' --ci-provider custom --vcs-provider none --verbose true ".

what I tried to do with custom-url is to get that .html as a clickable attachment in the message to get redirected to that but my slack message is the following:

Please provide some suggestion and how I can integrate it with Bitbucket. In our case our version control and Build all on bitbucket.

@YOU54F I have written my own function to generate some report using mochawesome reporter. I have my html and json file in a specified report folder. I don't use typescript. Is there a way, I can add slack reporter as require and just give it my report directory as input? Can you pls help me with this?

it seems that artefact retrieval is not working anymore using

https://github.com/YOU54F/cypress-slack-reporter/blob/7fa3c8f0ea9b53fe1e955b18efd995a7e84898e0/src/slack/slack-alert.ts#L410

Will need to check docs and update function accordingly to construct new url

Nice easy one

• make a docusaurus v2 website init'd with typescript
• deploy to vercel (my account is oss and free)
• migrate readme to site, and make it less of a random brain fart

Hi,

I'm getting the error below upon running npx cypress-slack-reporter:

{"level":40,"time":1598962532830,"pid":10411,"hostname":"TribeStaffs-MacBook-Pro.local","msg":"Cannot find test report, so sending build fail message"}
{"level":30,"time":1598962533581,"pid":10411,"hostname":"TribeStaffs-MacBook-Pro.local","result":{"text":"ok"},"testStatus":{"totalSuites":0,"totalTests":0,"totalPasses":0,"totalFailures":0,"totalDuration":0,"reportFile":[],"status":"error"},"msg":"Slack message sent successfully"}

I've tried checking the verbose and it's the directory containing my generated report

ciProvider:- circleci
customUrl:- 
vcsProvider:- github
reportDirectory:- cypress/reports/generate-report
videoDirectory:- cypress/videos
screenshotDirectory:- cypress/screenshots

I created the reportDirectory above by performing the following commands:

> npx mochawesome-merge cypress/reports/mocha/*.json > cypress/reports/report.json

> npx marge cypress/reports/report.json -f report -o cypress/reports/generate-report

I'm not sure if I've overlooked anything (this is my first time working on cypress so I'm still exploring stuff). Here's my setup:

 "devDependencies": {
    "cypress": "^3.8.3",
    "cypress-multi-reporters": "^1.4.0",
    "cypress-slack-reporter": "^1.0.3",
    "gmail-tester": "^1.1.0",
    "mocha": "^8.1.3",
    "mochawesome": "^6.1.1",
    "mochawesome-merge": "^4.1.0",
    "mochawesome-report-generator": "^5.1.0"
  },

Thank You in advance for the help!

@YOU54F I think it will also be helpful to certain users, who can actually set some custom static message, which can be passed through the CLI itself?

do you have something like that? and let me know how this feature request sounds like? I can make a PR for that, incase makes sense.

cypress-slack-reporter does not support dotenv. I'm currently using dotenv. It would be better, if we have support for dotenv.

Vulnerabilities

DepShield reports that this application's usage of lodash.uniq:4.5.0 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)
• (CVSS 6.5) [CVE-2018-3721] lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutabl...

Occurrences

lodash.uniq:4.5.0 is a transitive dependency introduced by the following direct dependency(s):

• sonarqube-scanner:2.4.0
        └─ lodash.uniq:4.5.0

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Example script link gives a 404: https://github.com/YOU54F/cypress-slack-reporter/blob/master/cli/spec.ts

Vulnerabilities

DepShield reports that this application's usage of lodash.sortby:4.7.0 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)

Occurrences

lodash.sortby:4.7.0 is a transitive dependency introduced by the following direct dependency(s):

• jest:24.7.1
        └─ jest-cli:24.7.1
              └─ jest-config:24.7.1
                    └─ jest-environment-jsdom:24.7.1
                          └─ jsdom:11.12.0
                                └─ data-urls:1.1.0
                                      └─ whatwg-url:7.0.0
                                            └─ lodash.sortby:4.7.0
                                └─ whatwg-url:6.5.0
                                      └─ lodash.sortby:4.7.0

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Vulnerabilities

DepShield reports that this application's usage of lodash.once:4.1.1 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)

Occurrences

lodash.once:4.1.1 is a transitive dependency introduced by the following direct dependency(s):

• cypress:3.2.0
        └─ @cypress/xvfb:1.2.4
              └─ lodash.once:4.1.1

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Hello,

First of all, many thanks for the good job, your plugin is really usefull.
I would like to know if you could offer an option for a custom base URI, which allow a user to pass a custom BASE_URI for the videos and screenshots links.

For example if you put
npx cypress-slack-reporter --ci-provider none --vcs-provider none
Do you think it will be possible to offer a custom URI which allow to _artefactUrl
For the moment, I replace 'default' value in getArtefactUrl() but it would be better with a bash option, but I don't really understand how it works :)

Thanks in advance for your help.

Hi there,

I think CircleCI has updated their artifact links again, and am happy to submit a pull request to fix this, but wanted to check in with you first (in case I've got a setting wrong and this can be fixed in a different way).

I am on version 0.5.5.

I have CIRCLE_PROJECT_ID set.

The report link that is being posted into slack is something like this:

https://2334-92384-gh.circle-artifacts.com/0/cypress/reports/mocha-report/mochawesome-report/mochawesome.html

But the only way that I can access the report is via something like this:

https://2334-92384-gh.circle-artifacts.com/0/~/project/test/cypress/reports/mocha-report/mochawesome-report/mochawesome.html

So the generated link is missing this bit: ~/project/test/

My package.json is at the same level as that cypress folder.

Would it make sense to add an extra environment variable (or setting) to allow specifying this prefix?

Vulnerabilities

DepShield reports that this application's usage of lodash.clonedeep:4.5.0 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)
• (CVSS 6.5) [CVE-2018-3721] lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutabl...

Occurrences

lodash.clonedeep:4.5.0 is a transitive dependency introduced by the following direct dependency(s):

• @cypress/webpack-preprocessor:4.0.3
        └─ lodash.clonedeep:4.5.0

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

When a nightly run is executed I want it to send a slack message on failure only, which does work but the message on slack is incorrect. I see the bellow on failed builds:
Slack Message

CircleCi

.yml config

nightly:
    triggers: #use the triggers key to indicate a scheduled build
      - schedule:
          cron: "0 0 * * *" # use cron syntax to set the schedule
          filters:
            branches:
              only:
                - master
    jobs:
      - cypress/run:
          no-workspace: true
          name: Run All Tests
          parallelism: 2
          group: Nightly
          command: node cypress-retries.js Nightly
          post-steps:
            - run:
                when: always
                name: Merge MochaAwesome Reports
                command: npx mochawesome-merge --reportDir cypress/reports/mocha > mochareports/report.json
            - run:
                when: always
                name: Create mochawesome html report
                command: npx marge mochareports/*.json -f report -o mochareports
            - run:
                when: on_fail
                name: Slack report
                command: npx cypress-slack-reporter --verbose
            - store_artifacts:
                path: mochareports
            - store_test_results:
                path: cypress/reports
            - store_artifacts:
                path: cypress/videos/e2e
            - store_artifacts:
                path: cypress/screenshots/e2e

Send the message support for Github actions and bitbucket pipelines

#108

• typescript s3 uploader scripts and add to CLI
  • tsified
  • able to run in isolation
  • mock aws-sdk s3 upload function
  • tests
  • retrieve s3 links for test report/artefacts and inject into the slack report
  • uploading artefacts to s3
  • add to CLI
  • programatically run
  • Add into main slack-reporter script
  • provide CLI options to provide paths/credentials

When we use

npx cypress-slack-reporter --ci-provider jenkins

It is throwing an error as GIT_URL is not defined.

Which GIT_URL we need to mention in command?

https://github.com/YOU54F/cypress-slack-reporter/blob/6738b44448cb3ce3479da6729f8e28bde0b37ce2/src/slack/slack-alert.ts#L472

This message shows when there is no html file.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency @tsconfig/docusaurus to v1.0.7
• chore(deps): update dependency @types/bluebird to v3.5.38
• chore(deps): update dependency chai to v4.3.7
• chore(deps): update dependency cypress-multi-reporters to v1.6.3
• chore(deps): update dependency dotenv to v16.0.3
• chore(deps): update dependency s3-batch-upload to v1.5.2
• chore(deps): update dependency ts-jest to v27.1.5
• fix(deps): update dependency @cypress/browserify-preprocessor to v3.0.2
• fix(deps): update dependency @slack/client to v5.0.2
• fix(deps): update dependency @testing-library/cypress to v7.0.7
• fix(deps): update dependency @types/node to v10.17.60
• fix(deps): update dependency dotenv to v16.0.3
• fix(deps): update dependency mkdirp to v0.5.6
• fix(deps): update dependency mochawesome to v3.1.2
• fix(deps): update dependency prism-react-renderer to v1.3.5
• fix(deps): update dependency shelljs to v0.8.5
• fix(deps): update dependency shelljs to v0.8.5
• fix(deps): update dependency tsify to v5.0.4
• chore(deps): update babel monorepo (@babel/core, @babel/preset-env)
• chore(deps): update commitlint monorepo (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update cypress/base docker tag to v12.22.8
• chore(deps): update dependency @cypress/webpack-preprocessor to v5.17.1
• chore(deps): update dependency aws-sdk to v2.1379.0
• chore(deps): update dependency aws-sdk to v2.1379.0
• chore(deps): update dependency aws-sdk-mock to v5.8.0
• chore(deps): update dependency babel-loader to v8.3.0
• chore(deps): update dependency cypress to v9.7.0
• chore(deps): update dependency cypress-mochawesome-reporter to v3.4.0
• chore(deps): update dependency jest-stare to v2.5.0
• chore(deps): update dependency mocha-junit-reporter to v2.2.0
• chore(deps): update dependency papaparse to v5.4.1
• chore(deps): update dependency prettier to v2.8.8
• chore(deps): update dependency testdouble to v3.18.0
• chore(deps): update dependency ts-loader to v9.4.2
• chore(deps): update dependency ts-node to v10.9.1
• chore(deps): update dependency typescript to v4.9.5
• chore(deps): update dependency typescript to v4.9.5
• chore(deps): update dependency webpack to v5.83.1
• chore(deps): update dependency winston to v3.8.2
• chore(deps): update jest monorepo
• chore(deps): update node.js to v8.17
• fix(deps): update dependency @pact-foundation/pact to v9.18.1
• fix(deps): update dependency @pact-foundation/pact-web to v9.18.1
• fix(deps): update dependency @slack/types to v2.8.0
• fix(deps): update dependency @slack/web-api to v6.8.1
• fix(deps): update dependency @slack/webhook to v6.1.0
• fix(deps): update dependency @types/papaparse to v5.3.7
• fix(deps): update dependency axe-core to v4.7.1
• fix(deps): update dependency clsx to v1.2.1
• fix(deps): update dependency commander to v9.5.0
• fix(deps): update dependency create-jest-runner to ^0.12.0
• fix(deps): update dependency cypress to v3.8.3
• fix(deps): update dependency cypress to v7.7.0
• fix(deps): update dependency cypress-axe to ^0.14.0
• fix(deps): update dependency cypress-cucumber-preprocessor to v4.3.1
• fix(deps): update dependency cypress-failed-log to v2.10.0
• fix(deps): update dependency cypress-failed-log to v2.10.0
• fix(deps): update dependency cypress-multi-reporters to v1.6.3
• fix(deps): update dependency cypress-page-object to v1.1.0
• fix(deps): update dependency cypress-slack-reporter to v0.10.0
• fix(deps): update dependency cypress-slack-reporter to v1.5.3
• fix(deps): update dependency glob to v7.2.3
• fix(deps): update dependency jest-junit to v12.3.0
• fix(deps): update dependency lint-staged to v10.5.4
• fix(deps): update dependency mocha to v8.4.0
• fix(deps): update dependency mocha to v8.4.0
• fix(deps): update dependency mocha-junit-reporter to v2.2.0
• fix(deps): update dependency mochawesome to v6.3.1
• fix(deps): update dependency mochawesome to v6.3.1
• fix(deps): update dependency mochawesome-merge to v4.3.0
• fix(deps): update dependency mochawesome-report-generator to v5.2.0
• fix(deps): update dependency moment to v2.29.4
• fix(deps): update dependency prettier to v2.8.8
• fix(deps): update dependency serverless to v1.83.3
• fix(deps): update dependency slack-block-builder to v2.7.2
• fix(deps): update dependency sonarqube-scanner to v2.9.1
• fix(deps): update dependency sonarqube-scanner to v2.9.1
• fix(deps): update dependency tslint to v5.20.1
• fix(deps): update dependency uuid to v8.3.2
• fix(deps): update dependency wait-port to v0.3.1
• fix(deps): update dependency xlsx to ^0.18.0
• fix(deps): update docusaurus monorepo to v2.4.1 (@docusaurus/core, @docusaurus/module-type-aliases, @docusaurus/preset-classic)
• chore(deps): update cypress orb to v3
• chore(deps): update cypress/base docker tag to v16
• chore(deps): update cypress/base docker tag to v18
• chore(deps): update dependency @types/node to v18
• chore(deps): update dependency babel-loader to v9
• chore(deps): update dependency cypress to v12
• chore(deps): update dependency eslint to v8
• chore(deps): update dependency find-up to v6
• chore(deps): update dependency husky to v8
• chore(deps): update dependency jest-junit to v16
• chore(deps): update dependency lint-staged to v13
• chore(deps): update dependency mocha to v10
• chore(deps): update dependency mochawesome-merge to v4.3.0
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency sinon to v15
• chore(deps): update dependency ts-node to v10.9.1
• chore(deps): update dependency typescript to v5
• chore(deps): update node.js to v17
• fix(deps): update dependency @mdx-js/react to v2
• fix(deps): update dependency @pact-foundation/pact to v11
• fix(deps): update dependency @testing-library/cypress to v9
• fix(deps): update dependency commander to v10
• fix(deps): update dependency cypress-axe to v1
• fix(deps): update dependency cypress-slack-reporter to v1.5.3
• fix(deps): update dependency del to v7
• fix(deps): update dependency glob to v10
• fix(deps): update dependency mkdirp to v3
• fix(deps): update dependency pino to v8
• fix(deps): update dependency prism-react-renderer to v2
• fix(deps): update dependency serve to v14
• fix(deps): update dependency serverless to v3
• fix(deps): update dependency sonarqube-scanner to v3
• fix(deps): update dependency uuid to v9
• fix(deps): update dependency wait-port to v1
• fix(deps): update react monorepo to v18 (major) (react, react-dom)
• 🔐 Create all rate-limited PRs at once 🔐

⚠ Dependency Lookup Warnings ⚠

• Renovate failed to look up the following dependencies: Failed to look up npm package @you54f/cypress.

Files affected: cypress-edge/package.json

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency @types/node to v12.20.55
• chore(deps): update dependency ts-jest to v27.1.5
• chore(deps): update dependency cypress to v7.7.0
• chore(deps): update dependency cypress to v9.7.0
• chore(deps): update dependency standard-version to v9.5.0
• chore(deps): update commitlint monorepo to v17 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency mochawesome to v7
• chore(deps): update dependency mochawesome-report-generator to v6
• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• fix(deps): update dependency @types/pino to v7
• fix(deps): update dependency globby to v13

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Vulnerabilities

DepShield reports that this application's usage of lodash.get:4.4.2 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)
• (CVSS 6.5) [CVE-2018-3721] lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutabl...

Occurrences

lodash.get:4.4.2 is a transitive dependency introduced by the following direct dependency(s):

• sonarqube-scanner:2.4.0
        └─ lodash.get:4.4.2

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Hello,

I'm getting this error when trying to run npx cypress-slack-reporter --vcs-provider none --ci-provider none --verbose

I'm trying to run it from my local machine, my slack webhook works. I have no idea why I get this issue.

 ciProvider:- none
 customUrl:- 
 vcsProvider:- none
 reportDirectory:- mochareports
 videoDirectory:- cypress/videos
 screenshotDirectory:- cypress/screenshots

(node:11102) UnhandledPromiseRejectionWarning: Error: TypeError: Cannot read property 'split' of undefined
    at Object.exports.slackRunner (/home/vladmocan/unity-xp-qa/node_modules/cypress-slack-reporter/bin/slack/slack-alert.js:167:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:11102) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11102) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I understand that gitlab isn't supported yet. But I'm purely using this to send a brief PASS/FAIL to my Slack channel.
It seems to be working locally after running these steps.

e2e-tests:
  script:
    - npm ci
    - npm run e2e:ci 
    - npm run e2e:consolidate:report # consolidate test reports
    - npm run e2e:report:send # sends consolidated report to Slack

And I have a before-script to export the SLACK_WEBHOOK_URL

variables:
  SLACK_WEBHOOK: https://hooks.slack.com/services/XXXX

before_script:
  - export SLACK_WEBHOOK_URL=$SLACK_WEBHOOK

But for some reason I'm getting this error in my gitlab ci

> npx cypress-slack-reporter --report-dir mochareports/mochawesome.json --ci-provider none
{"level":30,"time":1618502686655,"pid":591,"hostname":"runner-x8zlwexr-project-25494770-concurrent-0","data":{"attachments":[{"color":"#36a64f","fallback":"Report available at mochareports/mochawesome.json/mochawesome.json","text":"Total Passed:  26","actions":[{"type":"button","text":"Test Report","url":"mochareports/mochawesome.json/mochawesome.json","style":"primary"},{"type":"button","text":"Build Logs","url":"undefined","style":"primary"}]},{"text":"","color":"#36a64f"}],"unfurl_links":false,"unfurl_media":false},"msg":"passing run"}
{"level":50,"time":1618502686660,"pid":591,"hostname":"runner-x8zlwexr-project-25494770-concurrent-0","e":{},"msg":"Unknown error occurred whilst sending slack message"}
(node:591) UnhandledPromiseRejectionWarning: Error: Error: An error occurred whilst sending slack message
    at Object.exports.slackRunner (/e2e-tests/node_modules/cypress-slack-reporter/bin/slack/slack-alert.js:162:15)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:591) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:591) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Have you come accross this issue by any chance?

Pretty sure circleci have deprecated the old endpoint we used to use to construct the links to the test artefacts.

Will dig out the doc links and fill in with more detail later :)

v0.9.0

v1.0.0

npm install cypress --save-dev
npm install mochawesome --save-dev
npm install mochawesome-merge --save-dev
npm install mochawesome-report-generator --save-dev
npm install cypress-multi-reporters --save-dev
npm install cypress-slack-reporter --save-dev

export SLACK_WEBHOOK_URL=XXXXXXXXXXXXX

npm run cy:run --record --key pixotope-cloud

mkdir cypress/reports/mochareports/
mkdir cypress/screenshots
npx mochawesome-merge ./cypress/reports/mocha/*.json > cypress/reports/mochareports/output.json

npx marge cypress/reports/mochareports/output.json -f pixotope-cloud-report -o cypress/reports/mochareports/


npx cypress-slack-reporter \
--custom-url=${HTTP_URL} \
--report-dir=cypress/reports/mochareports \
--screenshot-dir=cypress/screenshots \
--video-dir=cypress/videos \
--ci-provider=aws \
--verbose

I wrote a feature that would allow users to upload their files to an S3 bucket (public read only), and serve up a link in the slack message.

For various reasons, I never wired it up, but the code is there

https://github.com/YOU54F/cypress-slack-reporter/blob/master/src/uploads3/upload.new.ts

Drop me a thumbs up if you want to see the feature and it would be useful.

I went for public read only, as I don't how how people will be able to view assets served from a private bucket, from the slack message.

Vulnerabilities

DepShield reports that this application's usage of lodash.isfunction:3.0.9 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)

Occurrences

lodash.isfunction:3.0.9 is a transitive dependency introduced by the following direct dependency(s):

• mochawesome:3.1.1
        └─ mochawesome-report-generator:3.1.5
              └─ lodash.isfunction:3.0.9

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

I tried to do everything like the README and set the export and everything but it keep me giving some "invalid build specification" with undefined on the URL.

Maybe because the new changes to the URL artifact method? or I'm doing something wrong on export?
My export:
export CIRCLE_PROJECT_ID=${CI_PROJECT_ID}

Any help will be much appreciated! Thank you in advance!

Below the result when I try to access:

Hi,

If we will run e.g "scripts": { "slack-report": "./node_modules/.bin/cypress-slack-reporter-full", }

Which have:

 mochawesomeReporterOptions: {
            reportDir: "cypress/reports/mocha",
            quiet: true,
            overwrite: true,
            html: false,
            json: true
        }

Overwrite is set to true, so if user will have more then one test the json file will be always overwritten, and we can't merge couple of reports into one.

Could you check it?

https://github.com/LironEr/cypress-mochawesome-reporter is awesome.

It would save a fair few bits of faff for the user

should we support and promote integrations with this over adam grubers original package

Hi!
I'm having issues running the execution part npx cypress-slack-reporter

/home/ubed/Documents/Playground/cypress-slack/node_modules/cypress-slack-reporter/bin/slack/slack-alert.js:167
        throw new Error(e);
              ^

Error: TypeError: Cannot read property 'split' of undefined
    at Object.exports.slackRunner (/home/ubed/Documents/Playground/cypress-slack/node_modules/cypress-slack-reporter/bin/slack/slack-alert.js:167:15)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

I already export the webhook

Steps performed

yarn add cypress-slack-reporter --dev
yarn add mochawesome --dev
yarn add mochawesome-merge --dev
yarn add mochawesome-report-generator --dev
yarn add cypress-multi-reporters --dev

Created Slack app and Webhook URL / Oauth
added code snippets for cypress.json and reporterOpts.json
after running test, I combine test report with this command
npx mochawesome-merge cypress/reports/mocha/mochawesome.json > mochareports/report.json
after that, I generate report with this command
npx marge mochareports/report.json -f report -o mochareports
and running cypress-slack-reporter
npx cypress-slack-reporter

System Info
Arch Linux
Cypress : 8.3.0
"cypress-slack-reporter": "^1.2.1",
"cypress-multi-reporters": "^1.5.0",
"mochawesome": "^6.2.2",
"mochawesome-merge": "^4.2.0",
"mochawesome-report-generator": "^5.2.0"

Can you help me to solve this problem?

Hello,

I'm trying to configure your plugin w Circle CI but I stuck on bin files which you added to the .gitignore.

To be honest it is not easy to setup all configuration, I would also recommend more step by step README :)