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

[Component Testing using Service Virtualisation(Mountebank)] #12352

Closed
Kapil-Anandagiri opened this issue Feb 25, 2022 · 2 comments
Closed

[Component Testing using Service Virtualisation(Mountebank)] #12352

Kapil-Anandagiri opened this issue Feb 25, 2022 · 2 comments

Comments

@Kapil-Anandagiri
Copy link

Using service virtualisation want to perform the component/system testing.
Features Required

  1. Start the stub server automatically and all my new endpoints should listen on stub server portno, so that I can validate the mocks with respect to the component testing. (By this way it will help a lot for Shift Left Testing)
  2. Need to connect DB using playwright package itself, so by this way apart from fixtures data driven testcases also can be achieved.

Thanks in Advance

@mxschmitt
Copy link
Member

Component testing of e.g. React components is not yet possible, I'd recommend to subscribe to this issue: #7148

You could start the web server by using the webServer feature in Playwright Test, see here: https://playwright.dev/docs/test-advanced#launching-a-development-web-server-during-the-tests
For connecting to a database, you can use any NPM / Node.js package, there are no limitations because Playwright runs inside Node.js and not inside a browser. Depending on your setup you need different database clients.

@mxschmitt
Copy link
Member

Closing as part of the triage process since it seemed stale or did not get enough upvotes in the past. Please create a new issue with a detailed reproducible or feature request if you still face issues.

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

No branches or pull requests

2 participants