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

feat: add footer to the settings #18867

Merged
merged 3 commits into from
Nov 14, 2021
Merged

Conversation

elevatebart
Copy link
Contributor

@elevatebart elevatebart commented Nov 10, 2021

User facing changelog

Added a footer to the bottom of the settings page to go back to the launchpad

Details

Screen.Recording.2021-11-09.at.10.06.17.PM.mov

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Nov 10, 2021

Thanks for taking the time to open a PR!

@cypress
Copy link

cypress bot commented Nov 11, 2021



Test summary

18647 2 216 7Flakiness 4


Run details

Project cypress
Status Failed
Commit fee75d3
Started Nov 14, 2021 11:24 PM
Ended Nov 14, 2021 11:37 PM
Duration 12:08 💡
OS Linux Debian - 10.9
Browser Multiple

View run in Cypress Dashboard ➡️


Failures

Run group: 5x-driver-electron (Linux, Electron )
commands/files_spec.js Failed
1 ... > throws when there is an error writing the file
Run group: 2x-desktop-gui (Linux, Electron )
settings_spec.js Failed
1 Settings > file preference panel > loads preferred editor and available editors

Flakiness

commands/net_stubbing_spec.ts Flakiness
1 network stubbing > waiting and aliasing > can timeout waiting on a single request using "alias.request"
commands/xhr_spec.js Flakiness
1 src/cy/commands/xhr > abort > aborts xhrs currently in flight
cypress/proxy-logging-spec.ts Flakiness
1 ... > works with forceNetworkError
e2e/redirects_spec.js Flakiness
1 redirection > meta > binds to the new page after a timeout

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

@@ -310,6 +310,10 @@
"testingPreferences": {
"title": "Testing Preferences",
"description": "Configure your testing environment with these flags"
},
"footer": {
"text": "You can reconfigure the component testing settings for this project if you’re experiencing issues with your Cypress configuration.",
Copy link
Contributor

Choose a reason for hiding this comment

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

This message should be specific to the currently selected testing type i.e. You can reconfigure the ${testingType} testing settings for this project if you’re experiencing issues with your Cypress configuration.

Copy link
Contributor

Choose a reason for hiding this comment

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

How about we just say "You can reconfigure the settings for ..." since you can potentially change to another testing type.

@lmiller1990 lmiller1990 merged commit 9e70f1d into unified-desktop-gui Nov 14, 2021
@lmiller1990 lmiller1990 deleted the feat/settings-footer branch November 14, 2021 23:41
tgriesser added a commit that referenced this pull request Nov 17, 2021
* 10.0-release:
  feat: improve vite DX (#18937)
  feat: Use plugins on config files (#18798)
  BREAKING CHANGE: trigger major bump
  BREAKING CHANGE: trigger major bump
  fix: fix cypress/package.json crasher
  fix(breaking): change circle.yml to release binary
  fix: build-prod-ui deps before build-prod packages
  feat: implement spec list tree (#18901)
  chore: adding 10.0-release to the circle.yml build script (#18926)
  feat(app): remove __vite__ route and default to unified runner (#18909)
  fix: app layout + specs list review (#18862)
  feat(app): show previous versions (#18838)
  feat: scaffold integration files in app (#18763)
  feat: add footer to the settings (#18867)
  fix: Exit when both --e2e and --component flags are passed in (#18855)
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.

3 participants