Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 12 02:50

    ecruzado on Version2-7-0

    (compare)

  • May 12 02:48

    ecruzado on master

    fix homophones for non asci (#7… (compare)

  • May 12 02:48
    ecruzado closed #708
  • May 12 02:35
    ecruzado opened #708
  • May 12 02:35

    ecruzado on fixHomophonesForNonAsci

    fix homophones for non asci (compare)

  • May 06 17:22

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 06 17:22
    dependabot[bot] commented #696
  • May 06 17:22

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 06 17:22
    ecruzado closed #696
  • May 06 17:22

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 06 17:22
    dependabot[bot] commented #697
  • May 06 17:22
    ecruzado closed #697
  • May 06 17:22

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 06 17:22
    dependabot[bot] commented #702
  • May 06 17:22
    ecruzado closed #702
  • May 06 17:22
    dependabot[bot] commented #703
  • May 06 17:22

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 06 17:22
    ecruzado closed #703
  • May 06 17:22
    dependabot[bot] edited #702
  • May 06 17:22
    dependabot[bot] edited #697
Diego Martín
@dmarvp
hi @TomV, the bst test command is not meant to keep the process open. Are you on the latest version of bst?
Tom V
@TomV

@dmarvp BST: v2.4.65 Node: v12.14.1 is what I'm running, might be the new VSCode.. (it can auto attach to node process for debugging, but I have that disabled..) I'll try in a standard terminal.

Should I upgrade to2.4.72?

Diego Martín
@dmarvp
we have updated the latest tag of bst this morning, please try using version v2.4.74 and see if that helps
Tom V
@TomV
Yes, I am doing that now! Thanks.. It does seem to work better in the standard terminal :-)
Tom V
@TomV

@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.

Tom V
@TomV
Just occurs to me that it may be waiting for something on my side, like a database handle to close.. My test is
bst test && echo All Done
Never 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?
Diego Martín
@dmarvp
You could use the 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
Tom V
@TomV
@dmarvp Thanks! Sounds like exactly the right tool... and it was an RT(F)M answer ... I may have missed it since I'm working on unit tests.. Thanks for the link 👍
Tom V
@TomV

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 :-)

Tom V
@TomV
FYI: anyone seeing the error 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.
John Kelvie
@jkelvie
Thanks for sharing this @TomV
Nitesh Chaudhary
@CHAUDHARYNKC_twitter
Hi, I'm running bst test --config tests/testing.json
but getting error "Expected value at [transcript] to ==
I am your IT helpdesk assistant"
can someone please help ?
Nitesh Chaudhary
@CHAUDHARYNKC_twitter
Please let me know if some more log information required. I'm following tutorial: https://blog.rasa.com/twilio-voice-rasa-tutorial/
Olubolar614
@Olubolar614
Hi, I'm currently unable to register online in order to access (login) bespoken dashboard, getting this error message "This domain is not allowed.Please use another email account or get in touch with us" .Please note, I'm using company's email address to register.I look forward to hearing from bespoken support team member.
xbootnek
@xbootnek
Are you planning a Google Actions sample app for testing?
John Kelvie
@jkelvie
Hi @xbootnek - we have a couple different examples, including this one:
Is that what you are looking for?
xbootnek
@xbootnek
Thanks for the rapid response. I issue bst test and get:
A testing.json file could not be found on this directory. Create one or use the --config option to specify its current location.
There is no testing.json present in the Git download.
John Kelvie
@jkelvie
Hi, you are correct. Sorry about that. Here is an example that is a Google Action, though it is built for DialogFlow:
xbootnek
@xbootnek
Sorry but DialogFlow won't hack it for me.
danagibson
@danagibson
I get an unexpected string at line 1697...I figured out another error that was at line 1179...turned out to be in my alexa interaction model...I've tried using the same method...adding characters to see if the line number changes...if the error just gave me the string it refers to...or the file it's in...something
danagibson
@danagibson
While I still would like to know why there isn't more information available...I did fix the issue by the method already described.
WendyB
@Wlb1557
Hi, setting up an e2e test and wondering if there is a practical way to store/reference response values in a file, as opposed to coding them in the .yml test script. The preference here is to reduce the number of locations in which we are storing/maintaining response values.