All Projects → bahmutov → cypress-get-it

bahmutov / cypress-get-it

Licence: other
Get elements by data attribute by creating a Cy command on the fly

Programming Languages

javascript
184084 projects - #8 most used programming language
HTML
75241 projects

Projects that are alternatives of or similar to cypress-get-it

cypress-watch-and-reload
Reloads Cypress when one of the watched files changes
Stars: ✭ 46 (+100%)
Mutual labels:  cypress, cypress-io, cypress-plugin
cypress-xpath
Adds XPath command to Cypress test runner
Stars: ✭ 145 (+530.43%)
Mutual labels:  cypress, cypress-io, cypress-plugin
cypress-browserify-preprocessor
Cypress preprocessor for bundling JavaScript via browserify
Stars: ✭ 23 (+0%)
Mutual labels:  cypress, cypress-io, cypress-plugin
cypress-example-docker-compose
Example running Cypress tests against Apache server via docker-compose
Stars: ✭ 106 (+360.87%)
Mutual labels:  cypress, cypress-io
todo-graphql-example
Example Todo app on top of json-graphql-server
Stars: ✭ 20 (-13.04%)
Mutual labels:  cypress, cypress-io
cypress-plugin-stripe-elements
A small Cypress plugin that assists you in filling in Stripe Elements inputs
Stars: ✭ 22 (-4.35%)
Mutual labels:  cypress, cypress-plugin
cypress-example-docker-circle-workflows
Cypress + Docker + CircleCI Workflows = ❤️
Stars: ✭ 29 (+26.09%)
Mutual labels:  cypress, cypress-io
cypress-mochawesome-reporter
Zero config Mochawesome reporter for Cypress with screenshots
Stars: ✭ 48 (+108.7%)
Mutual labels:  cypress, cypress-io
cypress-upload-file-post-form
Solution for two Cypress testing use-cases I came across with: perform a direct http FORM request to the server containing a file and other parameters and upload a file into a form before submission
Stars: ✭ 59 (+156.52%)
Mutual labels:  cypress, cypress-io
cypress-hyperapp-unit-test
Unit test Hyperapp components using Cypress
Stars: ✭ 26 (+13.04%)
Mutual labels:  cypress, cypress-io
snapshot
Adds value / object / DOM element snapshot testing support to Cypress test runner
Stars: ✭ 114 (+395.65%)
Mutual labels:  cypress, cypress-io
cypress-dotenv
Cypress plugin that enables compatability with dotenv
Stars: ✭ 47 (+104.35%)
Mutual labels:  cypress, cypress-plugin
cypress-angularjs-unit-test
Unit test Angularjs code using Cypress.io test runner
Stars: ✭ 23 (+0%)
Mutual labels:  cypress, cypress-io
cypress-example-circleci-orb
Demo of using the Cypress CircleCI Orb
Stars: ✭ 26 (+13.04%)
Mutual labels:  cypress, cypress-io
cypress-test-tiny
Tiny Cypress E2E test case
Stars: ✭ 48 (+108.7%)
Mutual labels:  cypress, cypress-io
cypress-angular-unit-test
Trying to load and bootstrap Angular component dynamically inside Cypress
Stars: ✭ 146 (+534.78%)
Mutual labels:  cypress, cypress-io
instrument-cra
Little module for CRA applications to instrument code without ejecting react-scripts
Stars: ✭ 61 (+165.22%)
Mutual labels:  cypress, cypress-io
cypress-browser-permissions
A Cypress plugin to set launched browser preferences including permissions like Geolocation, Notifications, Microphone, etc.
Stars: ✭ 40 (+73.91%)
Mutual labels:  cypress, cypress-plugin
svelte-pwa-now
A PWA ready Svelte v3.0 starter template with Tailwind, Now integration and optional Typescript suppot
Stars: ✭ 138 (+500%)
Mutual labels:  cypress, cypress-io
cypress-retry
Retry just the failed Cypress.io tests using Cypress module API and AST rewriting
Stars: ✭ 16 (-30.43%)
Mutual labels:  cypress, cypress-io

cypress-get-it CircleCI renovate-app badge

Get elements by data attribute by creating a Cy command on the fly

NPM

Why

According to the Cypress best practices for Selecting Elements using dedicated test id data attributes is the most stable way of finding elements during end-to-end tests. Yet typing the full selector is ... annoying.

<div data-test-id="foo">foo</div>
cy.get('[data-test-id="foo"]').should('have.text', 'foo')

Who has time for this!

So you could make a little utility function

const tid = s => `[data-test-id="${s}"]`
cy.get(tid('foo')).should('have.text', 'foo')

Hmm, sure, but what if your HTML markup has different data attributes? Like this

<div data-test-id="foo">foo</div>
<div data-test="bar">bar</div>
<div test-id="baz">baz</div>

Do you need to write 3 different helper functions? No. With cypress-get-it you can create data attribute selector methods with descriptive names. In fact, the actual selector will be created from the method name on the fly. You want to get element with data-test-id=foo? Just use camel cased words and call cy.getDataTestId('foo'). The above elements become

cy.getDataTestId('foo').should('have.text', 'foo')
cy.getDataTest('bar').should('have.text', 'bar')
cy.getTestId('baz').should('have.text', 'baz')

cypress-get-it

So any element attribute like foo-bar-baz="something" could be fetched with descriptive cy.getFooBarBaz("something").

How it works

Load this plugin from your support file and it will replace global cy instance with an ES6 Proxy which will intercept any methods calls to get... and will call cy.get with the right selector automatically.

Install and use

npm i -D cypress-get-it

Require this module from your cypress/support/index.js

require('cypress-get-it')

Small print

Author: Gleb Bahmutov <[email protected]> © 2019

License: MIT - do anything with the code, but don't blame me if it does not work.

Support: if you find any problems with this module, email / tweet / open issue on Github

MIT License

Copyright (c) 2019 Gleb Bahmutov <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].