Client configuration data can optionally be read from a local file if you'd like to keep your authentication data separated from your code. Place a file named tender__config.json in the root directory of your application to use it in place of runtime configuration. No special code is neccessary - the file will automatically be loaded if it exists.

The configuration file should follow the following format. All fields are optional and will be overridden by runtime parameters if specified. The testData object is used by the automated tests and should be omitted unless you plan on running them. See below for detail.

To run the test suite, invoke the following commands in the repository:

$ npm install
$ npm test

Please note that the majority of the tests rely on a live Tender API account in order to execute.
To set up the test data for your account, create a local configuration file as shown above and fill out
the testData object as follows:

queue - The name of a queue in your account.

category - The name of a category in your account.

categoryId - The id of a category in your account.

user - The full name of a user belonging to your Tender account.

userId - The id of a user belonging to your Tender account.

discussionId - The id of any discussion belonging to your account

pattern - A regexp pattern that will match the title of at least one Open discussion on your account.

A single discussion will be created under the category specified above, replied to, and deleted as part of the tests. All other tests perform read operations only.