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

Quarantine and live modes are not working nicely together #4093

Closed
valgussev opened this issue Aug 1, 2019 · 2 comments
Closed

Quarantine and live modes are not working nicely together #4093

valgussev opened this issue Aug 1, 2019 · 2 comments
Assignees
Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: live mode TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@valgussev
Copy link

What is the Current behavior?

In both quarantine and live modes failed test will stuck on the first try

What is the Expected behavior?

Failed test should rerun 3 times and print an error of the last run

What is your web application and your TestCafe test code?

import { Selector } from 'testcafe';

fixture('Test').page('http://localhost:3000/');

test('Test', async t => {
  console.log('Inside test');
  await t.click(Selector('.test'));
});

Steps to Reproduce:

Clone this repo https://github.com/valerii-cognite/testcafe-quarantine-issue

run yarn && yarn start

In order to see a problem run

yarn testcafe chrome testcafe --live --quarantine-mode

and see theat failed test will never be retriggered and no error will be printed.

In order to see an expected behaviour run

yarn testcafe chrome testcafe --live

or

yarn testcafe chrome testcafe --quarantine-mode

and observe an error.

Your Environment details:

  • testcafe version: 1.3.3
  • node.js version: v8.13.0
  • browser name and version: Chrome 75
  • platform and version: macOS 10.13
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Aug 1, 2019
@AndreyBelym AndreyBelym added AREA: server SYSTEM: live mode TYPE: bug The described behavior is considered as wrong (bug). labels Aug 1, 2019
@AndreyBelym AndreyBelym added this to the Planned milestone Aug 1, 2019
@AndreyBelym
Copy link
Contributor

AndreyBelym commented Aug 1, 2019

Thank you for your report. I've reproduced the issue. We will address it in future development sprints.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Aug 1, 2019
@AndreyBelym AndreyBelym modified the milestones: Planned, Sprint #40 Aug 28, 2019
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Aug 29, 2019
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Aug 29, 2019
@AlexKamaev AlexKamaev self-assigned this Aug 29, 2019
@lock
Copy link

lock bot commented Sep 13, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Sep 13, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 13, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
* fix quarantine for live mode (closes DevExpress#4093)

* Update src/runner/test-run-controller.js

Co-Authored-By: Vladimir Airikh <vladimir.airich@gmail.com>

* Update src/live/test-run-controller.js

Co-Authored-By: Vladimir Airikh <vladimir.airich@gmail.com>

* Update src/live/test-run-controller.js

Co-Authored-By: Vladimir Airikh <vladimir.airich@gmail.com>

* Update src/live/test-run-controller.js

Co-Authored-By: Vladimir Airikh <vladimir.airich@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: live mode TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

3 participants