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

Feature/share buttons #140

Merged
merged 8 commits into from
Mar 1, 2024
Merged

Feature/share buttons #140

merged 8 commits into from
Mar 1, 2024

Conversation

thomas-desmond
Copy link
Contributor

@thomas-desmond thomas-desmond commented Feb 20, 2024

Adding a "Share" button to the outcome page that brings up a modal with a copy-able URL and share buttons for popular social media platforms.

@thomas-desmond thomas-desmond self-assigned this Feb 20, 2024
Copy link

vercel bot commented Feb 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sitecore-migration-game ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 26, 2024 5:24pm

@thomas-desmond
Copy link
Contributor Author

Copy link
Contributor

@dylanyoung-dev dylanyoung-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will say, I love that we can review specific outcome pages. Also like the messaging. Would be cool if we can play with tweaking the messaging in the future, so that we could see what messages engage the best. (But obviously out of scope for this item).

So just one short comment about the test, but I don't think that's necessary to change. So looks good.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if combining multiple things in a test is a good idea. For now just a generalized comment. Nothing to change I don't think. But I was wondering how you might use before (which could run the steps to get to the outcome page) and then have individual tests for each of the cases you want to test. Not sure that's how that feature works lol

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely don't want to run the same flow multiple times to test different things. So I'm not sure that which I thought of works where it only runs the test once up to the outcome page, but maybe something to look into?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. We should have a few full-flow tests from beginning to end, but I don't want one test to end up testing 15 things working on the outcome page.

I think now that we have outcome pages we could visit the URL /outcome/48fc3ad8-ecc4-4a53-a07b-2cd136a59959 as the first step of the cypress test. We don't need to go through the whole flow for certain things like the share button.

Merging this for now but any further outcome page tests we should consider just navigating directly to a known existing outcome.

@thomas-desmond thomas-desmond merged commit d1d06eb into main Mar 1, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants