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.

Sign up for GitHub

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

Jump to bottom

TestCafe starts getting 404 errors for any pages in session #3560

Closed
AndreyBelym opened this issue Mar 13, 2019 · 4 comments
Closed

TestCafe starts getting 404 errors for any pages in session #3560

AndreyBelym opened this issue Mar 13, 2019 · 4 comments
Assignees
@AlexKamaev
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. Support Center An issue created/received from the Support Center ticket. TYPE: enhancement The accepted proposal for future implementation.
Milestone
Sprint #38

Comments

@AndreyBelym
Copy link
Contributor

AndreyBelym commented Mar 13, 2019 •
edited by helen-dikareva
Loading

https://supportcenter.devexpress.com/internal/ticket/details/T723455

What is your Test Scenario?

Test a page that submits a form.

What is the Current behavior?

After the form is submitted, the browser shows the 404 error. Trying to manually open any page in the current session will also lead to the 404 error.

What is the Expected behavior?

The page is shown after the form is submitted.

What is your web application and your TestCafe test code?

Check the origin ticket link.

Your Environment details:

  • testcafe version: 1.1.0
  • node.js version: 10.12.0
  • command-line arguments: n/a
  • browser name and version: Chrome 74
  • platform and version: Windows 10
@AndreyBelym AndreyBelym added the TYPE: bug The described behavior is considered as wrong (bug). label Mar 13, 2019
@AndreyBelym AndreyBelym added this to the Sprint #30 milestone Mar 13, 2019
@AndreyBelym AndreyBelym modified the milestones: Sprint #30, Sprint #31 Apr 2, 2019
@AlexKamaev AlexKamaev self-assigned this Apr 2, 2019
@AlexKamaev AlexKamaev added TYPE: enhancement The accepted proposal for future implementation. and removed !IMPORTANT! TYPE: bug The described behavior is considered as wrong (bug). labels Apr 4, 2019
@AlexKamaev AlexKamaev modified the milestones: Sprint #31, Planned Apr 4, 2019
@addisonmiller
Copy link

I'm experiencing this as well. Just wanted to pass along, that running safari test at same time corrects issue in Chrome. Just a workaround, not a fix.

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Apr 17, 2019
@AlexKamaev
Copy link
Contributor

@addisonmiller
The website from the original issue has its own specifics so your problem is hardly related to it.
It's better to create a separate report using this form . Please also provide us with an example which demonstrates the issue.
I would also recommend using the latest testcafe version since it has some fixes for similar issues

@AlexKamaev AlexKamaev removed the STATE: Need response An issue that requires a response or attention from the team. label Apr 17, 2019
@helen-dikareva helen-dikareva added the Support Center An issue created/received from the Support Center ticket. label Apr 24, 2019
@AndreyBelym AndreyBelym modified the milestones: Planned, Sprint #37 Jul 16, 2019
@AndreyBelym AndreyBelym removed Support Center An issue created/received from the Support Center ticket. labels Jul 16, 2019
@AlexKamaev
Copy link
Contributor

I was able to reproduce the issue on the sample. It's very unstable, but still fails:

<!DOCTYPE html>
<html>
<head>
    <meta charset="UTF-8">
    <title></title>
</head>
<body>

<script>
    function onClick () {
        setTimeout(function () {
            document.forms[0].submit();
        }, 100);
    }
</script>

<form action="http://google.com">
    <input type="text" id="text"/>
    <button onclick="onClick(); return false;">submit</button>
</form>

</body>
</html>
import { Selector } from 'testcafe';

fixture`fixture`
    .page`...`;

for (let i = 0; i < 10; i++) {
    test('1', async t => {
        await t.typeText('input', '12345');
        await t.click('button');
    });

    test('2', async t => {
       await t.wait(5000);
    });
}

@AndreyBelym AndreyBelym added the Support Center An issue created/received from the Support Center ticket. label Jul 23, 2019
@AndreyBelym AndreyBelym modified the milestones: Sprint #37, Sprint #38 Jul 23, 2019
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Jul 26, 2019
@AlexKamaev
prevent any form submit after the test is done (closes DevExpress#3560)
3f168a0
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Jul 30, 2019
@AlexKamaev
prevent any form submit after the test is done (closes DevExpress#3560)
64c4381
AndreyBelym pushed a commit to AlexKamaev/testcafe that referenced this issue Aug 1, 2019
@AlexKamaev @AndreyBelym
prevent any form submit after the test is done (closes DevExpress#3560)
71d3dcf
@lock
Copy link

lock bot commented Aug 11, 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 Aug 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Aug 11, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
@AlexKamaev @kirovboris
Bump version (v1.4.0-rc.2); Bump hh (v14.7.2); Prevent form.submit (fix
20f759e 
DevExpress#3560) (DevExpress#4077)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@AlexKamaev AlexKamaev

Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. Support Center An issue created/received from the Support Center ticket. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Milestone
Sprint #38
Development

No branches or pull requests
4 participants
@AlexKamaev @addisonmiller @AndreyBelym @helen-dikareva