6.8 KiB
Testing & Local Development
- License key
- Simulated hosts
- Test suite
- End-to-end tests
- Test hosts
- Database backup/restore
- Seeding Data
- MySQL shell
- Testing SSO
License key
Need to test Fleet Premium features locally?
Use the --dev_license flag to use the default development license key.
For example:
./build/fleet serve --dev --dev_license
Simulated hosts
It can be helpful to quickly populate the UI with simulated hosts when developing or testing features that require host information.
Check out the instructions in the /tools/osquery directory for starting up simulated hosts in your development environment.
Test suite
You must install the golangci-lint command to run make test[-go] or make lint[-go], using:
go install github.com/golangci/golangci-lint/cmd/golangci-lint@v1.42.0
Make sure it is available in your PATH. To execute the basic unit and integration tests, run the following from the root of the repository:
REDIS_TEST=1 MYSQL_TEST=1 make test
It is a good idea to run make test before submitting a Pull Request.
Go unit tests
To run all Go unit tests, run the following:
REDIS_TEST=1 MYSQL_TEST=1 make test-go
Go linters
To run all Go linters and static analyzers, run the following:
make lint-go
Javascript unit tests
To run all JS unit tests, run the following:
make test-js
or
yarn test
Javascript linters
To run all JS linters and static analyzers, run the following:
make lint-js
or
yarn lint
MySQL tests
To run MySQL integration tests set environment variables as follows:
MYSQL_TEST=1 make test-go
Email tests
To run email related integration tests using MailHog set environment as follows:
MAIL_TEST=1 make test-go
Network tests
A few tests require network access as they make requests to external hosts. Given that the network is unreliable, may not be available, and those hosts may also not be unavailable, those tests are skipped by default and are opt-in via the NETWORK_TEST environment variable. To run them:
NETWORK_TEST=1 make test-go
Viewing test coverage
When you run make test or make test-go from the root of the repository, test coverage reports are generated in every subpackage. For example, the server subpackage will have a coverage report generated in ./server/server.cover
To explore a test coverage report on a line-by-line basis in the browser, run the following:
# substitute ./datastore/datastore.cover, etc
go tool cover -html=./server/server.cover
To view test a test coverage report in a terminal, run the following:
# substitute ./datastore/datastore.cover, etc
go tool cover -func=./server/server.cover
End-to-end tests
E2E tests are run using Docker and Cypress.
E2E tests are constantly evolving and running them or examining CI results is the best way to understand what they cover, but at a high level they cover:
- Setup
- Login/out flows
- Host page add hosts label flows
- Queries flows
- Schedule flows scheduling packs
- Permissions Admin Observer (global and team) Maintainer
- Organizational Settings Settings adjustments Users
Preparation
Make sure dependencies are up to date and the Fleet binaries are built locally.
For Fleet Free tests:
make e2e-reset-db
make e2e-serve-free
For Fleet Premium tests:
make e2e-reset-db
make e2e-serve-premium
This will start a local Fleet server connected to the E2E database. Leave this server running for the duration of end-to-end testing.
make e2e-setup
This will initialize the E2E instance with a user.
Run tests
Tests can be run in interactive mode, or from the command line.
Interactive
For Fleet Free tests:
yarn e2e-browser:free
For Fleet Premium tests:
yarn e2e-browser:premium
Use the graphical UI controls to run and view tests.
Command line
For Fleet Free tests:
yarn e2e-cli:free
For Fleet Premium tests:
yarn e2e-cli:premium
Tests will run automatically and results are reported to the shell.
Test hosts
The Fleet repo includes tools to start test osquery hosts. Please see the documentation in /tools/osquery for more information.
Manually testing email with MailHog
To intercept sent emails while running a Fleet development environment, first, in the Fleet UI, navigate to the Organization settings page under Admin.
Then, in the "SMTP Options" section, enter any email address in the "Sender Address" field, set the "SMTP Server" to localhost on port 1025, and set "Authentication Type" to None. Note that you may use any active or inactive sender address.
Visit locahost:8025 to view Mailhog's admin interface which will display all emails sent using the simulated mail server.
Database Backup/Restore
In the course of development (particularly when crafting database migrations), it may be useful to backup and restore the MySQL database. This can be achieved with the following commands:
Backup:
./tools/backup_db/backup.sh
The database dump is stored in backup.sql.gz.
Restore:
./tools/backup_db/restore.sh
Note that a "restore" will replace the state of the development database with the state from the backup.
MySQL shell
Connect to the MySQL shell to view and interact directly with the contents of the development database.
To connect via Docker:
docker-compose exec mysql mysql -uroot -ptoor -Dfleet
Testing SSO
Fleet's docker-compose file includes a SAML identity provider (IdP) for testing SAML-based SSO locally.
Configuration
Configure SSO on the Organization Settings page with the following:
Identity Provider Name: SimpleSAML
Entity ID: https://localhost:8080
Issuer URI: http://localhost:8080/simplesaml/saml2/idp/SSOService.php
Metadata URL: http://localhost:9080/simplesaml/saml2/idp/metadata.php
The identity provider is configured with one user:
Username: sso_user
Email: sso_user@example.com
Password: user123#
Use the Fleet UI to invite one of these users with the associated email. Be sure the "Enable Single Sign On" box is checked for that user. Now after accepting the invitation, you should be able to log in as that user by clicking "Sign On with SimpleSAML" on the login page.
To add additional users, modify tools/saml/users.php and restart the simplesaml container.