Skip to content

Get Cypress up and running again (with docker and interactive testing) #2788

Get Cypress up and running again (with docker and interactive testing)

Get Cypress up and running again (with docker and interactive testing) #2788

Triggered via pull request June 26, 2024 22:16
@SplinesSplines
synchronize #652
tests/cypress
Status Failure
Total duration 38s
Artifacts

linter.yml

on: pull_request
RuboCop (Ruby)
30s
RuboCop (Ruby)
ESLint (JS)
16s
ESLint (JS)
Fit to window
Zoom out
Zoom in

Annotations

10 errors
ESLint (JS): spec/cypress/e2e/admin.js#L26
Do not wait for arbitrary time periods
ESLint (JS): spec/cypress/e2e/admin.js#L28
Do not wait for arbitrary time periods
ESLint (JS): spec/cypress/e2e/courses.js#L21
Do not wait for arbitrary time periods
ESLint (JS): spec/cypress/e2e/courses.js#L24
Do not wait for arbitrary time periods
ESLint (JS): spec/cypress/e2e/courses.js#L61
Do not wait for arbitrary time periods
ESLint (JS): spec/cypress/e2e/courses.js#L80
It is unsafe to chain further commands that rely on the subject after this command. It is best to split the chain, chaining again from `cy.` in a next command line
ESLint (JS): spec/cypress/e2e/media.js#L74
Do not wait for arbitrary time periods
ESLint (JS): spec/cypress/e2e/media.js#L80
Do not wait for arbitrary time periods
ESLint (JS): spec/cypress/e2e/media.js#L81
It is unsafe to chain further commands that rely on the subject after this command. It is best to split the chain, chaining again from `cy.` in a next command line
ESLint (JS): spec/cypress/e2e/media.js#L81
It is unsafe to chain further commands that rely on the subject after this command. It is best to split the chain, chaining again from `cy.` in a next command line