You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my push to get 100% code coverage, I introduced some unwieldy tests, especially in the pages folder.
There are a lot of table-driven tests in here where the tables are made up of large (many column) tuples with no naming or documentation to know what each column represents. You have to look at the test and try to infer it which is error-prone.
A better way to do this would be to use namedtuples, and update the references in the tests from their index to their column name instead.
The text was updated successfully, but these errors were encountered:
In my push to get 100% code coverage, I introduced some unwieldy tests, especially in the
pages
folder.There are a lot of table-driven tests in here where the tables are made up of large (many column) tuples with no naming or documentation to know what each column represents. You have to look at the test and try to infer it which is error-prone.
A better way to do this would be to use namedtuples, and update the references in the tests from their index to their column name instead.
The text was updated successfully, but these errors were encountered: