So, maybe I missed something obvious, but it seems like the functions to modify the current YesodExampleData are private, and one couldn't modify cookies. I think testing modifying the cookies seems like reasonable functionality to have, because users and browsers can obviously change them.

This is kind of a problem with all of yesod-test having generic names like get, but names like setCookie conflict with ones in Yesod itself. Thoughts on this? I prefixed them with test but maybe prefixing with y is better?

(In our application we've just imported yesod-test qualified, so we don't have this issue)

Before submitting your PR, check that you've:

• Bumped the version number
• Documented new APIs with Haddock markup
• Added @since declarations to the Haddocks for new, public APIs

After submitting your PR:

• Update the Changelog.md file with a link to your PR
• Check that CI passes (or if it fails, for reasons unrelated to your change, like CI timeouts)