Get more details at codescene.io.

• Running project
• Testing and Continuous Integration

• The build task will build the entire project (but not run it)
• The familiar run Gradle task will still run your SparkJava Server. (which is available at localhost:4567)
• The runClient task will build and run the client side of your project (available at localhost:9000)
• The runAllTests task will then run both the Java (Server) tests and the karma (client-side, Angular) tests
• The runServerTests task will run the Java (Server) tests
• The runClientTests task will run the karma (client-side, Angular) tests.
  • The runClientTestWithCoverage task will run the karma tests and generate test coverage data which will be placed in client/coverage; open the index.html in that directory in a browser and you'll get a web interface to that coverage data.
  • The runClientTestsAndWatch task will run the karma tests, but leave the testing browser open and the tests in "watch" mode. This means that any changes you make will cause the code to recompile and the tests to be re-run in the background. This can give you continuous feedback on the health of your tests.
• The runE2ETest task runs the E2E (end-to-end, Protractor) tests. For this to work you must make sure you have your Server running, and you may need to re-seed the database to make sure it's in a predictable state.
• The seedMongoDB task will load the "demo" data into the Mongo database. If you want/need to change what gets loaded, the seedMongoDB command is defined in the top level build.gradle and current loads two files, todos.seed.json and users.seed.json, both of which are also in the top level of the project. (They probably should be in a data directory to reduce clutter, so you might want to move them.) To load new/different data you should create the necessary JSON data files, and then update build.gradle to load those files.

build.sh is a script that calls upon gradle build to build the entire project which creates an executable to be able to launch the project in production mode. To run build.sh, go to your project directory in a terminal and enter:./build.sh

When build.sh is run, the script .3601_run.sh is copied to ~/3601.sh. When this is launched, for example, ./3601.sh, will run your project in production mode. The API_URL in environment.prod.ts needs to be the actual URL of your Server. If your Server is deployed on a droplet or virtual machine, for example, then you want something like http:https://192.168.0.1:4567 where you replace that IP with the IP of your droplet. If you've set up a domain name for your system, you can use that instead, like http:https://acooldomainname.com.

❗ Pro-tip: IntelliJ comes with a nice view to see the mongo databases setup. To access this click on File -> Settings -> Plugins, type Mongo and make sure the Mongo Plugin is installed. Now head to View -> Tool Windows -> Mongo Explorer. Then use the tool icon to add configuration. Once prompted type for Path to Mongo Shell: "/usr/bin/mongo" and hit the green ➕, to add your label and, huzzah!, Mongo Explorer is on your side bar.

Testing options are still integrated so you can test the client, or the Server or both. Testing client:

• runAllTests runs both the Server tests and the clients tests once.
• runClientTests runs the client tests once.
• runClientTestsAndWatch runs the client tests every time that the code changes after a save.
• runClientTestsWithCoverage runs the client tests and deposits code coverage statistics into a new directory within client called coverage. In there you will find an index.html. Right click on index.html and select Open in Browser with your browser of choice. For Chrome users, you can drag and drop index.html onto chrome and it will open it.
• runE2ETest runs end to end test for the client side. NOTE: Two Gradle tasks must be run before you can run the e2e tests. The Server (run) needs to be on for this test to work, and you have to need to have data in the dev database before running the e2e tests!
• runServerTests runs the Server tests.

• What are environments in Angular CLI?
• Testing Angular with Karma/Jasmine
• End to end testing (e2e) with protactor and Angular CLI
• Angular CLI commands

• Spark documentation
• HTTP Status Codes
• Other Resources

• Mongo's Java Drivers (Mongo JDBC)