@jperata - I'd love to show both the input utterance and the expected result phrase (or some of it) in the test results. e.g. (pseudo code)
{
input: "Hello Bespoken!":
expected: "Hello, How are you doing?"
}Right now, either from the command line or the html (jest-stare based) output, I only see the input phrase (or intent & slots) and not the expected response. It's like hearing one side of a conversation.
Can you help me find where to look for how the describe block getting specified? Is it possible for me to easily modify that to add a bit of the expected result for passing tests?
@dmarvp No luck, still need to control-C ath the end of the tests, even from standard terminal window (vs VSCode terminal). Ends like this:
Test Suites: 2 passed, 2 total
Tests: 4 passed, 4 total
Snapshots: 0 total
Time: 26.993s, estimated 29sStuck there and I need to control c before I can run again.
bst test && echo All DoneNever see the
All Done msg.Question: How would I do cleanup after the tests have run to close database connection for example? Is there a hook for that or do I need to figure out the jest tests?
filter property inside your testing.json file. It allows you to run custom code before and after each test or test suite: https://read.bespoken.io/end-to-end/guide/#filtering-during-test
FYI to anyone who sees something like I did, where the tests are not closing the process after runing:
IF you are using a database even for unit test :-( ... Make sure you are closing the connections to the db after some idle period.
For those using redis, you can just use redis_client.unref() immediately after you create the redis client object. That will ensure after the commands run, it will close the connections. You may want to put this inside of conditional context flag, since performance will be better in production if you are not aggressive about closing connections.
Test your configs, your mileage may very :-)
could not read source map for ...bespoken-tools/bin/bst.js.map (and a many many more like that), this is a VS Code bug, not directly related to bespoken-proxy.TLDR version: You can fix by updating your launch.json file that kicks off the bespoken proxy.
More info here: microsoft/vscode#102042 (and links from there.
I am your IT helpdesk assistant"
