A simple scenario from today:A developer gets a user story to display nice, layout constant, user-friendly error pages in case of an exception.Developers want to have detailed pages on dev (local machines) environment and same behavior on staging (to trace bugs). While test case needs to validate the new look of error page :) There's no other good place to test that than on staging :) Looks like a paradox to me :) What do we do with that?Edit: I've been asked to elaborate.Developers prefer detailed error pages with stack trace. Product owner wants to have nice error page without exception details. It is best for product owner not to even mention the word error on that page. They want custom error pages. Plus yes, we don't have separate QA environment and staging. It is because we have to ask IT Web team to create all of them, and DBA (not very friendly guys ;) ) to create databases and we have multiple small micro services.
How do you test environment dependent features?
testing