From the command line, you can run the following validators as subcommands (e.g. spectacles sql):

✅ SQL validation - tests the sql field of each dimension for database errors

✅ Assert validation - runs Looker data tests

✅ Content validation - tests for errors in Looks and Dashboards

✅ LookML validation - runs LookML validator

Documentation

You can find detailed documentation for the CLI and web app on our docs page: docs.spectacles.dev.

Why we built this

Occasionally, when we make changes to LookML or our data warehouse, we break downstream experiences in Looker:

• Changing the name of a database column without changing the corresponding sql field in our Looker view, leaving our users with a database error when using that field
• Adding an invalid join to an explore that fans out our data, inflating a key metric that drives our business without realising
• Editing LookML without remembering to check the Content Validator for errors, disrupting Dashboards and Looks that our users rely on
• Giving a new dimension a confusing name, causing other developers in our team to spend extra time trying to figure out how it should be used