graphdb-workbench 2.2.1-RC3 → 2.2.1-RC5

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 (48) hide show
  1. package/README.md +8 -1
  2. package/dist/11.2fbf25a8de5c52f67740.bundle.js +1 -1
  3. package/dist/11.2fbf25a8de5c52f67740.bundle.js.map +1 -1
  4. package/dist/148.dd250d3cc5aafade33c6.bundle.js +1 -1
  5. package/dist/148.dd250d3cc5aafade33c6.bundle.js.map +1 -1
  6. package/dist/20.fbcb31706f03a07e8827.bundle.js +1 -1
  7. package/dist/20.fbcb31706f03a07e8827.bundle.js.map +1 -1
  8. package/dist/27.c84970241a668ffaa401.bundle.js +1 -1
  9. package/dist/27.c84970241a668ffaa401.bundle.js.map +1 -1
  10. package/dist/33.4d23fa109c9184727386.bundle.js +1 -1
  11. package/dist/33.4d23fa109c9184727386.bundle.js.map +1 -1
  12. package/dist/40.50b40301c8cc69a70457.bundle.js +1 -1
  13. package/dist/40.50b40301c8cc69a70457.bundle.js.map +1 -1
  14. package/dist/94.38349f52df66313fbcc0.bundle.js +1 -1
  15. package/dist/94.38349f52df66313fbcc0.bundle.js.map +1 -1
  16. package/dist/bundle.ed626baa2f7b1cf6e71b.bundle.js +2 -2
  17. package/dist/bundle.ed626baa2f7b1cf6e71b.bundle.js.map +1 -1
  18. package/dist/index.html +2 -2
  19. package/dist/js/angular/core/directives/rdfresourcesearch/templates/rdfResourceSearchTemplate.html +1 -1
  20. package/dist/pages/autocomplete.html +1 -1
  21. package/dist/pages/choose-repository-type.html +1 -1
  22. package/dist/pages/cluster-management/clusterInfo.html +3 -3
  23. package/dist/pages/create-index.html +4 -4
  24. package/dist/pages/dependencies.html +1 -1
  25. package/dist/pages/domainRangeInfo.html +2 -2
  26. package/dist/pages/edit.html +1 -1
  27. package/dist/pages/explore.html +1 -1
  28. package/dist/pages/export.html +1 -1
  29. package/dist/pages/find.html +1 -1
  30. package/dist/pages/graph-config/saveGraphConfig.html +11 -11
  31. package/dist/pages/graphs-visualizations.html +7 -7
  32. package/dist/pages/guides.html +1 -1
  33. package/dist/pages/import.html +1 -1
  34. package/dist/pages/jdbc-create.html +5 -5
  35. package/dist/pages/monitor/queries.html +1 -1
  36. package/dist/pages/monitor/resources.html +2 -2
  37. package/dist/pages/namespaces.html +2 -2
  38. package/dist/pages/plugins.html +1 -1
  39. package/dist/pages/rdfClassHierarchyInfo.html +7 -7
  40. package/dist/pages/rdfrank.html +2 -2
  41. package/dist/pages/repositories.html +2 -2
  42. package/dist/pages/repository.html +2 -2
  43. package/dist/pages/similarity-indexes.html +1 -1
  44. package/dist/pages/sparql-template-create.html +5 -5
  45. package/dist/pages/sparql.html +3 -3
  46. package/dist/pages/webapi.html +2 -2
  47. package/dist/res/swagger/index.html +27 -27
  48. package/package.json +1 -1
package/README.md CHANGED
@@ -49,13 +49,20 @@ the Cypress's dashboard application. Follow the steps described below:
49
49
  `docker-compose up` in the `graphdb-workbench/test-cypress` folder. Check path directory which is set with **-Dgraphdb.workbench.importDirectory** property when server is started. The folder with this path have to contains all files from "fixture/graphdb-import"
50
50
 
51
51
  * In `graphdb-workbench` folder execute `npm run start` to build and run the workbench web
52
- application. In result it is published and served by webpack's web dev server.
52
+ application. In result, it is published and served by webpack's web dev server.
53
53
  * In terminal, go in `graphdb-workbench/test-cypress` folder and choose one of the options below:
54
54
  * Execute `npm run test` - this will run the test suite in a headless mode and the outcome log
55
55
  will be seen in the terminal.
56
56
  * Execute `npm run start` or the equivalent `npx cypress open` - this will open the Cypress's
57
57
  dashboard application through which the tests can be run one by one or altogether and observing the
58
58
  outcome in the dashboard.
59
+
60
+ > There is a separate acceptance tests suite containing some flaky tests which often fail on CI.
61
+ > That's why these are moved in the `integration-flaky` suite which is doesn't run on CI and is
62
+ > responsibility of the developer to run them manually before the commit.
63
+ >
64
+ > The flaky test suite can be run similarly to the normal test suite but using following commands:
65
+ > `npm run start:flaky` for browser mode or `npm run test:flaky` for a headless mode.
59
66
 
60
67
  ## Release and publish
61
68
  The workbench is regularly published as a package in the NPM registry.