ecruzado on Version2-7-0
ecruzado on master
fix homophones for non asci (#7… (compare)
ecruzado on fixHomophonesForNonAsci
fix homophones for non asci (compare)
@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 29s
Stuck there and I need to control c before I can run again.
bst test && echo All Done
filterproperty 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.