Security News
Opengrep Emerges as Open Source Alternative Amid Semgrep Licensing Controversy
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
cypress-react-router
Advanced tools
Adds cy.routerNavigate() command to the Cypress object to navigate using the React Router Dom history API. The command take the to and an optional options object as parameters.
npm install cypress-react-router
Adds cy.routerNavigate()
command to the Cypress object to navigate using the React Router Dom useNavigate()
API. The command take the to
and an optional options
object as parameter.
Typings should be added as follows in tsconfig.json:
{
"compilerOptions": {
"lib": ["es5", "dom"],
"target": "es5",
"types": ["cypress", "cypress-react-router"]
},
"include": ["**/*.ts"]
}
If you are wondering if you should use this package the most likely answer is no.
In most cases you should do something like:
cy.visit('/')
cy.get('[href="/article/42"]').click();
Or use some other cy.get()
selector, or even better cy.findByRole('link', { name: 'Article 42' })
from Cypress Testing Library.
So if you should not use this normally why does it exist?
In some cases you need to do setup work and the navigate to some well know route with previously setup data. So you might do something like:
cy.visit('/');
cy.login();
cy.visit('/article/42');
The problem here is that the second cy.visit()
reloads the application from the server. And if your application is a Single Page Application or SPA using React Router Dom you have just lost all state setup with the call to your custom cy.login()
command.
So instead of calling cy.visit()
a second time we want to do a history.push()
like you would in the React application and what happens if you click on a <Link />
component in the browser. And that is what this package will let you do.
In the file containing your <BrowserRouter />
or <HashRouter />
add the <CypressHistorySupport />
import React from 'react';
import { BrowserRouter } from 'react-router-dom';
import { CypressHistorySupport } from 'cypress-react-router';
const App = () => {
return (
<BrowserRouter>
<CypressHistorySupport />
{/* Your other components */}
</BrowserRouter>
);
};
In /cypress/support/commands.js
add support for the router commands
import 'cypress-react-router/add-commands';
Then in your Cypress tests use the cy.routerNavigate()
command as needed.
context('Open secure articles', () => {
beforeEach(() => {
cy.visit('/');
cy.login();
});
it('navigates to article 42 without reload', () => {
cy.routerNavigate('/article/42');
// Do whatever you need to do
});
});
Make sure to use the correct version of this library for you!
Version 1.* of this package is intended for use with React Router DOM version 5. Use the cy.historyPush()
and cy.historyReplace()
commands to execute the respective history.push()
and history.replace()
functions.
Version 2.* of this package is intended for use with React Router DOM version 6 which has an different API. Use the cy.routerNavigate()
command to execute the navigate()
function.
FAQs
Adds cy.routerNavigate() command to the Cypress object to navigate using the React Router Dom history API. The command take the to and an optional options object as parameters.
The npm package cypress-react-router receives a total of 5,459 weekly downloads. As such, cypress-react-router popularity was classified as popular.
We found that cypress-react-router demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.