Hi! I have a problem with the

selectFile()

API. Despite me being on 9.4.1, neither

cy.document().selectFile

nor

cy.get('input[type=file]').selectFile

are defined. Did I miss some config?

Hi, I want to save access token from the api call with custom command into environmental variable, but it does not work. Doesn't it work in this way?

Cypress.Commands.add('getAccessToken', () => {
    const options = {
        method: "POST",
        url: '/token.json',
        form: true,
        body: {
          grant_type: "password",
          username: Cypress.env('username'),
          password: Cypress.env('pass'),
          client_id: Cypress.env('client_id')
        }
      };
      
      cy.request(options)
          .then(response => {
              expect(response.body).to.have.property('access_token');
              Cypress.env('accessToken', response.body.access_token);
      });
    }

how do you know it doesn't work? if you are trying to access this env in other spec file, then it might not work, because

Cypress.env

appears to only set/change env variables for one spec file https://docs.cypress.io/api/cypress-api/env#Why-is-it-Cypress-env-and-not-cy-env

you can ensure that 'accessToken' is set by reading it after setting it by

Cyress.env('accessToken')

https://docs.cypress.io/api/cypress-api/env#Name-and-Value > Scope > > Remember, any changes that you make to environment variables using this API will only be in effect for the remainder of the tests in the same spec file.

it works in the same spec file, that is true. I was mistakenly thinking

Cypress.env

is set as a global variable which could be updated in env file... Thanks @User As my token expires, ideally, I was thinking to get it once and use it for whole test session...

you can try setting such env variable through Node's

process.env

, but that would require to use Cypress plugin (not command) https://docs.cypress.io/api/plugins/writing-a-plugin

Will investigate this way further, thanks for advice!

When using

cy.get('#element').click()

, what's happening in the background? We're encountering an error which only happens when the cypress test runs. If we mimic its behavior manually we don't have any issues. Here is [the test](https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/8174/files#diff-a00eb0a05c99c0a2bdfd49f3f79145e86aeeb09e909c68c3c8c42f3cbda2841dR52-R71) Here is the page of the deploy environment that has [the component being tested](https://ibmdotcom-web-components-experimental.s3.us-east.cloud-object-storage.appdomain.cloud/deploy-previews/8174/iframe.html?id=components-cloud-masthead--default) The failure:

dds-masthead | cloud platform (desktop)
    ✓ should have url for IBM logo (3613ms)
    ✓ should have cloud platform name (4120ms)
    ✓ should load top-nav with no more than one active item (4079ms)
    (Attempt 1 of 3) should have tabbed-interface megamenus
    (Attempt 2 of 3) should have tabbed-interface megamenus
    1) should have tabbed-interface megamenus
    ✓ should have functioning search bar with typeahead (7118ms)
    ✓ should have contact, login, and create-account CTAs (5095ms)


1) dds-masthead | cloud platform (desktop)
       should have tabbed-interface megamenus:
     AssertionError: Timed out retrying after 90000ms: expected '<div#panel-0-0>' to be 'visible'

This element `<div#panel-0-0>` is not visible because its parent `<dds-cloud-megamenu-right-navigation>` has CSS property: `visibility: hidden`
      at Context.eval (http://localhost:8081/__cypress/tests?p=tests/e2e-storybook/cypress/integration/masthead/cloud/cloud-masthead.e2e.js:150:33)

You shouldn't need to add anything to the config, only fixtures (or whatever you are needing to reference). Can you provide a reproducible example?

I just tried it in a clean [repository](https://github.com/sweidac/cypress-selectFile) and it works there. Unfortunately I can't share my original code, so I'll have to find it out for myself.

Hello , i need some help understanding how i do i get access to this property value, , im doing my-data-cy.should('exist').and('has.value', 'MyValue') i got the path correctly implemented, i have access to the mat-toogle-group, but still i cannot get the [value] proprety to make the assertion can some one help me ?

its returning ' '

instead of MyValue

and the test fail

Does anyone have an idea why clicking would cause a behavior when Cypress is running, but not in a "normal" scenario?

Got a weird issue happening. My application is using decorators, and while running unit tests with Cypress, I get this error

Error: Webpack Compilation Error
./src/resources/custom-attributes/after-render.js
Module build failed (from C:/Users/xxxxx/AppData/Local/Cypress/Cache/9.4.1/Cypress/resources/app/node_modules/babel-loader/lib/index.js):
SyntaxError: E:\xxxxx\form-builder\src\resources\custom-attributes\after-render.js: Support for the experimental syntax 'decorators-legacy' isn't currently enabled (3:1):

  1 | import { INode, bindable, BindingMode, customAttribute } from 'aurelia';
  2 |
> 3 | @customAttribute({
    | ^
  4 |     name: 'after-render'
  5 | })
  6 | export class AfterRender {
 @ ./src/resources/custom-attributes/index.js 21:19-44
 @ ./src/start.js
 @ ./src/FormVersion.spec.js

It looks like Webpack is trying to load in my file but complains about decorators with babel (note, I'm not using webpack in our application, so this is a Cypress error). I have a babel.config.json with this configuration

{
  "presets": [
    [
      "@babel/preset-env",
      {
        "loose": true,
        "exclude": [
          "@babel/plugin-proposal-dynamic-import"
        ]
      }
    ]
  ],
  "plugins": [
    [
      "@babel/plugin-proposal-decorators",
      {
        "legacy": true
      }
    ],
    [
      "@babel/plugin-proposal-class-properties",
      {
        "loose": true
      }
    ],
    "@babel/plugin-syntax-dynamic-import"
  ]
}

So it should definitely be working with the decorators. Anybody have any clues? I'm about to open a bug with it, but wanted to run it here first.

Clicking provides actionability similar to how a User would interact. For example, before typing into a form, a User will typically need to click the input box prior to typing. Is this what you mean by "normal" scenario?

@User I mentioned you in the thread I started above - just wanted to make sure you saw that

TypeScript and Docker - compilation error

Can you try

cy.get('[data-cy="my-data-cy"]').should('exist').and('has.value', 'MyValue')

hello @User if if put [value]="myValue" it returns undefined

but value="MyValue" works

MyValue came from parent to child, so maybe in the tests im getting undefined

Hello, I am accessing the UI application I want to test via a kubernetes ingress controller and although I am able to access the application manually via my browser (Chrome, MacOS) I am unable to access the app via the automated browser that Cypress uses

The app is normally accessible via a url like 'http://ui.localhost' but when I try to navigate to this url from inside the cypress browser I do not receive a response

hmm.. you may want to try aliasing. Is it possible to provide a reproducible example that I can test?

Not getting value

i was just running into this problem and clearing my .next cache fixed it!

hey @User , my main objective was to test if a inside a was active in a form and have certain value, for that i was trying to get the value from the class directive , but what i did was , instead i "reach" to the button itself and check if as class active and the value i want, and now the test is ok. 🙂 !!