Skip to content
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.

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

Change sync button title attribute #2814

Merged
merged 3 commits into from
Jun 14, 2022
Merged

Change sync button title attribute #2814

merged 3 commits into from
Jun 14, 2022

Conversation

burhandodhy
Copy link
Contributor

@burhandodhy burhandodhy commented Jun 1, 2022

Description of the Change

This PR changes the Sync button title attribute to Sync Page and Settings button title to Settings Page and also add the E2E test.

Closes #2793

Verification Process

  • Go to Settings Page.
  • Hover on the Sync button. The title would be Sync

Changelog Entry

Changed: Sync button Title.

Credits

Props @burhandodhy @JakePT

@felipeelia
Copy link
Member

@burhandodhy instead of simply "Sync", let's say "Sync Page" (and "Settings Page".)

1 similar comment
@felipeelia
Copy link
Member

@burhandodhy instead of simply "Sync", let's say "Sync Page" (and "Settings Page".)

@felipeelia felipeelia modified the milestone: 4.2.1 Jun 7, 2022
@burhandodhy burhandodhy self-assigned this Jun 7, 2022
@burhandodhy burhandodhy marked this pull request as ready for review June 8, 2022 10:51
Comment on lines 1 to 7
describe('Settings Page', () => {
it('Can see a Sync and Settings buttons on Settings Page', () => {
cy.visitAdminPage('admin.php?page=elasticpress-settings');
cy.get('.dashicons.start-sync').should('have.attr', 'title', 'Sync Page');
cy.get('.dashicons.dashicons-admin-generic').should('have.attr', 'title', 'Settings Page');
});
});
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is GREAT to see tests like these coming through, @burhandodhy, congrats, and thanks! Can we please move it from a whole new test to the already existent general.spec.js? The links should be on all (or almost all) pages, so although it makes sense to pick one to check, we can save a settings-page.spec.js to something particular to that page, like checking if tabs change, etc. What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@felipeelia agree with you. settings-page.spec.js should only have tests that are related to settings page. I move the test to general.spec.js

@felipeelia felipeelia removed their assignment Jun 13, 2022
@felipeelia felipeelia merged commit 96eb902 into develop Jun 14, 2022
@felipeelia felipeelia deleted the fix/2793 branch June 14, 2022 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change sync button title attribute
2 participants