[Blog] Contributing to Meshery with End-to-End Automation Testing using Cypress

Contributors and community members are encouraged to post on https://layer5.io/blog. A new blog post fitting the following description is requested to be written by a community member:

Desired Title: Contributing to Meshery with End-to-End Automation Testing using Cypress Topic: cypress, test automation, meshery Core points to convey in the post:

Reference: https://layer5io.slack.com/archives/C011VPREG2Z/p1651162390443769?thread_ts=1651113754.202709&cid=C011VPREG2Z

Great question (“How to start of with cypress testing in Meshery?“), in the future I highly suggest to skim at existing questions in Layer5 Discuss community forum and posting the question if it hasn’t been made yet (No post there yet for this specific one) but answering your question you can (ordering is based on effort and need of cross collaboration, but you can mix and match freely):

Lee’s favorite (mine as well) “be a user”: become a whiny regular (Meshery UI) or power user (Meshery CLI) as technically possible to you, we welcome all levels of expertise. Installing, using and gaining familiarity with Meshery and its features is of great use and on the way we’d be delighted if you can raise any questions and suggestions you get (Have you installed Meshery? If not, try out the Quick Start Guide which would get you with a local User-Packaged version of Meshery up and running, What about Meshery’s features like Service Mesh Lifecycle, Application, Pattern, Configuration and/or Performance Management? If not familiar, you may look into articles/guides from this list: Architecture Adapters Concept, Meshery Functionality, Using Multiple Adapters Guide. Finally, for Managing and using service meshes through Meshery try out some of the Operation Guides and/or Meshery CLI Guides) Refer to our existing blog on “Functional Testing with Cypress in Meshery UI”: https://layer5.io/blog/meshery/functional-testing-with-cypress-in-meshery-ui Look into meshery/meshery repo issues with ‘cypress’ tag (just added this new tag) and jump into the discussion of existing issues, help split issues from umbrella/epic issues and looking into closed issues’ merged PR’s is also a good way of getting familiar of how this kind of contributions are made. Look into meshery/meshery repo’s /ui/cypress folder and see how existing tests are implemented. Reach out in the #cypress-testing to request for guidance on meshery, cypress and github workflow specifics as you bump into roadblocks.

Granted that this is a bit of a stretch of what a new contributor would do but I highly suggest to you and anyone really interested to be one of our alpha/beta users of content for some WIP changes for both “Contributing to Meshery UI” and soon-to-be new “Contributing to Meshery Cypress Tests”. (These are in my fork only, for now)

---

Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

• See contributing instructions
• See Layer5 site designs in this Figma project.

[leecalcote]

@MarioArriaga92 for your consideration…

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.