Error: EISDIR: illegal operation on a directory

[tanuj-vishnoi]

Current behavior:

Error message is thrown

Error: EISDIR: illegal operation on a directory, 
open 'C:\Users\*********\AppData\Roaming\Cypress\cy\production\projects\CyDemo-f6363983d1108dd01027bb4ab06585aa\bundles

Desired behavior:

On clicking signIn button user should land on dashboard page

How to reproduce:

Submit userId and password in respective fields and hit signIn

Test code:

function loadFixture() {
    cy.fixture('login').as('loginJson')
}
describe('Login', function () {
    beforeEach(function () {
        loadFixture()
    })

    before(function () {
        cy.visit('https://*************.com');
    })

    it('It Should load in to the application', function () {
        cy.title().should('contain', 'xyz');
    })

    it('It Should enter credentials and login', function () {
        cy.get('#Username').type(this.loginJson.masterCoder.email).should('have.value', this.loginJson.masterCoder.email);
        cy.get('#Password').type(this.loginJson.masterCoder.password).should('have.value', this.loginJson.masterCoder.password);
        cy.get('.button-label.ng-binding').and('be.visible').click();
    })
});

Additional Info (images, stack traces, etc)

• Operating System: Windows10 64bit
• Cypress Version: 1.4.1
• Browser Version: 63.0.3239.132

[devopsOCL]

Any resolution to this ? I am seeing an exact issue but with a different directly listing ....

[jennifer-shehane]

Hey @tanuj-vishnoi, you mentioned you are using Cypress Version 1.4.1, could you verify the issue by running cypress version? Because this is a very old version.

Also, can anyone provide a way to reproduce this? That would be the fastest way to get your issue directly addressed.

[hrk15]

@jennifer-shehane Hi I am facing the same issue. In my case I added a configuration file to my project in which I am changing the supportFile path and url, which I am able to do but when I run the tests this error comes.

Steps:

1. created a new configuration file
2. set the configuration file using --env configFile=filename
3. run the test script

[jennifer-shehane]

Hey @hrk15, could you elaborate more on this step?

set the configuration file using --env configFile=filename

Could you provide what you have in your cypress.json file?

[hrk15]

@jennifer-shehane
my cypress.json file

{ 
    "chromeWebSecurity":  false,
    "env": {
        "name" : "prod"
    },
    "pageLoadTimeout" : 120000,
    "defaultCommandTimeout" : 10000,
    "baseUrl" : "product-url",
    "reporter": "mocha-allure-reporter",
    "reporterOptions": {
        "targetDir": "allure-results"
    }
}

my custom config.json content

{ 
    "chromeWebSecurity":  false,
    "env": {
        "name" : "prod"
    },
    "pageLoadTimeout" : 120000,
    "defaultCommandTimeout" : 10000,
    "baseUrl" : "product-url2",
    "reporter": "mocha-allure-reporter",
    "reporterOptions": {
        "targetDir": "allure-results"
    },
    "supportFile": "cypress/support/step_definitions/"
}

[alexborovkov]

@jennifer-shehane I also face this issue after updating to Cypress 3.2.0. Some of the tests failed with this error. As I understand the root cause - when I load fixture using .route(/notifications/, "fixture:notifications this error appeared because I have folder and file with same name notifications in project structure. When I expicitly set extension like notifications.json, it fixed the problem. But I am not sure why it is worked in previous Cypress version.

[brian-mann]

@AleksandrBorovkov this has already been fixed in 3.3.0 and pending release. The original issue is here: #3739

Closing this as a duplicate.

[jennifer-shehane]

@AleksandrBorovkov Your issues has indeed already been fixed in 3.3.0 and pending release from here #3739

But, this original issue was opened before the fixture regression and is unrelated to this fix. Reopening.