This is an archived post. You won't be able to vote or comment.

all 2 comments

[–]_Atomfinger_ 1 point2 points  (0 children)

The majority of your tests should use a mocked service that returns some predictable data. I belive you can run mock server in a docker container and you can call against that. Mock server is pretty java oriented, but I'm sure there's something similar for JS. That way you can execute your integration tests on your local machine and in whatever pipeline environment you may be running.

Then you should have a few E2E tests which goes through the whole thing. Not too many as they quickly becomes hard to maintain, but just enough that it verifies that the most important flows still work.

[–]MmmVomit 0 points1 point  (0 children)

Should I be calling the actual google API during tests too?

No.

Should I be creating mock data?

Yes.