We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Due to #521, we can't use our regular build chain with this, so we're having trouble with integrating code that uses this into our test suite.
Can you suggest a way for us to set up our karma.conf so that Box.Preview is available at test time?
karma.conf
Box.Preview
Preferably without having to re-fetch preview.js from the network with every test run.
Or is there a mock implementation of Box.Preview we should load instead?
The text was updated successfully, but these errors were encountered:
@keturn I see this was posted some time ago and never received a response. Did you ever figure out a solution?
Sorry, something went wrong.
Couldn't say; I'm no longer working with that project.
No branches or pull requests
Due to #521, we can't use our regular build chain with this, so we're having trouble with integrating code that uses this into our test suite.
Can you suggest a way for us to set up our
karma.conf
so thatBox.Preview
is available at test time?Preferably without having to re-fetch preview.js from the network with every test run.
Or is there a mock implementation of Box.Preview we should load instead?
The text was updated successfully, but these errors were encountered: