-
Notifications
You must be signed in to change notification settings - Fork 18
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
What's the recommended way to run the tests? #5
Comments
I don't have integration test with all mocks of APIs, through I believe it's possible. |
If I were going to set up nice testing, do you have any preferred strategy or framework in mind that I could start setting up? |
For testing strategy, just using your common sense. For framework, I don't have strong preference here. But I use Jest a lot and seems like the most popular one in JS word. |
For me testAll fails with various errors about missing ES6 features if not using the V8 engine but I have different problems preventing me from using V8: Script Editor's "Run > testAll" says it only works with runtimeVersion: DEPRECATED_ES5 and the menu options don't show up at all in the spreadsheet so I can't trigger it from the menus either (apparently due to https://stackoverflow.com/a/55580374/307705). Have you run into these issues? |
You can patch #12 locally to get tests running for now if we decide not to merge the workaround changes. |
How do you run the tests? In particular, I'm looking for a way to quickly run the tests from the command line as I'm making changes.
The text was updated successfully, but these errors were encountered: