* develop: (40 commits)
fix(driver): Sticky elements within a fixed container will not prevent an element from being scrolled to (#18441)
chore: make `create` function on server.ts obsolete (#18615)
docs: Add instructions to squash commits to develop in Contributing (#18728)
fix(@cypress/react): throw if using Next.js swc-loader without nodeVersion=system (#18686)
refactor: remove Ramda (#18723)
chore: Increase paralleled machines for desktop-gui tests (#18725)
chore: Update Chrome (stable) to 95.0.4638.69 (#18696)
chore: release @cypress/vue-v3.0.4
chore: release @cypress/react-v5.10.2
chore: release @cypress/schematic-v1.5.3
fix: remove outdated registry link (#18710)
chore: release @cypress/schematic-v1.5.2
chore: release create-cypress-tests-v1.1.3
chore: Update Chrome (beta) to 96.0.4664.27 (#18676)
chore(tests): Remove flaky assertion that relies on png how compression (#18668)
fix: make sure to go back to no-specs when delete spec file (#17760)
fix: Next.JS 12 components testing failing with ` TypeError: Cannot read property 'traceChild' of undefined` (#18648)
Backport .gitignore from unified-desktop-gui
chore(docs): add 'Upgrading Electron' instructions (#18594)
release 8.7.0 [skip ci]
...
* feat: initial search input component
* Ugly LeftNav control
* chore: fixing the broken relative url specs
* feat: cleaning up the left nav styles and adding a more interactive spec
* chore: rebase
* wip: nav bar external link fix
* wip: active index
* wip: active index
* wip: more css modules
* wip: dark mode/light mode support devtools
* spwip: split left nav
* wip: runner-ui-changes
* wip: box shadows, borders, and more
* fix: types
* chore: extract component
* chore: extract component for readability
* chore: add checks for width on pane
* chore: refactor to make it more easier to understand what is rendered in panes
* chore: move things around
* chore: move things around
* chore: fix style
* chore: fix shortcuts
* tests: fix a test
* fix: fix screenshots feature
* chore: add placeholder
* chore: rebase
* fix: casing
* chore: build
* chore: old file
* chore: update
* chore: update name
* wip: fixing bugs in UI
* chore: improve resize logic
* chore: improve resize logic
* chore: remove unused code
* chore: styling
* chore: fix screenshotting
* chore: style
* chore: fix lint
* chore: bump bin size
* chore: revert changes in runnables
* fix: remove padding during screenshot
* chore: rebase and reauthor commit
* fix: correctly open spec list when focusing
Co-authored-by: Lachlan Miller <lachlan.miller.1990@outlook.com>
* chore: update driver with component testing
* feat: bring ct changes in reporter
* test: update script utils test
* fix: type issue
* test: add test for new ct behavior in driver
runScript can now use promises instead of files.
Thi test this new behavior
* tests(ct): tests for the reporter runable store
* fix: remove changes on event handling in driver
* build: augment zip size to avoid zip errors
* test: add renderin tests for reporter multispec
* test: better matcher for runnableHistory
Co-authored-by: Jessica Sachs <jess@jessicasachs.io>
* test: make the runscripts eval tests clearer
* refactor(reporter): main interface instead of type
* fix(reporter): runInAction when specRunId changes
* refactor(driver): remove restartRunner function
Co-authored-by: Jessica Sachs <jess@jessicasachs.io>
* fix(deps): update jimp to 0.13.0 🌟
* Bump max linux filesize for binary
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Jennifer Shehane <jennifer@cypress.io>
* electron@7.x
* node12.8.1-chrome78-ff70
* Revert "node12.8.1-chrome78-ff70" for now
This reverts commit db2d521994.
* update sendCommand to log on all sendcommands
* promisification in 6.x
* Revert "Revert "node12.8.1-chrome78-ff70" for now"
This reverts commit 57fe764098.
* fix sendcommand
* fix cdp in electron
* fix desktop-gui test
* skip tests that will be fixed by #4973
* bump MAX_ALLOWED_FILE_SIZE :/
* update electron browser spec
* make new dialog code null-proof
* add failing e2e test for issue 5475
* bump electron packager
* add e2e snapshot
* update deprecated electron getters/setters
https://github.com/electron/electron/blob/7-1-x/docs/api/modernization/property-updates.md
* build and test on Mac
* use electron-builder 20.41.0
that adds an option to use hardened Mac OS, which is necessary
for code notarization later.
See https://github.com/electron-userland/electron-builder/releases/tag/v20.41.0
and https://github.com/electron-userland/electron-builder/pull/3858
* electron-builder and pass hardenedRuntime: true
* uncomment build
* upload built binary on mac
* back to 20.41.0, trying after sign hook without success
* use current electron-builder alias instead of build
* retry smoke test on first failure
* testing
* trying to notarize signed app (that does not have node_modules yet)
* env variable names
* copy node_modules ourselves
* build and bundle binary on mac on circle, inject new context
* enable build steps before electron build
* increase mac build timeout
* update build folder on mac
* uncomment actual electron build command
* set linux target to zip
* set zip as target for all platforms
* updated steps
* put notarization hook back
* tweaks for icons
* remove dist electron before code sign
* icons per platform
* make node_modules copy path platform-specific
* fix linux build unpacked folder
* build mac
* fix lint
* test new mac binary against kitchensink
* working on Linux build
* try building entire thing on Linux
* removing correct electron dist folder
* increase zip size limit for now
* add folder rename on Linux from linux-unpacked to Cypress
* print file sizes before zipping
* move linux-unpacked to build dir function
* try deleting second electron file, but code signing probably would not work
* test windows build [build binary]
* ignore tsc errors
* windows build path
* windows [build binary]
* update windows build folder
* increase binary build timeout on Mac
* no need to pass our dist folder
* adding explicit list of additional binaries to code sign on mac
* yarn lock
* uncomment necessary build steps
* electron dir for Linux
* yarn lock again
* back to execa v3
* use execa v4 in packages launcher
* yarn lock again and again
* updated tests that use execa
* print build folder
* add executable name on Linux
* get rid of execa.shell in build scripts
* remove old and commented out code
* need to test building binary on Windows
* throw error from after sign hook if fails
* use execa to zip
* yarn lock
* fix after merge variable
* update test
* add nohoist ffmpeg installer
* patch
* yarn types pass
* yarn lock has binary
Co-authored-by: Zach Bloomquist <github@chary.us>
Co-authored-by: Brian Mann <brian.mann86@gmail.com>
* add packages/server experiments
* show experiments in desktop GUI
* add intro experiments text
* conditional message
* add experiments record to start of the headless run
* keep experiments in the config, remove duplicate logic
* small tweaks
* remove experimentalComponentTesting for now, separate PR
* rearrange settings spec into sections per panel
* do not crash if there are no experiments
* return component testing experiment
* work on styling of experiments panel + adding basic tests
* update settings spec text
* add unit tests for experimental features in cypress run output
* Add styling for 'non-enabled' status sign.
* add more experiments and key whitelist in experiments GUI
* add message when there are no experiments
* fix coffeelint
* fix merge in settings spec
* trailing whitespace
* make experiments info all live in one place
* add ts lint exception
* update unit test
* update run spec
* do not show experiments panel at all without experiments
* add more comments
* Update style of ON/OFF status for experimental features.
* remove empty messaging from experiments panel (since panel is no longer shown when empty)
* remove check for 'isEmpty' when showing list
* update lock file
Co-authored-by: Jennifer Shehane <jennifer@cypress.io>
* Add warning when setting CYPRESS_ENV to non-production value
* Add warning and update error when setting CYPRESS_ENV in config to non-production value
* Update config test/to throw
* we want warning, not throw
* Rename env var to CYPRESS_INTERNAL_ENV + fix warning to actually warn when staging
* update cli snapshot to include new 'info' command
* yarn.lock
* removed the warning from config, is overboard on our own tests 😓
* cleanup from review
Co-authored-by: Gleb Bahmutov <gleb.bahmutov@gmail.com>
* fix patch-package
- don't hoist dependencies that are patched, this way we can be assured the path is always correct
- put all patches in root postinstall so postinstall-postinstall is guaranteed to work
* wip
* Revert "fix patch-package"
This reverts commit 5583f21478.
* use per package patches
* don't ignor engines or silence
* try: make sinon patch devonly
* fix socketspec
* run full ci on this branch
* bump xcode tools to bump mac node version
* also run appveyor
* Revert "run full ci on this branch"
This reverts commit c3e52d09ec.
* Revert "also run appveyor"
This reverts commit bfe7b0499a.
- add needed deps in `ui-components` package
- upgrade `@cypress/webpack-preprocessor`
- refactor some eslint code, remove unused eslint scripts
- rename `build-js` scripts to `build-prod` since they'll only need to run when building for prod / checking for tsc errors
* enable using yarn
* enable lerna and yarn workspaces
No longer can reliably access node_modules via thei node_modules directory; yarn may optimize it via hoisting it up. This meant updating JS tasks that were copying files directly from node_modules directories. In these cases, pulled in a new package to resolve these correctly.
SCSS files remain impacted, but cannot easily import via JS. These paths have been modified, but it feels dangerous and incorrect to reach into a node_module to grab files like this.
Many prebuild steps were removed. I **think** the purpose of `check-deps-pre` is no longer needed, but need to confirm this.
* enabling test-unit script
removal of pretest-unit due to check-deps-pre
* removal of all `check-deps` and `check-deps-pre`
I do not think these are needed anymore
* remove npm run all
Replaced by `lerna run` and `lerna run --scope`
* use yarn in circle CI
appveyor to soon follow
* yarn in appveyor
* remove need for bin-upplaces using bin-up have a dev dependency on some package; mostly mocha. This mocha package will be optimized by yarn workspaces by hoisting it into the root; which is effectively what bin-up usage was mimicing.
* replace npm run with yarn in package files
* replace explict paths to internal packages with yarn bin
* remove unecessary link packages script and references
* properly require package for mocha
* removing yarn test in this package as it was just a proxy for test-*
* yarn test in root now reflects what is run in circle ci
* relax yarn version requirement for circle ci
* @packages/cli is really just cypress
also run test in parallel via `yarn test`; it runs test in all 10 packages
* ensure postinstall is called before prebuild
yarn does not call postinstall when nothing has installed; such is the case when everything has been cached
* vscode config uses yarn
* cannot rely on which node_modules dir a package is in
find the right node_module dir via `resolve-pkg`
* further relax yarn version for OSX build in circle ci
* resolve failing test
Regarding direct access to node_modules
* node version in mac build not sufficient
ignoring check of node/yarn versions when installing
* preinstall script does not exist
I **think** the reason to not install packages' modules (the reason for `--ignore-scripts` may be irrelevant with yarn workspaces managing the packages)
* upgrade mocha that was using --file
`--file` was introduce in >=5
* scope test runs to correct packages
* explictly close connections; otherwise script hangs after tests run
* refactor so npm and npx commads can be created
npx is used to utlize lerna for running across all packages sans cli
* properly resolve socket.io-client node_module
We cannot reach directly into node_modules to grab the socket.io-client file. Furthermore, running it locally will require resolving from a different cwd, the repo root, as opposed to the package's dist directory.
The existence of the file deterimes whether we are building the binary or running locally.
* remove unnecessary arg in vscode debug config
enable debugging in @packages/server to troubleshoot failing test
* another npm command found to be changed to yarn
* properly print colors to terminal
`lerna run` does not appear to print colors to the terminal properly. Changed to leverage `lerna exec`
See https://github.com/lerna/lerna/issues/1168
* add missing test scripts to packages that have partially have them
'test', 'test-unit', 'test-watch', and 'test-debug'
This makes running them from the root easier and enables debugging via IDE on more packages
* properly patch package in yarn workspaces
* another package needing to postinstall
* use existing script over explicit lerna exec
* patches must be copied to dist
* return to building on postinstall
* do not hoist driver's packagesThere are too many places we need driver's packages to not be hoisted when testing. We have *.html files in test with script tags srcing node_modules.
* wait-on is used in circle-ci and needs to be a root dep
No longer hoisted by `@packages/driver`. This previously worked only because it was hoisted. Adding it to root properly.
* update documentation based on new ergonomics
* launcher has unit tests that should be runnable via top level task
* more concise way to run build within cypress scope
* fix for unit test that never seemed to work
`getPathToExample` is really `getPathToExamples`
* bust cache based on yarn.lock changing
* define intra-dependencies among packages
Due to the way we build the binary, all are considered dev dependencies.
* address `jquery.scrollto` mismatched jquery version
Tell yarn to explicitly resolve `jquery@3.1.1` for any dependencies and sub-dependencies. The root issue is that `jquery.scrollto` package specifies jquery as a dependency instead of a peer dependency (which is correct). Its jquery version is set to the `>=1.8` which then resolves to 3.4.1. In doing so, it will patch its jquery instead of ours; meaning that `$.scrollTo` is not defined.
* add/remove deps from renovate
- bin-up is gone in favor of yarn workspaces and lerna from root
- check-deps is gone in favor of `yarn check --integrity`
- lerna added
* few misc yarn lock updates
* hope that this may speed up build binary
installing several of the same dep in >1 package will likely be sped up using yarn due to its machine-wide caching.
* yarn pack prefix version with a `v`
* auto-run `yarn install` when deps become out of date
When switching to a branch with a different set of required deps, running any of the main top level tasks (as seen in the `./CONTRIBUTING.md` guide) will check for deps changes via `yarn check --integrity` and run `yarn` in root if deps are out of sync.
* add clean top level task, remove prebuild
install => build => prebuild => check => install === no good
* address code review to undo formatting changes
* favor default imports over deconstructing imports
* favor @package resolution; pr feedback
* include a specific revision
for some reason, it cannot resolve the original SHA `29dafed297142d3b8a9d8a01842cbdf249a98b72`
using the next closes SHA
* properly cache yarn packagesfollowed guide: https://circleci.com/docs/2.0/yarn/
* lower barrier for contributors to get started
relax node version to be 12.0.0 or higher; will use node version found in `.node-version` in CI
* updates required after merging latest development
was getting type errors when building. recreating the `yarn.lock` file seemed to resolve the issue.
* hidden dep on a specific type version in server
made dep explicit and now it can build.
* update request to patched version
non-breaking changes to request was updated in server, but not everywhere else. It appears that transitive deps were using the 2.88.0 request version instead of the updated one for the server package.
* missing commit from previous commit/merge
* do not force a higher version of yarn than the default on circleci
* exclude e2e.js helper from stop-only command
* trying to bust node_modules cache.https://github.com/yarnpkg/yarn/issues/6412#issuecomment-537787740
* incorrect quotation tick placement
* fix: properly postinstall parse-domain
Do not explicitly script the shell invocation of a dependency's postinstall (parse-domain). The dependency's node_modules may not be where the package thinks they are and are not properly resolved.
It appears that postinstall will automatically be called when installing with yarn.
* run all CI stages
* fix win-appveyor-build.js
* Update CONTRIBUTING.md
Co-Authored-By: Zach Bloomquist <github@chary.us>
* Update CONTRIBUTING.md
Co-Authored-By: Zach Bloomquist <github@chary.us>
* Update CONTRIBUTING.md
Co-Authored-By: Zach Bloomquist <github@chary.us>
* Server package watching a specific test works correctly.
* PR feedback
* Correctly use yarn to pack (to get package size)
* correct size calculation
`yarn pack` does not output the file name like `npm pack` does. Correct this by explictly setting the filename.
* PR feedback
* PR feedback
* update readmes and testing commands from them
* do not include this in default build
* yarn is now installed by default
https://github.com/appveyor/ci/issues/1852
* do not include server in `yarn` auto build
* a few more npm references changed to yarn
* Revert "run all CI stages"
This reverts commit 9256aed99f.
* Update circle.yml
Co-Authored-By: Zach Bloomquist <github@chary.us>
Co-authored-by: Zach Bloomquist <github@chary.us>
