Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tasks to drop and create test database #188

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nickborromeo
Copy link
Contributor

In the CONTRIBUTING.md it says

To shorten the development loop you can:

a) run trilogy tests locally with: make test
b) run ruby binding tests with cd contrib/ruby, bundle exec rake test. It's possible to run a test single example by passing a TESTOPTS environment variable like so: TESTOPTS=-n/test_packet_size_greater_than_trilogy_max_packet_len/.

When you follow these instructions, it will fail if you do not have a test database created. This change adds tasks the following tasks:

  • db:create
  • db:drop
  • db:clean

When running the ruby binding tests, it will run the db:clean task to drop the test database first (if it exists) and creates it.

I think it will also be helpful to have a similar task in the Makefile so that make test can setup the DB if the user chooses not to use the docker approach. However, I am not sure how to do this 🤔

It might also be useful to push forward with
#170 as we can pontentially move away from Docker for the CI builds.

In the `CONTRIBUTING.md` it says

> To shorten the development loop you can:
>
> a) run trilogy tests locally with: make test
> b) run ruby binding tests with cd contrib/ruby, bundle exec rake test. It's possible to run a test single example by passing a TESTOPTS environment variable like so: TESTOPTS=-n/test_packet_size_greater_than_trilogy_max_packet_len/.

When you follow these instructions, it will fail if you do not have a
`test` database created. This change adds tasks the following tasks:

- `db:create`
- `db:drop`
- `db:clean`

When running the ruby binding tests, it will run the `db:clean` task to
drop the test database first (if it exists) and creates it.

I think it will also be helpful to have a similar task in the `Makefile`
so that `make test` can setup the DB if the user chooses not to use the
docker approach. However, I am not sure how to do this 🤔

It might also be useful to push forward with
trilogy-libraries#170 as we can
pontentially move away from Docker for the CI builds.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant