Use Staging JWT Token

To use the staging endpoint to grab a token, rather than production, use the env variable variable USE_STAGING_JWT. The default value is false (will use prod) set to true in order to switch to staging.

Getting Started

Install app

git clone [email protected]:cbdr/cbax-apply-platform.git
npm install

Start app

grunt # builds javascript and starts servers (express and mongodb VM)
grunt express # just starts server

Running Tests

 # Run Jasmine-Node, Karma and Protractor tests for dev environment
grunt # build and start server
grunt test:dev

 # Run tests for CI/test environment
grunt test:ci

End to end tests (Endpoint testing)

npm run-script e2e

Setup

Install Grunt

npm install -g grunt-cli

Grunt Protractor Runner

npm install
cd node_mondules/grunt-protractor-runner
npm install protractor
cd ../.. # PROJECT ROOT
./node_modules/grunt-protractor-runner/node_modules/protractor/bin/webdriver-manager update

 # setup environment variables
export SAUCE_USERNAME='[USERNAME]'
export SAUCE_ACCESS_KEY='[ACCESS-KEY]'

References

• Jasmine
• Grunt Jasmine Node
• Karma config
• Grunt Karma runner
• Grunt Protractor Runner

Visit

http://localhost:3000/demo.html

Deployment

For quick deployment instructions go here

To run the deployment script:

node ./utils/deploy

Which does nothing. it needs to know what you want to deploy.

Available Options (controlled by ./utils/deploy/command_options.js):

• --cbax OR -c direct script to deploy cbax app
• --resumepicker OR -r direct script to deploy resumepicker app
• --console OR -o direct script to deploy console app
• --urlservice OR -u direct script to deploy urlservice app
• --app can be used multiple times, options are cbax || resumepicker || console || urlservice should be given a revision in the same order as the app is specified
• --revision used to specify the revision for the apps specified by the --app param
• --dryrun used to output the deployment params that will be used for the actual deployment (ignore the error about .start() of undefined)
• --testdeployment used to run a test deployment (single deploy to useast test stack)
• --proddeployment used to run deployment in singaport, then eu, the useast in that order and only on successful completion of the prior deployment (if eu fails, useast will not be deployed)

ONE OF THE LAST TWO PARAMS LISTED MUST BE USED, OR NOTHING WILL HAPPEN

Jenkins Test

Testing

• Staging|Production Url for Postman: "https://avi.applyexperience.io/"|"https://application.careerbuilder.com/"
• API Tester: "/core/apply/{route}"

Versioning

• Default: applicant-info, candidateScreenerResponse, getCandidateLocation, getJobApplications, external
• 1.0: form, formschema, submit

Error

• Error-- {"name":"cbax-development","hostname":"app_dequeue","pid":1,"lib":"concurrent_app_queue","level":60,"msg":"QUEUEING ERRORS LIKE THIS SHOULD NEVER HAPPEN: { UnrecognizedClientException: The security token included in the request is invalid. When above error come, try below command- *Solution - Run the command -docker run -p 9324:9324 -p 9325:9325 softwaremill/elasticmq