Skip to content
This repository has been archived by the owner on Jan 27, 2023. It is now read-only.

No ability for multiple possible responses #3

Open
kbrimble opened this issue Feb 3, 2017 · 1 comment
Open

No ability for multiple possible responses #3

kbrimble opened this issue Feb 3, 2017 · 1 comment

Comments

@kbrimble
Copy link
Owner

kbrimble commented Feb 3, 2017

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.

@anth12
Copy link

anth12 commented Jun 8, 2017

@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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants