Tag Info

New answers tagged

0

Automated User Interface Testing solves the ability to: rapidly repeat testing of a large number of components remember to test a large number of functions each time compare runs and run times of test suites as the application grows set up runs with hundreds of different inputs and variable conditions enable people who did not write the test to run it and ...


0

As you pointed out, often the specifics of what constitutes invalid request parameters is different enough for each view, and so including this type of code in each view is (I think) fine and not a DRY violation. It also self-documents the view by having code at the beginning that clarifies what the view expects to receive, either in the URL, GET, or POST, ...



Top 50 recent answers are included