Matthew Schwartz

Is this work currently planned? I'd love to integrate this into my repo at work, but we heavily rely on `extends` in `tsconfig`

+1, getting similarly wonky results

@bilby91 all expectations are done in ExpectedMesage.ts. We also know the expectations that are going to be run (just based off the current ones). All we need to do is...

I think that's not bad. Following something like [karma](https://karma-runner.github.io/1.0/config/configuration-file.html)'s approach would be decent. Globals in a config file and or env variables. It would also help with #10

@bilby91 @benswinburne I've extended the library to be able to toggle between assertion libraries based on config or options. It's currently on the dev branch. I've opened up a new...

@bilby91 https://github.com/microsoftly/BotTester/commit/0a050c72ec98771657fd456455a7b812879d7e54 I tested locally to ensure the config/options would switch frameworks. I'm not going to commit anything until I have an implementation in place.

@benswinburne @bilby91 ava support added, see #60 (it's a bit of a hack, but it allows users to run with ava)

please add tests to the `BotTester.mocha.spec` and `BotTesterFailure.mocha.spec`.

I think it would be helpful to make a unique case to assert against. For instance ```javascript botTester.sendMessageToBot('something', (message) => { // do things return 'hello' }, 'hello') ``` so...

If an error is thrown inside a test step, that step will be recorded as an error. If a dev wants to fail in their test, that approach would still...