I've started to create a few cypress tests and want to get some eyes on it and get the code out so that others can add tests if they'd like. I haven't added it to tox yet but I've run through the steps we'd need to take to run it from the cli.
The general structure for tests that I've included is: **Explore** - Controls - setting controls in the UI and confirm that they are getting applied correctly - Links - test all links on explore pages - Visualizations - test functionality for different chart types, use form_data to test various combinations of control values and validate that the data is displaying correctly for the viz type. **Dashboard** - testing dashboard loading and editing ability The difference between control tests and visualization tests seems really minor, but I think it would be useful in thinking about testing in isolation. Removing/setting controls for a single viz type, as well as, validating complex controls like metrics and filters would be useful to separate from testing the parameters for each visualization types. Let me know if anyone has thoughts on this! I needed to add `load_test_users` as a cli command so we can run it in backend and frontend tests. I'd want to check that we are in test mode before creating admin users, but it doesn't seem like there's an easy flag to test for test mode. Anyone know of a way to check this? I can add something if not. [ Full content available at: https://github.com/apache/incubator-superset/pull/5693 ] This message was relayed via gitbox.apache.org for [email protected]
