search

NoriSte / ui-testing-best-practices

The largest UI testing best practices list (last update: March 2023)
Creative Commons Attribution Share Alike 4.0 International
1.67k stars 153 forks source link

Add the "Decouple the back-end and front-end test through Contract Testing" chapter #40

Closed NoriSte closed 1 year ago

NoriSte commented 1 year ago

Bring @NoriSte's article to the repo.

NoriSte commented 1 year ago

I don't fully get the layman's takeaway from this article.

At a high level, this sounds like we are running some e2e tests, they are recroding fixtures (which in this context are called contracts), and future tests are made into UI-integration tests. Is this correct?

E2e recording to fixutres is a decent idea. Where can someone not in Hasura find out more about doing something similar?

How about alternatives? Why doesn't the company use API e2e tests, instead of UI e2e, or UI integration?

Have you considered Pact? What did you find out, why isn't it a good fit?

I kind of wish to see this kind of analysis at the end, and recommendation for a layman to take some ideas away. Otherwise it's a good story, but does not help the reader as much as I wish it did.

I agree, let me close this PR and come back on this topic in the future with more examples and suggestions, if any 😊