7e9446ea07
fix copyright date Add more user tests More user tests More user tests Start refactoring user tests Docs Fix lint Fix db fixtures init in tests Fix models test Fix loading fixtures Fix ineffasign Fix lint Fix integration tests Fix init of test engine creation Fix user related tests Better handling of creating test enging Moved all fixtures to db package Moved all fixtures to db package Moved user related stuff to seperate package Co-authored-by: kolaente <k@knt.li> Reviewed-on: https://kolaente.dev/vikunja/api/pulls/123
2 KiB
| date | title | draft | type | menu | ||||
|---|---|---|---|---|---|---|---|---|
| 2019-02-12:00:00+02:00 | Testing | false | doc |
|
Testing
You can run unit tests with [our Makefile]({{< ref "make.md">}}) with
{{< highlight bash >}} make test {{< /highlight >}}
Running tests with config
You can run tests with all available config variables if you want, enabeling you to run tests for a lot of scenarios.
To use the normal config set the enviroment variable VIKUNJA_TESTS_USE_CONFIG=1.
Show sql queries
When UNIT_TESTS_VERBOSE=1 is set, all sql queries will be shown when tests are run.
Fixtures
All tests are run against a set of db fixtures.
These fixtures are defined in pkg/models/fixtures in YAML-Files which represent the database structure.
When you add a new test case which requires new database entries to test against, update these files.
Integration tests
All integration tests live in pkg/integrations.
You can run them by executing make integration-test.
The integration tests use the same config and fixtures as the unit tests and therefor have the same options available, see at the beginning of this document.
To run integration tests, use make integration-test.
Initializing db fixtures when writing tests
All db fixtures for all tests live in the pkg/db/fixtures/ folder as yaml files.
Each file has the same name as the table the fixtures are for.
You should put new fixtures in this folder.
When initializing db fixtures, you are responsible for defining which tables your package needs in your test init function.
Usually, this is done as follows (this code snippet is taken from the user package):
err = db.InitTestFixtures("users")
if err != nil {
log.Fatal(err)
}
In your actual tests, you then load the fixtures into the in-memory db like so:
db.LoadAndAssertFixtures(t)
This will load all fixtures you defined in your test init method. You should always use this method to load fixtures, the only exception is when your package tests require extra test fixtures other than db fixtures (like files).