3 ms·

FE contractor here with hundreds of hours writing selenium & cypress tests. The main issue is not automating the browser, the main issue is getting the data acc

FE contractor here with hundreds of hours writing selenium & cypress tests. The main issue is not automating the browser, the main issue is getting the data access & service mocks right. I hardly ever had an application that could be testet against a dev/prod DB - you will always need to setup special test cases with a certain dataset for a particular case - especially for those nasty corner cases for which you write your tests for. I've worked in projects where we created special testing REST endpoints to load/unload scenarios into the DB, and also on other projects using browser mocks. In both cases, this is the work that requires the most amount of time.

gvkhna 6y ago
Thanks for your feedback! For broad testing we definitely understand there has to be some time spent setting up good testing environments. Running a staging environment suited to being tested to catch regressions is usually not quick. But it can be effective to run the same tests across one type of environment, such as staging tests against a staging environment. This will catch many regressions, and with more work setting up good scenarios cover large parts of an application. Do you find any value in making it easier to do testing?