commit | 9252094e2641219004f07313e292ad37bc8e52d1 | [log] [tgz] |
---|---|---|
author | Dominik HanĂ¡k <domhanak@users.noreply.github.com> | Wed May 19 15:53:34 2021 +0200 |
committer | GitHub <noreply@github.com> | Wed May 19 10:53:34 2021 -0300 |
tree | 05908082b7c0c26ea00c7ec7d49b6377e3f3b90a | |
parent | dae40d6daa755f6fffe0cdb7073dd4f4557a1e65 [diff] |
KOGITO-5134: Fix VSCode integration tests editor waiting mechanism (#508) * KOGITO-5134: Fix VSCode integration tests editor waiting mechanism Minor refactoring, docs, format, errors Refactor waitUntilKogitoEditorIsLoaded Add javadoc, change name. Extract driver to single variable. Handle some errors in catch(), fix issues from review Remove dependency, add notification handling Wait for webview ready iframe, fix typos * Fix handling of closing of editors when test fails. Now the test should finish all others and not fail in the middle. * Always reset the webdriver to original window Fixes cases where there was a test failure and the driver was not switched back.
Kogito is the next generation of business automation platform focused on cloud-native development, deployment and execution.
Homepage: http://kogito.kie.org
Wiki: https://github.com/kiegroup/kogito-tooling/wiki
JIRA: https://issues.jboss.org/projects/KOGITO
jBPM: https://www.jbpm.org/
Drools: https://www.drools.org/
This module contains a number of examples that you can take a look at and try out yourself. Please take a look at the readme of each individual example for more details on how the example works and how to run it yourself (either locally or on Kubernetes):
In Kogito Tooling releases page you will find extensions and released tooling packages.
Check out the source:
git clone git@github.com:kiegroup/kogito-tooling.git
If you don't have a GitHub account use this command instead:
git clone https://github.com/kiegroup/kogito-tooling.git
Build with Yarn:
cd kogito-tooling yarn run init #prod yarn run build:prod # dev yarn run build # skips integration tests and production packing yarn run build:fast # skips lint and unit tests
NOTE: It's necessary to have the Git tags fetched when building with
build:prod
.
Final artifacts will be on
packages/*/dist
directories.
NOTE: We recommend using LTS version of Node.js when developing this project. Our CI uses Node
12.16.3
and Yarn1.19.1
.
NOTE: This repo now consumes NPM packages containing the exploded WARs of the BPMN, DMN, and SceSim Editors. For this reason, if you want to use a local build of one of them during development, you can use some environment variables to point to the exploded WAR directories.
- BPMN:
EXTERNAL_RESOURCE_PATH__bpmnEditor
- DMN:
EXTERNAL_RESOURCE_PATH__dmnEditor
- SceSim:
EXTERNAL_RESOURCE_PATH__scesimEditor
Example:
$ export EXTERNAL_RESOURCE_PATH__bpmnEditor=/Users/tiago/redhat/kie-wb-common/kie-wb-common-stunner/kie-wb-common-stunner-sets/kie-wb-common-stunner-bpmn/kie-wb-common-stunner-bpmn-kogito-runtime/target/kie-wb-common-stunner-bpmn-kogito-runtime/
$ export EXTERNAL_RESOURCE_PATH__dmnEditor=/Users/tiago/redhat/kie-wb-common/kie-wb-common-dmn/kie-wb-common-dmn-webapp-kogito-runtime/target/kie-wb-common-dmn-webapp-kogito-runtime/
$ yarn run init && yarn run build:prod
This is only necessary for these GWT-based Editors.
packages/vscode-extension-pack-kogito-kie-editors
folder on VS Code. Use a new VS Code window so that the packages/vscode-extension-pack-kogito-kie-editors
folder shows up as root in the VS Code explorer.Debug
menu/section. You can also use the respective shortcuts (F5 to start debugging, for instance).webpack
and webpack-cli
to be globally installed on NPM. Normally you can do that with npm install -g webpack@4.41.2 webpack-cli@3.3.10
, but sudo
may be required depending on your installation.packages/vscode-extension-pack-kogito-kie-editors
, you have to manually rebuild them before relaunching the extension on VS Code.packages/chrome-extension-pack-kogito-kie-editors
folder on your favourite IDE. You can import the entire repo as well if you want to make changes to other packages.yarn build:fast
on packages/chrome-extension-pack-kogito-kie-editors
. This will create a version of the Chrome Extension that fetches the envelope locally.yarn run serve-envelope
on packages/chrome-extension-pack-kogito-kie-editors
. This will start a webpack-dev-server
instance with the editors and their envelope. We use that because we don't pack the Chrome Extension bundle with the editors inside. Instead, we fetch them from GitHub pages.chrome://flags/#allow-insecure-localhost
in your Chrome browser and enable this flag. Alternativelly, you can go to https://localhost:9001
and add an exception.chrome://extensions
. Enable “Developer mode” on the top right corner and click on “Load unpacked”. Choose the packages/chrome-extension-pack-kogito-kie-editors/dist
folder.packages/online-editor
.yarn start
. This will start a webpack-dev-server
instance with the Online Editor resources.https://localhost:9001
.packages/desktop
or packages/hub
. They work exactly the same.yarn start
. If you make changes and want to reload the app, run yarn run build:fast && yarn start
. This will recompile the module and restart the Electron app. Remember: if you make changes to other modules, you have to build them too!yarn run build:prod
. This will pack the application for the current OS. If you want to pack the application for a different OS, run yarn run pack:linux
, for example. See package.json
for more details.packages/kie-editors-standalone
.yarn start --config webpack.package-resources.config.js
. This will start a webpack-dev-server
instance with the Standalone Editors test page.https://localhost:9001/resources/dmn
and the Standalone BPMN Editor by accessing https://localhost:9001/resources/bpmn
.Build: {github-username}/{branch-name}
. This will trigger a job that will fetch the forks (1) of {github-username}
, merge {branch-name}
into master, and build them. In a few seconds you should see a new comment on the same issue, saying that a new build was triggered for you. The GitHub Actions bot will also provide a link so you can follow the build logs and download artifacts, and another link to access an Online Editor instance (2) containing your changes, once it's finished running.(1) This process considers the following repositories: droolsjbpm-build-bootstrap
, kie-soup
, appformer
, kie-wb-common
, drools-wb
and kogito-tooling
.
(2) The Online Editor instance will be accessible for 30 days.
All contributions are welcome! Before you start please read the Developing Drools and jBPM guide.
Here are some of the most notable ones for quick reference: