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
First thanks for this gem, it just magically removed the issues we had about where to put the flash messages across different pages. Just don't put them inside the layout, put them above it ! :)
Then, the one problem I encountered was that a lot of my acceptance tests started to fail because they are relying on the flash message to check if for example a resource has been created, updated, destroyed, or the user has been logged in or out.
One solution I found was not to use use Gritter in the testing environment and fall back to classic flash notices, but then we don't really test the actual behavior of the app,
Another one would be to run those tests with js: true so the Gritter message is actually shown, but this would significantly slow down all those tests.
Yet another one would be not to rely on the flash notices at all in the tests, but then it would be some part of the business logic that would be lost : the fact that the user gets noticed about the result of his actions.
But as you can see none of those solutions is ideal.
So I wondered what you guys do in those cases, and if we could come up with a nice solution to include in the doc for everyone to see.
Cheers !
The text was updated successfully, but these errors were encountered:
Hi there,
First thanks for this gem, it just magically removed the issues we had about where to put the flash messages across different pages. Just don't put them inside the layout, put them above it ! :)
Then, the one problem I encountered was that a lot of my acceptance tests started to fail because they are relying on the flash message to check if for example a resource has been created, updated, destroyed, or the user has been logged in or out.
One solution I found was not to use use Gritter in the testing environment and fall back to classic flash notices, but then we don't really test the actual behavior of the app,
Another one would be to run those tests with js: true so the Gritter message is actually shown, but this would significantly slow down all those tests.
Yet another one would be not to rely on the flash notices at all in the tests, but then it would be some part of the business logic that would be lost : the fact that the user gets noticed about the result of his actions.
But as you can see none of those solutions is ideal.
So I wondered what you guys do in those cases, and if we could come up with a nice solution to include in the doc for everyone to see.
Cheers !
The text was updated successfully, but these errors were encountered: