Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BotTest: ProcessResult.goesToState ignores visited states, if there were reactions.go #71

Open
nikvoloshin opened this issue Oct 6, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@nikvoloshin
Copy link
Contributor

nikvoloshin commented Oct 6, 2020

Let's assume the following scenario:

state("main") {
	state("first") {
		activators {
			regex("first")
        }

		action {
			reactions.go("../second")
		}
	}

	state("second") {
	
	}
}

And the following test case:

withCurrentContext("/main")
query("first") goesToState "/main/first" endsWithState "/main/second"

Expected behavior:
The test succeeds

Actual behavior:
The test fails because of goesToState

@nikvoloshin nikvoloshin added the bug Something isn't working label Oct 6, 2020
@nikvoloshin nikvoloshin changed the title ProcessResult.goesToState ignores noContext states if they do reactions.go DialogContext.currentState ignores noContext states if they do reactions.go Oct 6, 2020
@nikvoloshin nikvoloshin changed the title DialogContext.currentState ignores noContext states if they do reactions.go BotTest: ProcessResult.goesToState ignores visited states, if there were reactions.go Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant