Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing at Redirect #1681

Closed
ghost opened this issue May 4, 2018 · 8 comments
Closed

Failing at Redirect #1681

ghost opened this issue May 4, 2018 · 8 comments
Labels
topic: 😳 whoops there is no test to run Error msg: "Whoops there is no test to run"

Comments

@ghost
Copy link

ghost commented May 4, 2018

Current behavior:

I am accessing my local project at http://drupal.docker.localhost.website.com:8000/ and then I am doing a form submission. Upon form submission it goes to another url (same domain) http://drupal.docker.localhost.website.com:8000/after/form/submit and instead of staying on the page, it suddenly goes to the page with "Sorry, there are no test to run"

a few notes

  • I am on a corporate proxy
  • I was having this issue accessing an external url (uat.oursite.com) however now I am getting this odd functionality for my localhost as well
@jennifer-shehane
Copy link
Member

Could you try running the current workarounds, specifically about "environment variables" with corporate proxy as outlined in #1469 and let me know if this resolved your issue?

@jennifer-shehane jennifer-shehane added the stage: awaiting response Potential fix was proposed; awaiting response label May 4, 2018
@ghost
Copy link
Author

ghost commented May 4, 2018

@jennifer-shehane

  • I attempted to set NO_PROXY to prevent hitting corporate proxy - same behavior
  • I downloaded via the direct download and that doesnt even run my test, says: "Whoops, we can't run your test" or it models the same behavior as mentioned before...

I have no_proxy set in environment and in my project... could it be something else?

@kuceb
Copy link
Contributor

kuceb commented May 7, 2018

@jasonellington are you specifically having problems on localhost subdomains?

@ghost
Copy link
Author

ghost commented May 7, 2018

@bkucera although i havent tried it on a regular domain, i was not having this problem until recently. No significant changes to my cypress code were made, however there were a few commits to our develop branch that i merged in to my testing branch...

I am testing a e-commerce process where someone is adding a product to their cart. In my local environment i cannot get passed the homepage and filling out a form and browsing products... however if i used our uat.website.com (external site) i can get further along the shopping process but the same behavior still occurs... I am unsure if this information helps but I am very stuck on this problem

@jennifer-shehane jennifer-shehane added stage: needs investigating Someone from Cypress needs to look at this and removed stage: awaiting response Potential fix was proposed; awaiting response labels May 7, 2018
@ghost
Copy link
Author

ghost commented May 8, 2018

@jennifer-shehane @bkucera
here is the code I am executing:

it('test 1', function() {
    cy.visit('http://docker.localhost.website.com:8000/')
    cy.get('#button').click()
    cy.get('#product').select('product_1')
    cy.get('#zipcode').type('10003').
    //failing after this call
    cy.get('#form').submit().debug()

    cy.get('#age').select('60')
  })

here is a statement in the log of the debug on the command line that looks suspicious

cypress:server:files specPattern for test files is undefined +0ms

@jennifer-shehane
Copy link
Member

cypress:server:files specPattern for test files is undefined

This message just means that you did not pass anything to the --spec flag when running your tests.

@ghost
Copy link
Author

ghost commented May 9, 2018

@jennifer-shehane is there any configuration or project configuration that could be causing the weird functionality? Anything I can look for in the logs? Does Cypress proxy all traffic even if my url is in my no_proxy configuration?

@jennifer-shehane
Copy link
Member

Since this issue hasn't had activity in a while, we'll close the issue until we can confirm this is still happening. Please comment if there is new information to provide concerning the original issue and we'd be happy to reopen.

@jennifer-shehane jennifer-shehane removed the stage: needs investigating Someone from Cypress needs to look at this label Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: 😳 whoops there is no test to run Error msg: "Whoops there is no test to run"
Projects
None yet
Development

No branches or pull requests

2 participants