dbfixtures

Venom - Executor Database Fixtures

Step to load fixtures into MySQL and PostgreSQL databases.

It uses the package testfixtures/v3 under the hood: https://github.com/go-testfixtures/testfixtures Please read its documentation for further details about the parameters of this executor, especially folder and files, and how you should write the fixtures.

Input

In your yaml file, you declare your step like this

  - database mandatory [mysql/postgres/sqlite3]
  - dsn mandatory
  - schemas optional
  - migrations optional
  - migrationsTable optional
  - skipResetSequences optional
  - files optional
  - folder optional

• schemas is a list of paths to several .sql file that contains the schemas of the tables in your database. If specified, the content of every file will be executed before loading the fixtures.
• files parameter is only used as a fallback if folder is not used.
• migrations is a folder path that contains SQL migrations files that can be used to initialize the database, instead of a list of schemas. Note that if schemas is not empty, it will have precedence and migrations files will be ignored.
• migrationsTable is the table used to store the migration version.
• skipResetSequences is only used for PostgreSQL database, it control whether index should be reset (default) or not

Example usage (mysql):

name: Title of TestSuite
testcases:

  - name: Load database fixtures
    steps:
      - type: dbfixtures
        database: mysql
        dsn: user:password@(localhost:3306)/venom?multiStatements=true
        schemas:
          - schemas/mysql.sql
        folder: fixtures
        files:
          - fixtures/table.yml

note: in the example above, the query param multiStatements=true is mandatory if we want to be able to load the schema.

SQL drivers

This executor uses the following SQL drivers:

• MySQL: https://github.com/go-sql-driver/mysql
• PostgreSQL: https://github.com/lib/pq