"The value of any practice depends on its context" N-wise testing is a technique, not a silver bullet to solve any problem. It's your responsibility as a professional to analyze how to best approach a specific problem. Take the example of a pairwise analysis: valid name, valid password valid name, invalid password invalid name, valid password ...


Some issues you will run into are: co-ordination of who tests what determining who tests what parts of security determining the feedback mechanisms for each changes in one area that affect the other co-coordinating validations standards for where validation is done (can be both) Essentially the issues are mostly about Communication and co-ordination


combining API and UI Since a user story describes a feature and features could consist of UI and API changes, I guess this is pretty natural and happens all the time on different teams. API and UI implementations and validation Validations are something that usually have to be implemented, both on frontend (html, JS) and again on backend because we can't ...

Only top voted, non community-wiki answers of a minimum length are eligible