You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 27, 2023. It is now read-only.
Currently all of the {Property}Matches() responses fail the test if the regex isn't matched (aside from Activity.Text).
This means that bots that have "randomised" responses cannot be tested without doing large regexes with pipes between the different things that a bot could say.
The text was updated successfully, but these errors were encountered:
@kbrimble I encountered this same conundrum and at first matched with regex | but it quickly got out of hand and is not maintainable when updating the random responses.
For me the content is stored in a key/value store, so when the bot is chatting over direct line with unit test conversation rather than sending the random message it returns the reference key which allows for content to be updated without breaking unit tests.
I know this isn't a direct solution as it comes with the overhead of offloading the content elsewhere but I found it a perfect solution.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently all of the
{Property}Matches()
responses fail the test if the regex isn't matched (aside fromActivity.Text
).This means that bots that have "randomised" responses cannot be tested without doing large regexes with pipes between the different things that a bot could say.
The text was updated successfully, but these errors were encountered: