mirror of
https://github.com/bitwarden/server
synced 2026-01-15 15:03:34 +00:00
f144828a87
We want to reduce the amount of business critical test data in the company. One way of doing that is to generate test data on demand prior to client side testing. Clients will request a scene to be set up with a JSON body set of options, specific to a given scene. Successful seed requests will be responded to with a mangleMap which maps magic strings present in the request to the mangled, non-colliding versions inserted into the database. This way, the server is solely responsible for understanding uniqueness requirements in the database. scenes also are able to return custom data, depending on the scene. For example, user creation would benefit from a return value of the userId for further test setup on the client side. Clients will indicate they are running tests by including a unique header, x-play-id which specifies a unique testing context. The server uses this PlayId as the seed for any mangling that occurs. This allows the client to decide it will reuse a given PlayId if the test context builds on top of previously executed tests. When a given context is no longer needed, the API user will delete all test data associated with the PlayId by calling a delete endpoint. --------- Co-authored-by: Matt Gibson <mgibson@bitwarden.com>
Bitwarden Database Seeder
A class library for generating and inserting test data.
Project Structure
The project is organized into these main components:
Factories
Factories are helper classes for creating domain entities and populating them with realistic data. This assist in decreasing the amount of boilerplate code needed to create test data in recipes.
Recipes
Recipes are pre-defined data sets which can be run to generate and load data into the database. They often allow a allow for a few arguments to customize the data slightly. Recipes should be kept simple and focused on a single task. Default to creating more recipes rather than adding complexity to existing ones.