You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of the rate at which testing frameworks are being developed and the increasing maturity of webpack and babel, we are going to need to integrate a robust CI process that actually pulls a current quasar repo image and attempts to build each of the test runners in isolation and then run at least superficial tests to make sure that nothing is broken. This should be automatic on new point releases to quasar-cli (perhaps with a webhook) and mandatory for the introduction of new test-runners to the pantheon.
The text was updated successfully, but these errors were encountered:
Because of the rate at which testing frameworks are being developed and the increasing maturity of webpack and babel, we are going to need to integrate a robust CI process that actually pulls a current quasar repo image and attempts to build each of the test runners in isolation and then run at least superficial tests to make sure that nothing is broken. This should be automatic on new point releases to quasar-cli (perhaps with a webhook) and mandatory for the introduction of new test-runners to the pantheon.
The text was updated successfully, but these errors were encountered: