With Cypress, you can easily create tests for your modern web applications, debug them visually, and automatically run them in your continuous integration builds.

Cypress Community

hello, do you have any recommendations for file upload without the html attribute being <input type=file>, but rather being <div> element?

Hey, i am trying to debug why `res.body.payload` is sometimes empty (as my comment says). So i added `logToCLI` method in a plugin and i want to call it by `cy.task`.
```js
Cypress.Commands.add('confirmTestUserRegistration', (email) => {
    return cy.getLinkFromEmail(email, 'Account activation', '/pages/confirm-registration').then((url) => {
      cy.intercept('/api/users/confirm-registration', (req) => {
        req.continue((res) => {
          console.log('[confirmTestUserRegistration()] /res:', res);
          if (!res.body.payload) {
            cy.task('logToCLI', {
              message: `confirmTestUserRegistration() no 'res.body.payload' found!`,
              value: res,
            });
          }

          // TODO: [issue] sometimes `res.body.payload` is undefined due to 401 response code
          return expect(res.body.payload.isUserConfirmed).to.be.true;
        });
      }).as('confirmRegistration');

      cy.visit(url);
      cy.wait('@confirmRegistration');
      cy.contains(
        '[data-cy="message:registration-confirmation-succeeded-hint"]',
        'You can now log in to your new account.'
      );
    });
  });
```
The plugin code is fairly simple:
```js
module.exports = (on) => {
    on('task', {
        logToCLI ({ message, value }) {
            console.log('[Cypress CLI]', message, value);
            
            return null;
        }
    })
}
```
, but Cypress throws error:
> **CypressError: Cypress detected that you returned a promise from a command while also invoking one or more cy commands in that promise.
> **
> The command that returned the promise was:
> 
>   > `cy.wait()`
> 
>  The cy command you invoked inside the promise was:
> 
>    > `cy.task()`

Why do i receive the error if i don't use any promise? Is it about nesting?

Update: i prepended `cy.task(..)` call with `return` and error no longer appears (i don't exactly know why though - i'd be grateful for some explanation regarding how Cypress behaves here). However, i don't see a log inside CLI, like the task itself didn't run 🤔 I didn't notice other errors.

I haven't been able to look at this example in detail, but this video from Gleb might be helpful, especially around 5:45  where he shows an example of getting this error without explicitly using a promise https://www.youtube.com/watch?v=9AF-lcvh1dk

It might be that Cypress is not sure whether to `return expect(res.body.payload.isUserConfirmed).to.be.true` or wait for `cy.task`to complete. Do you definitely need to return the `expect` stuff? This is not a part of Cy I'm super familiar with but hopefully Gleb's video gets you on the right track. Happy to come back to this in the next few days when I have more time too.

Thanks for reply. I watched the YT film, but AFAIK in my case Cypress should rather not be  confused what to do, because i have `if` statement. But maybe the issue is that unless the `cy.task` is prepended by `return` then Cypress still has dillema like "Ok, condition met, so do `cy.task`, but there is also `expect` outside the condition - so what to do? Oh, i'll throw error, because i don't know.". If i add `return` before `cy.task` the error is gone, because i think Cypress should know at this moment that `cy.task` returns a promise-alike, which is also returned, so no `expect` is going to happen.

What's more confusing for me (as i at least has some clue about what's reason for `cy.task` error) - why the `logToCLI` task doesn't log anything to Node's console? I return `null` from it, because i don't do any async stuff in there.

why do you want to use other element than specific input for file upload?

you can hide the input and programmatically trigger it as user interacts with the div

Hello guys is there a way to export a variable with a string into another it function? I've tried to export and import it but it didn't work with module.exports. I always got undefined.

what exactly do you mean? and show the code of what you have tried

you can import something from a module to your spec file

you can also share value within spec context via alias or `this` (if it's inside non-arrow function)

when I cy.log the imported variable it gives me undefined but I need the string

yea I tried logging this but that doesn't work either

also, why do you export something from `it`?

I thought its ok to do that (I'm new to cypress)

if you want to have some helper function then use Commands API
https://docs.cypress.io/api/cypress-api/custom-commands

you can have reusable function as Command

I'm not sure I understand your question. Can you provide a code block for reference and tell me a little more about your use case?

Hi I'm using Cypress to test our app on Production (against best practices) and we're running into an issue where we've implemented logic to have our app open a new tab to the page instead of redirecting if we find out its embedded. When we run cypress headless or using a testrunner, the test steps run to login and instead of redirecting our app to a specific page, it opens that page by design. 

My question is how do i disable this behavior on the app if i know Cypress is the one requesting the app? Is there a user agent that Cypress sets when it makes requests to the app that i can then use in our code to detect and disable that behavior?

https://discord.com/channels/755913899261296641/763105090679865354/934533240625197137
bump

Hi, you can check for `window.Cypress` in your code if you want to do anything specific when Cypress is present

neverminded, I think I was checking the wrong element. Thanks anyway.

No worries! Let us know if you have any additional questions!

Wanted to circle back to say this has been resolved with v9.4.0. See our Changelog here: https://docs.cypress.io/guides/references/changelog#9-4-1