Comments (3)
Once you create a Server
instance the window.WebSocket
object has been mocked by default. Usually the best place for it is beforeEach
hook.
If it's not working for you it's better to check the documentation of the library. https://playwright.dev/docs/mock#creating-mocks
For example you can try mocking it manually like this:
import { WebSocket } from 'mock-socket';
test.beforeEach(async ({ page }) => {
await page.addInitScript(() => {
window.WebSocket = WebSocket;
});
});
and create a server with mock: false
option later:
test('...', async ({ page }) => {
const server = new Server('ws://localhost:8080', { mock: false });
});
from mock-socket.
Hey @Atrue thanks for the response. The issue I had was the WebSocket definition doesn't get passed through the addInitScript(), so the definition is never overwritten. Is there a workaround for that you're aware of? It looks like the stuff in the init script is completely isolated.
from mock-socket.
You need to try the examples in the documentation and make sure they works, if so you can try mocking the WebSocket the same way, you can even try it without this library, but there is no difference.
As mocking getBattery
is the same as the mocking WebSocket
it should work in both cases. But if the playwright has difference there you can also try using Object.defineProperty
from mock-socket.
Related Issues (20)
- Is this repo still maintained? HOT 5
- Using QueryParams in ws url doesn't work HOT 1
- How to mock Apollo client to test graphql subscription HOT 1
- Add `connectionDelay` option to Server to delay opening connection
- Mock ws inside web worker HOT 3
- Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.8. HOT 2
- Delay execution of dispatched events HOT 5
- Enable and disable MockSocket at runtime HOT 2
- mock-socket configuration issue ? HOT 1
- [Typescript] Client.addEventListener and Server.addEventlistener has wrong typing HOT 1
- send should throw an error if readyState is CONNECTING HOT 1
- Bug in ws client mock - wrong close code when server not found HOT 1
- Export `CloseEvent` HOT 1
- Spec doesn't actually say that `send()` should throw when the socket is `CLOSING` or `CLOSED` HOT 2
- Calling `close()` in the `CONNECTING` state should not result in open callback being called
- Do you need to import the WebSocket in this example? HOT 4
- The socket-server stops after 1 message is emitted HOT 4
- Apparently, test.cb() has been deprecated by ava HOT 1
- Using JWM/`mock-socket` in Jest with `partysocket` causes error: `TypeError: ports is not iterable` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mock-socket.