Developer Guide

This page describes how to build, test, run the Scenarioo Viewer Webapp locally for developers on their developer machine.


You need a correctly setup development environment for working on Scenarioo as described here: Development Environment Setup

Build, Test and Run the Scenarioo Viewer Web App

This process describes how you clean update all your sources and build everything needed to properly run the demo locally and to run tests:

  1. You need to have cloned all sources (if not yet):

     git clone scenarioo

    Depending on whether the current development state of the sources needs to have a lates and greates snapshot version of the Scenarioo Writer Library scenarioo-java, you might as well have to clone and build the writer library repo (check scenariooApiVersion property at top of our build file build.gradle to see whether it uses a SNAèSHOT-version, or try it without it, if you're feeling lucky):

     git clone scenarioo-java
  2. In case current version uses SNAPSHOT version of scenariioo-java: Update and build the writer library and install the newest SNAPSHOT in local maven repo:

      cd scenarioo-java
      git pull
      ./gradlew clean build test install
  3. build the server

     cd ~/scenarioo
     git pull
     ./gradlew clean build test war
  4. Refresh and build in your IDE

  5. Generate the dummy test data:

    • This was already done by running all tests.
    • But if you just want to clean your test data to a good state again, you can also choose to only run all tests inside project scenarioo-docu-generation-example: this sub module builds all dummy data of the 'wikipedia-docu-example' that you need for testing the Scenarioo web app (and running e2e tests later).
  1. Start up the scenarioo-server in Tomcat (usually done in your IDE), see Development Environment Setup for more info on that.

  2. Build, serve and browse the client of the web app:

     cd ~/scenarioo/scenarioo-client
     npm install
     npm start

    Then open the browser to browse the application under http://localhost:8500/scenarioo/ (Caution: webpack needs to need the slash in the end!) If you change files in the client the browser will refresh automatically

    Some remarks about this:

    • npm install: Installs node.js modules (mainly needed tools) as configured in package.json. They are placed in the folder node_modules. It also calls the relatively installed bower binary to install frontend dependencies.
  3. Configure webapp correctly (if not yet) and browse it:

    • Go to the configuration page (under Manage in the top right corner, then choose tab General Settings). You should see some preconfigured values, which means the client was able to reach the server.
    • In the field "Documentation Data Directory Path" you see where Scenarioo stores the config.xml file and where it expects documentation data. You can change the folder to a different one, see Setup of Scenarioo Viewer Web App. You can either add your own config.xml file to this folder or let Scenarioo write the file the first time you save some configuration changes in the Manage section of Scenarioo.
    • In the Builds tab on the Manage page of Scenarioo you can click on the Import & Update Builds link in the top right corner. You should see then that Scenarioo is either currently importing the build (state = PROCESSING) or already done with it (state = SUCCESS).
    • Reload the page, as soon as the state of the builds are SUCCESS the Branch wikipedia-docu-example and it's builds should be selectable in the Scenarioo navigation bar. Select the build and navigate the example documentation. If you see a list of use cases, everything should be okay.
  4. Before you start to develop, you should check that all unit tests and E2E test are successful, before you start to break them ;-) Make sure to run these tests regularly when you develop and to keep them successful:

    • run all unit tests:
      • run all java unit tests inside scenarioo-java
      • run all java unit tests inside scenarioo/scenarioo-server
      • run all java-script unit tests inside scenarioo/scenarioo-client: npm test
    • run all E2E tests (=web tests): see E2E Testing

Well done, now you're ready to code!

Now have fun improving and extending Scenarioo, we are awaiting for your first pull request soon ;-)

Build WAR File for Server Deployement

The following command creates a war file which contains the server and the client code.

./gradlew war

Client package update strategy (package.json)

Packages should b specified statically. Example: "gulp-ng-annotate": "2.0.2".

Remark by Rolf: I changed this to from 2.0.x to 2.0.2 to use the specific version even for minor version. Reason: we should never automatically use newer minor versions - experiences sho that it can always happen that even a minor update of a dependency makes Scenarioo not work anymore - and this is not acceptable that somebody can not work because just the day before they introduced a bug in a minor version --> Murphies Law! Therefore I think we should use fix versions for all dependencies! (this replaced old comment, which was: "Only the bugfix version shall be dynamic. This will make our builds more stable. Specify the dynamic version by using the 'x' character.")

Npm packages may be checked by using the command npm outdated. You can update outdated packages by using npm update - but if you do so, you have to ensure that everything still works (e2e tests?) and inform developers in case new npm version is needed!

results matching ""

    No results matching ""