Skip to content

Schema setup script doesn't populate test db #7

Open
@bdickason

Description

The test.js file hardcodes the test db to tekkenchickentest but this db is not populated by the schema script.

Propose we either:

  1. Populate the test db alongside the main db in /database/init.js -or-
  2. Allow the user to pass in a variable to /database/init.js to override the db

The thinking here is that we're going to want to setup a CI server (ala travis CI) that runs every test when we check in the build, so we should create a programmatic way to populate the db for running tests.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions