@nebula.js/sn-gauge 0.7.2 → 0.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/README.md +3 -10
  2. package/core/esm/index.js +3 -3
  3. package/core/package.json +1 -1
  4. package/dist/sn-gauge.esm.js +4 -4
  5. package/dist/sn-gauge.js +4 -4
  6. package/dist/sn-gauge.systemjs.js +3 -3
  7. package/package.json +36 -41
  8. package/sn-gauge-ext/dist/sn-gauge.js +4 -4
  9. package/sn-gauge-ext/sn-gauge.qext +1 -1
package/README.md CHANGED
@@ -4,15 +4,8 @@
4
4
 
5
5
  A nebula.js supernova picasso gauge chart
6
6
 
7
- ## Developing
7
+ # Rendering tests
8
8
 
9
- The following procedure ensures we have both the current gauge chart and the sn-gauge (this repo) working, making it easy to compare. What's more, it's fast to update sn-gauge chart after changing code (just one browser refresh).
9
+ Rendering tests are running playwright. Execute rendering tests with `pnpm test:e2e --headed`.
10
10
 
11
- Note: you only need to do step 2, 3, 4 once
12
-
13
- 1. Install with `pnpm install`
14
- 2. Build extension with `pnpm build` and upload it to your tenant. I use V&P team tenant (fualn).
15
- 3. In sense-client, in "web/assets/objects/extension/extension-loader/load-qlik-extension-system.ts", add `'sn-gauge': 'sn-gauge',` into `const enabledCharts` object.
16
- 4. In qmfe dev tool, add new override with name "sn-gauge", address "https://localhost:8000/pkg/sn-gauge"
17
- 5. Also use override of sense-client with your local change from step 3
18
- 6. Run your local sn-gauge with `pnpm start:mfe`. Note: you may have to change the port in step 4 based on what presented in your terminal at this step.
11
+ Rendering test compares a baseline snapshot with a current version of the same object. The output is then stored under `baselines`. It is important to take the baseline from the build in your PR and not your local baselines which is stored under `baselines-local`. The report with baselines can be found under summary and is a zipped file called `playwright-report`. Make sure to unzip it to see the images.