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

clean up the command structure for dbt test #109

Closed
jthandy opened this issue Aug 16, 2016 · 1 comment
Closed

clean up the command structure for dbt test #109

jthandy opened this issue Aug 16, 2016 · 1 comment
Assignees
Milestone

Comments

@jthandy
Copy link
Member

jthandy commented Aug 16, 2016

few concerns:

  • the more common thing to do will actually be to run dbt test --validate rather than dbt test. it's strange that the more common use case is the one where you need to supply a flag.
  • "test" vs "validate" as verbs don't have super-clear meanings. we should think for a bit here about what we want these terms to be prior to really launching testing and building docs around this stuff.
  • when i use dbt test --validate i would really prefer that it not do the part where it builds the "limit 0" temporary tables. i would imagine running this validation once a day or even multiple times a day, on already-working dbt models. there is no need to build these test models in this environment because we're actually validating the real dbt models.
@drewbanin drewbanin added this to the 0.4.1 milestone Aug 20, 2016
@drewbanin drewbanin self-assigned this Aug 20, 2016
@drewbanin
Copy link
Contributor

i rolled this out as a part of 0.4.1

# run models
dbt run
# create "limit 0" views and delete them afterwards. model names are prefixed with "test_"
dbt run --dry
# run schema validations from schema.yml files
dbt test 

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

No branches or pull requests

2 participants