Hello scichart team!
We would like to run e2e tests for our application, which uses the scichirt.js library. To run e2e, we will be running a local development server with our SPA app in some CI environment.
Is there a way to avoid installing a license manager for e2e in CI env and use RuntimeLicenseKey, but for localhost?
- Sergey Chernyakov asked 1 year ago
- last edited 1 year ago
- You must login to post comments
There are some ways to make this work. We do end to end testing internally for scichart.js as well as visual testing (similar to UIAutomation Testing, screenshot compare of charts generated expected vs. actual). To achieve this we use a combination of nodejs, headless browser, and some internal magic which is as yet unpublished (but on our roadmap)
From a licensing perspective, there are only two (or three) ways to license localhost
-
is to use the community license. This works everywhere, but with a watermark. It also has a time limit of 6-months from build date of the library, so requires regular updating. For more info about community-license terms & conditions see here.
-
is to install the licensing wizard on the server and activate a developer license. This will require purchasing an additional dev license (which typically is not required for build servers or build agents) however since you are running the app on this server with URL=localhost, this case is detected as a developer or OEM session and requires a developer license.
-
There is a third option, this is to purchase an Advanced License for SciChart.js (formerly called Server-Side License). This is a module where we can grant a client/server license key that works when deploying an application to localhost. The most popular use-case for Advanced Licenses are embedded systems, custom hardware and resellers of SaaS apps where the URL is not known at runtime. There is an additional fee for this license type but it’s not excessive and you can find out more by asking sales.
We’re in the process of finalising the wording for (3) and making it clearer / easier to understand for our users as well as our own team.
- Andrew Burnett-Thompson answered 1 year ago
- You must login to post comments
Please login first to submit.