Skip to content
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

Open
dbarnett opened this issue Aug 23, 2019 · 5 comments
Open

What's the recommended way to run the tests? #5

dbarnett opened this issue Aug 23, 2019 · 5 comments
Labels
question Further information is requested

Comments

@dbarnett
Copy link
Contributor

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.

@dbarnett dbarnett added the question Further information is requested label Aug 23, 2019
@ranmocy
Copy link
Owner

ranmocy commented Aug 23, 2019

I don't have integration test with all mocks of APIs, through I believe it's possible.
I only do some critical unit test with a simple method in index.ts

@dbarnett
Copy link
Contributor Author

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?

@ranmocy
Copy link
Owner

ranmocy commented Aug 28, 2019

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.

@dbarnett
Copy link
Contributor Author

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?

@dbarnett
Copy link
Contributor Author

You can patch #12 locally to get tests running for now if we decide not to merge the workaround changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants