web-component-tester | Moved to Polymer/tools monorepo | Web Framework library

You should try to add ./ if the @open-wc is in the main public folder:

I stumbled in the answer in Specify browser location for wct-local test. It is different question (it is regard using gulp) but I noticed something different from my wct.conf.js which I gave a try and it in https://github.com/jimisdrpc/basic-vanilla-webcomponent now unit testing working with wct. What I changed was instead of

I would advice to use fetch for this. It also will send an ajax call and is native to your browser.

There are many errors :

• First, please read the whole documentation as in the last paragraph it's clear that for those who use npm you need an additional dependency through the wctPackageName :

Components which wish to support npm-based installation should include wct-browser-legacy in their devDependencies, which is a package that contains only the client-side javascript necessary for executing WCT tests in an npm-based environment. WCT will attempt to identify which package provides the client-side code by checking for compatible packages in the following order of preference: wct-mocha, wct-browser-legacy and web-component-tester. If you want to specify which package provides WCT client-side code, use the --wct-package-name flag or wctPackageName option in wct.conf.json with the npm package name.

So you will need to add wct-browser-legacy in your devDependencies

• Giving your project structure, you are including the app.js as if it was at the same level. It should be ../src/app.js.
• You should add the type="module" to that import
• You declared a fixture but didn't take profit of it through the function fixture

If I had to correct your code :

• The command should be wct --npm -wct-package-name=wct-browser-legacy. Or even better create a wct.conf.js file with the following information :

I found a solution. When I listen on key down event the event is correctly catch.

It's a missing feature in MockInteractions.

No need to install wct-headless. Just create file wct.conf.json with the following content:

a11ySuite was moved to wct-browser-legacy as of web-component-tester version 6.4.3. Given the "legacy" naming, I'm guessing it's deprecated. I assume it's used like this:

I've tried to debug further and found that we are not able to launch google-chrome in docker container which is throwing an error Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted Trace/breakpoint trap (core dumped).

So while investigating the issue I found that there was an issue in chrome which prevents chrome to startup in docker environment. run google chrome headless in docker.

With all these options now I managed to resolve this issue.

I'm using configuration file for WCT and passing the --no-sandbox option in config file.

So now WCT is launching google-chrome

My wct.conf.json file is

By looking at the other dependencies you're loading from the same directory, I would say that the path is case sensitive, and that for app-layout you only used lower case letters, instead of the PascalCase format, so maybe you should try: