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

[BUG] Component test ERR_EMPTY_RESPONSE on 2nd run #16424

Closed
vhscom opened this issue Aug 10, 2022 · 3 comments
Closed

[BUG] Component test ERR_EMPTY_RESPONSE on 2nd run #16424

vhscom opened this issue Aug 10, 2022 · 3 comments

Comments

@vhscom
Copy link

vhscom commented Aug 10, 2022

Context:

  • Playwright Version: "playwright/experimental-ct-svelte": "^1.24.2"
  • Operating System: macOS
  • Node.js version: 16.14.2
  • Browser: All
  • Extra: ARM chip device

Code Snippet

import {test, expect} from '@playwright/experimental-ct-svelte';

test('can show column', async ({mount}) => {
  const component = await mount(DataTable, {
    slots: {
      toolbar: '<div>Toolbar</div>'
    },
    props: {
      tableTitle: 'Test table',
      items: [],
      selectedOffsets: [],
      shouldShowColumn: true
    }
  });

  await expect(component).toContainText('Table column header text');
});

Describe the bug

When testing my first Svelte component, subsequent runs of the test runner result in an error message:

undefined: net::ERR_EMPTY_RESPONSE at http://localhost:3100/playwright/index.html
=========================== logs ===========================
navigating to "http://localhost:3100/playwright/index.html", waiting until "load"
============================================================

Occurs repeatedly and I cannot run tests after first test run and until the component under test has had its file date changed (via modification and saving). After that the app compiles and the test run. But not before then.

@rwoll
Copy link
Member

rwoll commented Aug 10, 2022

I attempted to repro here, but could did not observe any errors. Can you re-file with a repro attached (in the form of a GitHub repo we can clone, download, and run that produces the error)?

One thing to note: looks like you're missing DataTable import statment at the top of your file.

@rwoll rwoll closed this as completed Aug 10, 2022
@vhscom
Copy link
Author

vhscom commented Aug 10, 2022

@rwoll will do. I'm going to try a bulk upgrade on packages first and if that doesn't correct the problem I'll create a repo with a reduced test case for you if the issue persists.

@vhscom
Copy link
Author

vhscom commented Aug 11, 2022

Refiled with repro in #16460

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants