Standardize buckaroo integration testing #605
Description
Checks
- I have checked that this enhancement has not already been requested
How would you categorize this request. You can select multiple if not sure
Developer ergonomics (defaults, error messages)
Enhancement Description
I think each bucakroo integration target (and many of the unit tests) use adhoc dataframes written in line in the testcases. In many cases I think this is the right approach, I want the dataframe to be tailored to trigger a specific condition in buckaroo. These tests aren't parameterized and I don't want them to be.
At the same time, there are many tests I do want parameterized, just iterate over the DDD (and possibly make a TDDD Testing DDD with extra testing cases). Further, the same can be done for the integration tests, look at all the dataframes we use across all of the integration tests, consolidate them. a simple dataframe that works as a smoke test is great for integration and should fail fast (cancelling the rest of the test) - if that simple dataframe doesn't give you DOM elements none of the others will either. Then look at the rest of the DDD library.
this issue is related: #604
Pseudo Code Implementation
No response
Prior Art
n/a