Sign in and reach the account dashboard
describe('account dashboard access', () => {
it('signs in with the QA account', () => {
cy.visit('/login');
cy.env(['QA_EMAIL', 'QA_PASSWORD']).then(({ QA_EMAIL, QA_PASSWORD }) => {
cy.get('input[name="email"]').type(QA_EMAIL, { log: false });
cy.get('input[name="password"]').type(QA_PASSWORD, { log: false });
cy.contains('button', 'Sign in').click();
});
cy.location('pathname').should('eq', '/dashboard');
cy.get('[data-cy="account-menu"]').should('be.visible');
cy.contains('h2', 'Recent activity').should('be.visible');
cy.get('[data-cy="login-error"]').should('not.exist');
});
});Illustrative Cypress JavaScript spec using built-in commands. Configure baseUrl and supply QA_EMAIL and QA_PASSWORD in the Cypress test environment. These credentials are read with cy.env(). Keep test isolation enabled. This example account has no authenticator challenge. Source 1 · checked 2026-10-23. Source 2 · checked 2026-10-23.
Name: Account dashboard access Starting path: /login Environment: Staging Instructions: Sign in with the saved QA login and open the account dashboard. Expected: The account menu and recent activity are visible. A sign-in error or unresolved login challenge does not pass.
Store the email and password in an environment login. When the sign-in challenge itself is under test, select Start logged out under Options, or leave Reuse login sessions off on the login. Session reuse is off by default. If your real account needs an authenticator code, save its setup key and describe that challenge too. The benchmark below demonstrates a blocked prerequisite, not successful authentication.
The run ended with an Error status, which our benchmark scores as cannot verify: the security check failed and no credentials were supplied. It illustrates an unresolved login prerequisite, not a successful sign-in or proof that your authentication will work.