Any good rules of thumb for designing E2E tests that validate the components can all talk to each other without duplicating business logic tests (that are better handled in unit tests where all the inputs can be controlled)?
Any recommendations for a creating an email distribution list for a club with 25 members? Would be nice if there was was one email address we could all send to that included all of us.
