Project "Tests and Documentation Maker"

Developers can record user interaction steps to specify the intended use of their implemented functionality as Cypress scripts, which are used both for end-to-end testing as well as for end-user documentation.

In this context What links here? Main Page Project "MWStake Certified Extensions" Software "cypress"

Overview

1. Set up Software "cypress".
2. Configure cypress.config.js.
3. Assemble your use cases using parametrized blocks.
4. Run WYSIWYG interactive tests against Chrome, Firefox, etc.
5. Get automagically parsed documentation.

How to use

Configure and run the tests

1. PENDING: Somehow get https://github.com/MWStake/cypress-commands-core, which is an idea for the final place for what is currently https://github.com/dataspects/mediawiki-pages-EPPO/blob/main/cypress/support/commands.js LEX2206071345.
2. ACTION: Run Cypress/Cypress from Software "cypress"
3. ACTION: Add project by navigating EXACTLY into the root folder of a project, e.g. into ~/mediawiki-pages-EPPO/ (this is where the `cypress/` folder is/will be located in)
   • Cypress will indicate whether E2E testing is already configured
4. Set baseUrl in ~/mediawiki-pages-EPPO/cypress.config.js and restart

Create the test documentation

See https://github.com/dataspects/tests-documentation-maker

Develop

• https://docs.cypress.io/examples/examples/recipes
• https://docs.cypress.io/guides/core-concepts/writing-and-organizing-tests
• https://docs.cypress.io/guides/references/best-practices
  • https://example.cypress.io/commands/querying#best-practices
• https://docs.cypress.io/guides/references/assertions

Collecting MWStake best practices: #MWSTAKEBP