Botfuel Dialog

Build highly conversational bots with Botfuel Dialog.

Read Getting Started to learn how to run a bot in minutes. See some sample bots written with Botfuel Dialog.

For more explanations about the internals of Botfuel Dialog, see Concepts.

If you have any issue or question, feel free to open a ticket.

Run the tests

Running all the tests

Run botfuel-dialog and each test packages (integration) tests:

BOTFUEL_APP_ID=<...> BOTFUEL_APP_KEY=<...> npm test

If you are using Windows Powershell, use this command instead:

$Env:BOTFUEL_APP_ID=<...>; $Env:BOTFUEL_APP_KEY=<...>; npm test

Unit tests

Run only the botfuel-dialog tests:

npm unit-test

Integration tests

BOTFUEL_APP_ID=<...> BOTFUEL_APP_KEY=<...> npm test packages/<PACKAGE_NAME>

If you are using Windows Powershell, use this command instead:

$Env:BOTFUEL_APP_ID=<...>; $Env:BOTFUEL_APP_KEY=<...>; npm test packages/<PACKAGE_NAME>

Example:

BOTFUEL_APP_ID=<...> BOTFUEL_APP_KEY=<...> npm test packages/test-qna

By default, integration tests are run using fixtures. To register new fixtures, add REPLAY=record to the test command:

REPLAY=record BOTFUEL_APP_ID=<...> BOTFUEL_APP_KEY=<...> npm test

If you are using Windows Powershell, use this command instead:

$Env:REPLAY=record; $Env:BOTFUEL_APP_ID=<...>; $Env:BOTFUEL_APP_KEY=<...>; npm test

This will make real API calls and create new fixtures.

Publish on NPM

BOTFUEL_APP_ID=<...> BOTFUEL_APP_KEY=<...> npm release

If you are using Windows Powershell, use this command instead:

$Env:BOTFUEL_APP_ID=<...>; $Env:BOTFUEL_APP_KEY=<...>; npm release

Publishing requires credentials because it runs integration tests beforehand.

License

See the License file.