[Project description]
If you are looking for something specific, you can jump right into the relevant section from here.
5.Git
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
Cypress is a next generation front end testing tool built for the modern web. It can test anything that runs in a browser. For Cypress features, please check https://docs.cypress.io/guides/overview/why-cypress.html#Features Tests are written in cypress version 4.0
- Clone the repo
git clone [repo ssh]- Install dependencies
npm install- Open cypress
npm run cypress- To commit your changes
npm run commit5.To run cypress headless to view how many test passed and failed on the terminal ...sh npm run cy:run -- --record --key 4e3bda2b-bbc2-476d-9076-01ab3833c180 "cypress/integration/common/homePage-test.js ...
| Folder | Description |
|---|---|
| Fixtures | Used as external pieces of static data that can be used by your tests. Fixture files are located in cypress/fixtures by default, but can be configured to another directory. |
| Integration | Used for creating test suits.Test files are located in cypress/integration by default, but can be configured to another directory.We are writing tests in js.Test file naming convention shall include the word test for easy documentation generation i.e feature1-test.js |
| Plugin | Used to load plugins By default.Cypress will automatically include the plugins file cypress/plugins/index.js before every single spec file it runs. |
| Support | Used to create various custom commands and overwrite existing commands.This file runs before every single spec file. |
| Utilities | Used to include all common methods needed for tests, Contain page methods (methods to interact with page elems), generic functions (generate name, email, date ..etc) and assertions (used for needed assertions) |
- esLint is being used to enforce js styles and conventions.
- esLint autocorrect is being used which automatically corrects warnings and errors.
- Excluded file: package-lock.json
- esDoc is being used for code documentation
devshould be the semi-stable branch.mastershould have the code that is fully stable.- A new branch should be created for every major feature
<feature-name>.- one-way-booking