* Get auditing.cy.spec to pass

* Skip custom drill through tests until we replace them

* A few updates to the whitelabel test case:
- Move custom colors into constant variable to reference throughout
- remove some 'it' blocks we didn't need to speed up tests
- Remove a few 'wait's
- Restructure tests to be a bit more in line with best practices

* Update the snippet permissions test:
- Create test for just creating snippet as admin
- Create test for inability to create snippet as user by default
- Quarantine the user snippet creation test

* Rename sandboxes

* Replace legacy ENABLE_ENTERPRISE_EDITION env variable with MB_EDITION

* Add MB_EDITION env variable to Cypress test run

* Adds Cypress tests for saved/unsaved questions and date/time formatting.

Co-authored-by: Nemanja <31325167+nemanjaglumac@users.noreply.github.com>
Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

* https://docs.cypress.io/guides/references/configuration.html#Videos

- Adds helpful log message to various helper functions in `frontend/test/__support__/cypress.js`.
    - `--- Logging in as ${user} ---` to `signIn()`
    - `--- Signing out ---` to `signOut()` and
    - `--- Restore Data Set ---` to `restore()`

* Add `read-excel-file` library

* Add "file download" config to `cypress-plugins.js`

* Switch to SheetJS for xlsx/csv testing and upgrade Cypress because of https://github.com/cypress-io/cypress/pull/7382




Co-authored-by: Damon P. Cortesi <d.lifehacker@gmail.com>

I'm going over this today in an onboarding tech dive and I'm apparently more OCD than I thought.

* Fix env variable name to reflect one actually used in Docker image

* actually fix the var name

* Upgrade Cypress to v5.5.0

* Needed to unset the `DISPLAY` ENV through `config.yml` to finally make this work! (Reference: https://github.com/cypress-io/cypress/issues/4034#issuecomment-486773042)

This makes the dependencies reproducible in the CI run, making it less
susceptible to external disturbances (e.g. https://yarnpkg.com/ being
unreachble) since there is just-in-time version resolution anymore and
likely all the necessary packages are available in the build cache.

1 am PST = 09:00 UTC

CircleCI cron is for UTC:
https://circleci.com/docs/2.0/workflows/#scheduling-a-workflow

* Fix `metrics.cy.spec.js` flakes (#13682)

* Refactor the test using API

* Fix flakes in `revisions screen` block

* Improve test assertions (there were some rendering problems, so I adjusted the assertions)

- isolated flake (`it.only("should surface an error when validation for any field fails (metabase#4506)", () => {...})`) passed 10x (https://github.com/nemanjaglumac/metabase-tests/actions/runs/348275781)
- the whole spec passed 20x (https://github.com/nemanjaglumac/metabase-tests/actions/runs/348306177)

Smoketest for OSS edition (for now)

* Add a circleci nightly workflow that runs a bigger set of Cypress smoketests

* Run this every hour while we're testing it, add a small fix to the admin test

* Smoketests: Skip some known failing tests

Co-authored-by: Ariya Hidayat <ariya@metabase.com>

* If scheduled analyze task is short, refingerprint tables

- make the sync steps return their values rather than log and nil
- dynamic var in fingerprint.clj to swap out query clauses for fields
- update the fingerprint runner to not consume whole list when
    refingerprinting
- algorith for fields to refingerprint: shuffle table and do up to
    1000 fields
- we refingerprint after analyzing in the task if two conditions hold:
   1. the analysis lasted under 5 minutes
      Don't want to hog our CPU or connections
   2. no fields were fingerprinted.
      The first analysis will fingerprint everything and analyze
      fields base on that. Seems subsequently we almost never
      fingerprint unless its a new field.

TODO for the future to make it better:
- manual overrides to prevent these refingerprinting (might be
necessary before this goes live. I lean towards actually doing this
and making it opt IN so that people can enable. We verify that its
working frequently enough to be helpful but not causing problems. Then
in 38 or 39 we flip it and make it opt OUT)
- better strategies for what to refingerprint. Right now just picks
tables at random. We don't have a place to write down frequency of use
of tables nor if the fingerprints are changing substantially (for some
notion of substantial). Also, only date and number fingerprints are
used by the app at the moment. Could just bias to these fields for the
moment.
- Our analysis doesn't override if there's already a special_type (Or
other field things). We don't capture if special_type and other
aspects of a field are manually computed (and therefore a candidate to
use ongoing fingerprint results (state fields based on percentage of
state values, etc). If this becomes the case and our analysis can
become more mature to improving insights and knowing its not
clobbering a human override/input we could just make the initial
fingerprint smarter.

As it stands this step is after the normal fingerprinting so that we
don't accidentally do too much work and because we can't really use
the information in the analysis/classify steps yet.

Docstrings for linter

* Add refingerprint column to Database

its nullable now so that people can opt in and we can migrate to opt
out in the future with the following strategy:  if null, set to True,
set default to True. This allows us to respect people who have turned
it off and enabling in a future release when we are sure the
performance ramifications are not too severe.

* Add tests for refingerprinting

* Test for refingerprinting being bounded

* Update UI verbiage for refingerprinting

* fix ProgressBar component

* [styleguide] - add some simple stats

* update ProgressBar snap

* cleanup

* Add repro for #12928 [ci skip]
(Cannot join Saved Questions that themselves contains joins)

* Quarantine flaky tests (#13682)

* Add TODO note re: `describeWithToken`

Co-authored-by: Nemanja Glumac 

Merge release-x.37.x 11/04/2020

* Add repro for #13626 [ci skip]

Note: Once this issue is fixed, add a positive assertion to the Cypress test.

* upgrade some deps to fix warnings

* add back lint-yaml scrip

* remove e2e/karma references

* Add repro for #13235 [ci skip]
(Cannot filter by selecting remapped display value from dropdown list)

* Fix Cypress flake `should allow bulk hiding tables`

* Fix Cypress flake `should save a setting` in `settings/settings.cy.spec.js`

* Quarantine `view embedded questions` test(s) in `public.cy.spec.js`