Skip to content

Support system testing environment #16207

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.

Sign up for GitHub

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

Jump to bottom
Closed
6 of 10 tasks
JessicaSachs opened this issue Apr 26, 2021 · 2 comments · Fixed by #18574
Closed
6 of 10 tasks

Support system testing environment #16207

JessicaSachs opened this issue Apr 26, 2021 · 2 comments · Fixed by #18574
Assignees
@flotwig

Comments

@JessicaSachs
Copy link
Contributor

JessicaSachs commented Apr 26, 2021 •
edited by flotwig
Loading

We should re-use the harness created inside of server/tests/e2e because the project configuration is mostly the same between testingTypes.
@JessicaSachs JessicaSachs self-assigned this Apr 26, 2021
@JessicaSachs JessicaSachs changed the title Support playground testing environment Support system testing environment Apr 27, 2021
@JessicaSachs JessicaSachs mentioned this issue May 5, 2021
Merged
1 task
@cypress-bot cypress-bot bot added stage: needs review The PR code is done & tested, needs review stage: work in progress and removed stage: needs review The PR code is done & tested, needs review stage: work in progress labels May 5, 2021
@brian-mann
Copy link
Member

brian-mann commented Oct 7, 2021 •
edited by flotwig
Loading

  • copy only the project you’re working in to .projects
  • symlink .projects to /tmp/projects so it doesn’t pollute git AND so it doesn't use node_mods
  • research circle ci timings to better understand if we could improve CI performance, and not have to manually balance our spec files
  • namespace system-tests as @tooling/system-tests but leave them in the root, but possibly move into a ./tooling/system-tests once thorstens work is merged in (since he’s adding a lot of private packages for our build/script process)
  • possibly also could move ./scripts to become ./tooling/scripts if they need their own package.json
  • maybe make project take a string and automatically use fixtures
  • pass e2e/ct/both if projects can run on both (or just one or the other) as opposed to creating a systemTests.it(...)
  • don’t make project use a default, make it required so it’s clear what project is going to be used
  • avoid mass file renames to prevent git from cluttering up until we’ve settled on a namespace pattern
  • pull and make sure that yarn test 3_user_agent_spec.js runs on your machine, and then merge in develop so you know its all working

@jennifer-shehane jennifer-shehane mentioned this issue Oct 8, 2021
Closed
@cypress-bot cypress-bot bot added stage: needs review The PR code is done & tested, needs review stage: work in progress and removed stage: work in progress stage: needs review The PR code is done & tested, needs review labels Oct 14, 2021
@flotwig flotwig mentioned this issue Oct 20, 2021
Merged
1 task
@cypress-bot cypress-bot bot added stage: needs review The PR code is done & tested, needs review and removed stage: work in progress labels Nov 22, 2021
@cypress-bot cypress-bot bot added stage: pending release and removed stage: needs review The PR code is done & tested, needs review labels Nov 24, 2021
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Nov 24, 2021

The code for this is done in cypress-io/cypress#18574, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flotwig flotwig

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test: node_modules installs for system-tests, other improvements cypress-io/cypress
4 participants
@flotwig @chrisbreiding @brian-mann @JessicaSachs