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

Expected State, Page State comparison report printout bug #23

Open
tomrdale opened this issue Mar 27, 2018 · 0 comments
Open

Expected State, Page State comparison report printout bug #23

tomrdale opened this issue Mar 27, 2018 · 0 comments
Labels
bug Something isn't working

Comments

@tomrdale
Copy link
Contributor

tomrdale commented Mar 27, 2018

Description:

When the effects action fails during execution, and the report is printed out to show the difference between page state and expected state, the printout does not show any thing from expected or page state if the model section of the component does not have a property that we expect during the effects.

Steps to reproduce:

  1. Create an entry component to go to a website
  2. Have at least one component that is added to expected state for the effects of going to the website
  3. Add an property to the state when creating the component that does not exist inside the model of the component you are adding
  4. Run the tests, the effects will fail with a bugged print report

Expected Behavior:

When the report is printed out, it should show the value we expected, and the page state should tell us undefined, or something that shows it was not part of the calculated model

@tomrdale tomrdale added the bug Something isn't working label Mar 27, 2018
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