Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cypress still in use?

See original GitHub issue

Your Question

Website URL Path: https://github.com/corona-warn-app/cwa-website/blob/master/README.md#testing
Question: Is cypress still being actively used by the Open Source Team for website testing of https://www.coronawarn.app/ ?

https://github.com/corona-warn-app/cwa-website/blob/master/cypress/integration/hotline_spec.js fails in cypress because the hotline phone number was updated without updating the cypress test routine.

  Running:  hotline_spec.js                                                                 (3 of 3)


  Test Hotline phone number
    1) Verify App and TAN Hotline


  0 passing (5s)
  1 failing

  1) Test Hotline phone number
       Verify App and TAN Hotline:
     AssertionError: Timed out retrying: Expected to find content: '+49 800 7540001' within the element: <div.link-item.col-6.col-md-4> but never did.
      at Context.eval (http://localhost:8000/__cypress/tests?p=cypress\integration\hotline_spec.js:10:53)

Issue Analytics

State:
Created 2 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

MikeMcC399commented, Jul 21, 2021

@svengabr The cypress tests are now completing successfully, so this issue can be closed.

  (Run Finished)


       Spec                                              Tests  Passing  Failing  Pending  Skipped
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ √  applink_spec.js                          00:08        3        3        -        -        - │
  ├────────────────────────────────────────────────────────────────────────────────────────────────┤
  │ √  blog_spec.js                             00:08        2        2        -        -        - │
  ├────────────────────────────────────────────────────────────────────────────────────────────────┤
  │ √  hotline_spec.js                          00:01        1        1        -        -        - │
  ├────────────────────────────────────────────────────────────────────────────────────────────────┤
  │ √  pages/eventRegistration.js               00:33        6        6        -        -        - │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
    √  All specs passed!                        00:50       12       12        -        -        -

0reactions

svengabrcommented, Jul 21, 2021

Cypress was updated lately with some new pull requests that were approved. @MikeMcC399 do you think we could close this issue?

Top Results From Across the Web

Troubleshooting | Cypress Documentation

If you still haven't found a solution, open an issue with a reproducible example ... Tip: use the cypress info command to see...

Best Practices - Cypress Documentation

We have built Cypress to support this use case. In fact, Cypress does not clean up its own internal state when the test...

Error Messages | Cypress Documentation

This message means that Cypress was unable to find tests in the specified file. You'll likely get this message if you have an...

Announcing Cypress Component Testing GA and ...

Since it's still Cypress, you use the same familiar APIs to write and organize component tests and have access to our vast ecosystem...

Retry-ability - Cypress Documentation

If the assertion still fails, Cypress continues retrying until the cy.find() timeout is reached. Retry-ability allows the test to complete each query as...