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

chore: add v13 welcome page content #27549

Merged

Conversation

AtofStryker
Copy link
Contributor

@AtofStryker AtofStryker commented Aug 14, 2023

  • Closes N/A

Additional details

Adds the v13 welcome/splash page with updated content

Steps to test

How has the user experience changed?

PR Tasks

@AtofStryker AtofStryker force-pushed the chore/update_major_version_welcome_page_v13 branch from 5727579 to a59b58f Compare August 14, 2023 16:09
@AtofStryker AtofStryker changed the title feat: add v13 splash page content (wip) chore: add v13 welcome page content Aug 14, 2023
@AtofStryker AtofStryker self-assigned this Aug 14, 2023
@AtofStryker AtofStryker force-pushed the chore/update_major_version_welcome_page_v13 branch from 15f97f7 to 4fd745f Compare August 18, 2023 19:01
chore: add video link for v13 inside graphql context and root resolver. add migration tests outside of migration manager and update component tests to test aspects

chore: update copy to most recent. Needs onlink deployments

chore: opt for named slot in major version welcome as we still want to show the changes whether or not the video is present

chore: fix video margin by shrinking the margin for a more appealing loadout

chore: update onlinks for what is expected in deploy

chore: adjust margins around video, move video up, and reduce margin on major welcome title

chore: bump release date to 8/29

chore: update stubbed query to reference actual video
@AtofStryker AtofStryker force-pushed the chore/update_major_version_welcome_page_v13 branch from 56a4ca7 to fca2b37 Compare August 18, 2023 19:22
@AtofStryker AtofStryker marked this pull request as ready for review August 18, 2023 19:23
Copy link
Member

@jennifer-shehane jennifer-shehane left a comment

Choose a reason for hiding this comment

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

Content looks good, I didn't do a thorough code review and would like someone to do that and get it up and running in their review.

@AtofStryker
Copy link
Contributor Author

Content looks good, I didn't do a thorough code review and would like someone to do that and get it up and running in their review.

Sounds good. The v13 video is in staging currently, so whoever tests this would need to run:

CYPRESS_INTERNAL_ENV=staging yarn cypress:open

inside the packages/launchpad

@marktnoonan
Copy link
Contributor

I'll plan to pull this down later today and review!

@AtofStryker AtofStryker requested a review from tgriesser August 21, 2023 16:44
@AtofStryker
Copy link
Contributor Author

@tgriesser I want to double check and make sure I handled the resolution properly in the graphQL resolver.

/>
>
<template
v-if="videoHtml"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Will this pass if videoHtml is ''?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It does not. v-if only evaluates with the expression is truthy https://vuejs.org/guide/essentials/conditional.html#v-if

@@ -0,0 +1,10 @@
const { defineConfig } = require('cypress')
Copy link
Collaborator

Choose a reason for hiding this comment

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

Where do these get run?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

in the e2e migration test

describe('v13 migration welcome page with video', () => {

<div class="mb-[16px]">
<ExternalLink
href="https://on.cypress.io/changelog#12-0-0"
href="https://on.cypress.io/changelog?utm_source=splash-page&utm_campaign=v13#13-0-0"
Copy link
Contributor

Choose a reason for hiding this comment

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

Generally we use only 2 values for utm_source - Binary: App or Binary: Launchpad. Is this intentionally different from that? I realize it's not documented well. There's a sheet that wrangles these values, it would be good to add these there. Medium seems more suitable than "source" for "splash page" based on the existing pattern.

But also curious - is there a particular person expecting to do some analysis later based on these params, or are we more playing it safe?

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'm probably not the best person to ask about the utm_source, but it was in the approved copy for the splash page. I wonder if it makes sense to update the utm_source to Binary: App and leverage medium for the splash page . Heres the copy for reference. I can ask the GTM team in slack

Copy link
Contributor

Choose a reason for hiding this comment

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

Good idea to clarify in Slack. Being consistent is nice but there's not a hard and fast rule.

Copy link
Contributor

@marktnoonan marktnoonan left a comment

Choose a reason for hiding this comment

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

This all looks good to me, approving with the assumption that we figure out the UTM params before merge.

@cypress
Copy link

cypress bot commented Aug 23, 2023

29 flaky tests on run #50422 ↗︎

0 28013 1354 0 Flakiness 29

Details:

stub migration src in network performance launchpad test on video as abortcontr...
Project: cypress Commit: 2317e62e0e
Status: Passed Duration: 18:21 💡
Started: Aug 24, 2023 11:03 PM Ended: Aug 24, 2023 11:21 PM
Flakiness  e2e/origin/config_env.cy.ts • 1 flaky test • 5x-driver-firefox

View Output Video

Test Artifacts
cy.origin- Cypress.config() > serializable > overwrites different values in secondary if one exists in the primary Output
Flakiness  e2e/origin/commands/assertions.cy.ts • 1 flaky test • 5x-driver-firefox

View Output Video

Test Artifacts
cy.origin assertions > #consoleProps > .should() and .and() Output
Flakiness  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-firefox

View Output Video

Test Artifacts
... > correctly returns currentRetry Output
... > correctly returns currentRetry Output
... > correctly returns currentRetry Output
Flakiness  scaffold-component-testing.cy.ts • 1 flaky test • launchpad-e2e

View Output Video

Test Artifacts
scaffolding component testing > vuecli5vue3 > scaffolds component testing for Vue CLI 5 w/ Vue 3 project Test Replay Output Screenshots
Flakiness  config-files-error-handling.cy.ts • 1 flaky test • launchpad-e2e

View Output Video

Test Artifacts
Config files error handling > handles deprecated config fields Test Replay Output Screenshots

The first 5 flaky specs are shown, see all 17 specs in Cypress Cloud.

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.

…abortcontroller is difficult to test with current ctx setup
@AtofStryker AtofStryker force-pushed the chore/update_major_version_welcome_page_v13 branch from d31067f to 2317e62 Compare August 24, 2023 22:52
@AtofStryker AtofStryker merged commit 150b04c into release/13.0.0 Aug 24, 2023
@AtofStryker AtofStryker deleted the chore/update_major_version_welcome_page_v13 branch August 24, 2023 23:36
@cypress cypress bot mentioned this pull request Aug 25, 2023
3 tasks
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Aug 29, 2023

Released in 13.0.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.0.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Aug 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants