Problem/Motivation
Both ViewUnitTestBase and ViewTestBase has quite a bunch of assertIdenti* methods, this is unnecessary duplication.
Proposed resolution
Extract them into a trait, probably take the one of ViewUnitTestBase as it provides more information.
Use this new trait as part of ViewUnitTestBase and ViewTestBase
Remaining tasks
User interface changes
API changes
Beta phase evaluation
| Issue category | Task, because it just removes maintaining overhead |
|---|---|
| Issue priority | Normal because it makes normal views tests easier to debug |
| Disruption | No disruption at all |
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 2402827-8.patch | 15.54 KB | kgoel |
| #6 | interdiff.txt | 1.52 KB | kgoel |
| #6 | 2402827-6.patch | 15.53 KB | kgoel |
| #1 | 2402827-1.patch | 15.57 KB | kgoel |
Comments
Comment #1
kgoel commentedComment #3
dawehnerMeh
Comment #5
dawehnerNice, first time pass!
Mh, how can we make that fit into 80 chars? Provide some assertions to check for the expected result of a view?
What about naming it
ViewResultAssertionTraitComment #6
kgoel commentedComment #8
kgoel commentedForgot to change the name of the file when I changed trait name :((
Comment #9
dawehnerThank you!
Comment #10
heddnSmall nit.
Me thinks these doc blocks should swap. The 1st/2nd should be the 3rd and the 3rd should have the wording from the 1st/2nd. Or just take out the default text
'Identical result set.'comment entirely. It doesn't add much.Comment #11
kgoel commentedSpoke with @heddn -
Moving this back to RTBC since $message is same in docblock for assertIdenticalResultsetHelper method in ViewTestBase and ViewUnitTestBase.
Comment #12
alexpottCommitted 9a2b86b and pushed to 8.0.x. Thanks!
Thanks for adding the beta evaluation to the issue summary.