Anyone know why cypress-slack-reporter doesn’t exist anymore on bahmutov GitHub ?

@gray-kilobyte-89541 do you know why ?

I did open a discussion on the Cypress project. Because I'm getting so little information on what is going on, I wasn't sure I had enough to create an issue from it. https://github.com/cypress-io/cypress/discussions/25402

Cypress - /Users/bouchard/workspace/clie...

Sure it does

$ npm info cypress-slack-reporter

cypress-slack-reporter@1.5.2 | MIT | deps: 8 | versions: 59
A slack reporter for mochawesome reports generated by Cypress or other test frameworks using Mocha, for runs generated on CircleCI
https://github.com/you54f/cypress-slack-reporter#readme

keywords: cypress, slack, circleci, reporter, mocha, mochawesome, mochawesome-merge, marge

bin: cypress-slack-reporter, cypress-slack-reporter-full

dist
.tarball: https://registry.npmjs.org/cypress-slack-reporter/-/cypress-slack-reporter-1.5.2.tgz
.shasum: 5c7ee822e77edfa7d4b1f8d6bd64774b6bb7234c
.integrity: sha512-NItMSC+AeIOGktYoYz8aTW6KjhdjUtSmeOggbCPbOaax+tORJaDApLZEM1GmGfEtAsr+Me3enbpdp/ymE5Ds6A==
.unpackedSize: 67.2 kB

dependencies:
@slack/types: ^2.0.0      @types/commander: ^2.12.2 commander: ^7.0.0         dotenv: 16.0.0            
@slack/webhook: ^6.0.0    @types/pino: ^6.0.1       del: ^6.0.0               pino: ^6.2.1              

maintainers:
- you54f <yousafn@gmail.com>

dist-tags:
latest: 1.5.2  

published a month ago by you54f <yousafn@gmail.com>

and

npm home cypress-slack-reporter

opens the github page

Yeah but github link send to a 404 ?

I talk about your version

github.com/bahmutov/cypress-slack-reporter

It opens the GitHub page of cypress-plugins, and the doc of cypress-slack-reporter doesn’t exist on the normal version (only for the old one)

Do you know if it works with GitLab ?

My plugin is called https://github.com/bahmutov/cypress-slack-notify

Hello all, after upgrading to cypress 12.1.0, it shows me all time "Default blank page. This page was cleared by navigating to about:blank." All my tests are now failing, how can i solve this?

If the Cypress runner URL switches during spec execution from

http://localhost:XXXX/__/#/specs

to a URL from your tests, is that an indication that frame busting has happened somewhere in the flow? I posted yesterday about seeing a test crash trying to login with no console or log output (at least none that seems significant to me). And I'm wondering if this behavior plus the URL points to framebusting?

Question for doing API tests with cypress. I’ve been adding my functions and expects to my commands.ts and calling the functions inside my test file. The issue with this is that I’m noticing that my commands.ts file could get pretty long. Is there another way anyone has done API testing with cypress with cleaning up commands.ts?

My company split our commands.js file into multiple files, and then point all those files in our support file (which they kinda talk about here: https://docs.cypress.io/api/cypress-api/custom-commands) i.e. we have something like

commandsOne.js

,

commandsTwo.js

, etc. under our

cypress/support

folder then, in our

cypress/support/e2e.js

file, we import them

// ***********************************************************
// This example support/e2e.js is processed and
// loaded automatically before your test files.
//
// This is a great place to put global configuration and
// behavior that modifies Cypress.
//
// You can change the location of this file or turn off
// automatically serving support files with the
// 'supportFile' configuration option.
//
// You can read more here:
// https://on.cypress.io/configuration
// ***********************************************************

// Import commands.js using ES2015 syntax:
import './commandsOne'
import './commandsTwo'

then you can do

cy.functionFromOne()

and

cy.functionFromTwo()

without any issue There's probably something minorly different for .ts files, but the idea should be the same, and/or detailed in that link. Hope this helps!

Awesome thanks so much! I'll take a look at that

When I write npx cypress open in the terminal it starts and crashes immediately

Hello guys, is anyone using reportportal with cypress within their testing framework? I am trying to pass the reportportal plugin into setupNodeEvents but I am having issues with ts modules?

Hey Everyone, I was trying to make an app which will tell us whether a link is valid or invalid. What I was doing is simply requesting for that link and if it gives the status as 200 it is valid otherwise invalid. But I am facing problem with linkedIn_profile URLs because it does not care whether a URL is valid or invalid and always give status as 999. Also here I cannot make use of linkedIn api as we do not have the access to search a user in linkedIn api. So, please can anyone help me with this?

Hey Everyone

check your baseurl in cypress config file

Add

testIsolation: false,

in cypress.config

Hi guys! I can mix test front-end with api testing? All the stuffs is maded on the front-end (I know that terrible but I cant fix it LOL) its some endpoints that I can use to do something on the back-end

When I try and login to cypress from the testing app, then it forever gets stuck on "Waiting for you to log in"

This is the same from the testing browser login and the Cypress app login

I fixed the above by changing my default browser from Brave to Chrome

Hey community. Have a question for you. I have created a task for mySQL connection and I run a query using cy.task() I need to verify the results after that but the thing is, I need to wait until an external service returns the data, which can take up to 3 minutes. (Horrible I know) my command is: cy.task("executeSql", "Select * from TABLE where id = '" + myID + "';" ).then($result => { expect($result.serviceID).to.not.be.null }) I would like to avoid putting a cywait(180000) and I was wondering how can I set a 3 minute timeout, so it keeps retrying the query until it gets a value or hits the limit. Is there a native way to do so? Or should I use recurse. My my concern is that I don´t have to retry the assertion but the task

Yes, you can use cy.request() to create steps that interact with the API directly. https://docs.cypress.io/api/commands/request Or you can use cy.intercept() to catch your API requests in real time and modify/mock the responses https://docs.cypress.io/api/commands/intercept#Syntax And you can definitely do that in the middle of your front end test run.

cy.task

does not retry. But you can use to do it https://github.com/bahmutov/cypress-recurse

Was aiming for that. I already use it for email fetch. Thankk you!