https://github.com/ow2-proactive/studio
Workflow Studio for ProActive Workflows & Scheduling
https://github.com/ow2-proactive/studio
editor proactive studio workflow
Last synced: 17 days ago
JSON representation
Workflow Studio for ProActive Workflows & Scheduling
- Host: GitHub
- URL: https://github.com/ow2-proactive/studio
- Owner: ow2-proactive
- Created: 2015-05-16T13:38:57.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2025-04-25T15:12:52.000Z (about 1 month ago)
- Last Synced: 2025-05-13T11:06:17.871Z (17 days ago)
- Topics: editor, proactive, studio, workflow
- Language: JavaScript
- Homepage: http://proactive.activeeon.com/
- Size: 79.5 MB
- Stars: 10
- Watchers: 18
- Forks: 43
- Open Issues: 108
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Workflow Studio for ProActive Workflows & Scheduling
[](http://jenkins.activeeon.com/job/studio/)
## Requirements
You need npm installed (Node.js).
Selenium-standalone is required for the UI tests (installed locally by npm). If you intend to run the tests locally, you'll need to update your Chrome browser and install the latest version of Selenium-standalone:
Delete package-lock.json file and then run the following command:
```
npm install selenium-standalone@latest
```
Not updating both Chrome and selenium-standalone can result in selenium not able to _attach_ to the browser when running the tests.
:boom::boom: Do not commit your changes to the selenium-standalone version :boom::boom:
## Setup
Run these commands to setup your dev environment:
```
npm install -g grunt-cli bower
npm install
bower install
```
Then to deploy the studio with the scheduler, create a symlink called `studio` in `$SCHEDULING_HOME/dist/war`
pointing to `app`.
# Tests
## Setup
- Fulfill the dependencies with `npm install` and `bower install`.
Then let's assume you did some changes to the code, you want to check for regressions.
You need to either run `grunt clean build test:ui:dev`(test is a predefined task of grunt,
and already runs some syntax check on the code).
### Manual Test Execution
- On the first run you need to use `node_modules/selenium-standalone/bin/selenium-standalone install` which
will install generic drivers and chrome drivers (firefox stopped support of their selenium driver and
started a new webdriver in Rust). Once selenium server is downloaded,
you can run it with `node_modules/selenium-standalone/bin/selenium-standalone start` to start
your local selenium server instance.
- Call nightwatch with your config and test suite
`node_modules/nightwatch/bin/nightwatch --config test/ui/nightwatch.json --env jenkins-chrome` for example
## How to run a specific test case
The test will assume you have a running studio instance (either in a real release that is running locally, or using method B). Method B doesn't require any running release, you have to run the following command `node test/json-server-data/mock-scheduler-rest.js` from your studio respository. Then you can run a single test file using `node_modules/nightwatch/bin/nightwatch --config test/ui/nightwatch.json --test test/ui/specs/login.js --testcase "PWS-159 The dialog Please open a workflow appears behind the no workflow open panel"`
if you don't specify the --testcase it will run the whole test file.
## Notes
You can also run a mocked json-server to simulate a running instance of the Studio, of course nothing will be submitted or modified server-side:
`grunt mock:run`
or along with a full compilation:
`grunt clean build mock:run`