Hello
I am trying to make visual E2E test form my application with playwright
When running locally everything works as expected after opening scichart’s Licence Wizard
But when I try to enter same page with playwright I get license key error
Is there any way to solve this? How excatly does scichart check for licence key?
I would be very glad for some help with this
- Cezary Szymanski asked 1 month ago
- last edited 1 month ago
- You must login to post comments
We don’t have any experience with Playwright, however in general assuming that end-to-end tests are run on a different domain, either that domain needs to be included in your runtime key as a test domain, OR, you need to remove the call to sciChartSurface.setRuntimeLicenseKey()
in your tests as per the error message, which will default the library to the watermarked community edition. Instructions on how to add a test domain can be found here.
There may be some other issues depending on environment, SciChart.js requires a browser with WebGL to run, and not knowing anything about Playwright – whether it provides a full browser or headless browser – there may be some further issues.
Internally we perform visual tests using Puppeteer & jest, which allows us to fire up a full WebGL enabled browser instance on the build server.
- Andrew Burnett-Thompson answered 1 month ago
- You must login to post comments
I am trying to run these tests on my local environment, so the host is localhost
Normally the authorization is made with License Wizard running on my PC
I guess the problem is that when running in Playwright the License Wizard is not detected?
Is there any way to overcome that issue? Or maybe you can give me a tip on how Scichart checks for the License Wizard on the machine?
- Cezary Szymanski answered 1 month ago
- last edited 1 month ago
- You must login to post comments
Hi Cezary, we can’t provide details on how our licensing works, but we can provide suggested solutions.
The options to solve this problem are, if you can, to run the SciChart licensing Wizard on the machine where tests are performed and activate a developer license. This will remove the licensing warning.
If this is not possible, you can also try to remove the call to SciChartSurface.setRuntimeLicenseKey()
in the test environment so that the chart defaults to community edition. This will show a watermark in your end-to-end tests but should allow you to proceed.
Finally, a more complex solution would be to purchase/integrate ‘Advanced Licensing’ options – this will also require input from our technical team.
Let me know if the simple solutions (1) (2) above work. If not, we may promote this to a support ticket so that our team can ask more questions about the environment and come up with a solution
- Andrew Burnett-Thompson answered 1 month ago
- You must login to post comments
Thank you for your help, I think that option 2 is a good enough as a work around for me right now
- Cezary Szymanski answered 1 month ago
- last edited 1 month ago
- You must login to post comments
Please login first to submit.