My plugins tools page

[asr0393]

Proposed changes

Type of Change

Production

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update
• Refactoring / housekeeping (changes to files not directly related to functionality)

Development

• Tests
• Dependency update
• Environment update / refactoring
• Documentation Update

Video

Checklist

• I have read the CONTRIBUTING doc
• I have viewed my change in a web-browser
• Linting and tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[circlecube]

Hey @asr0393 can you summarize the intent of this cypress test? They are not passing in the runner here, even though they may have worked locally for you.

It looks to be testing that the solutions page renders exactly what is represented in the fixture. I believe we have a test that checks one category and product as well as the accordion functionality, so not sure we need to check them all. See: https://github.com/newfold-labs/wp-module-solutions/blob/main/tests/cypress/integration/solutions-app.cy.js#L66-L90

To add more tests, please follow the notes here for adding tests for button states of entitlements: https://github.com/newfold-labs/wp-module-solutions/blob/main/tests/cypress/integration/solutions-app.cy.js#L94-L97

A test on the install plugins link could be useful though, but we should remove the domain from the URL in the test so it will work in every scenario.

[circlecube]

This is likely failing because in the runner the href will not match this. Try something more along these lines:

cy.get('a').contains('Add a New Plugin')
	.scrollIntoView()
	.should( 'be.visible' )
	.should( 'have.attr', 'href' )
	.and(
		'include',
		'wp-admin/plugin-install'
	);

The test doesn't need to click the link as that will take longer for the new page to load, since it can just check the href.

[asr0393]

The test is to verify the list of categories based on the solution plan as the catergories those are displayed for each solution(ecom,content creator and services) are different. Where in I tried to add the mock data for verify categories based on solution plan.