Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 17:08:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 83

Important directories and their use cases

Browse source
This commit is contained in:
RachelElysia 2021-06-14 11:04:49 -04:00 committed by GitHub
parent 5e3beb367f
commit de116a3cb0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
cypress/README.md
View file

@ -1,6 +1,17 @@
# Cypress Testing
Cypress tests are designed solely for end-to-end testing. If this is your first time developing or running end-to-end tests, [Fleet testing documentation](https://github.com/fleetdm/fleet/blob/main/docs/4-Contribution/2-Testing.md) includes git instructions for test preparation and running tests.
## Fleet Cypress directories
### Integration directory
Cypress tests the integration of [entire features](integration/all/app) of the app.
With the roll out of teams, Cypress tests the user interface of each role of a user on the Basic Tier ([Fleet Basic Documentation](integration/basic/README.md)) and Core Tier ([Fleet Core Documentation](integration/basic/README.md)).
### Support directory
[Commands](support/commands.ts) that are shared across tests are located in the support directory.
## Opening Cypress locally
To open simply run:
@ -8,7 +19,7 @@ To open simply run:
`yarn cypress:open`
This will open up cypress locally and
allow you to view the current test suite, as well as start writing new tests.
allow you to view the current test suite, as well as start writing new tests.
## Building best practices
As much as possible, build from a user's perspective. Use `.within` cypress command as needed to scope a command within a specific element (e.g. table, nav).