Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We need automated tests for 7.x-2.x. Any refactoring that needs to happen to support this is very much appreciated. Use UnitTests where possible (rather than web tests). This will make the test suite run faster.
Comments
Comment #1
cdale CreditAttribution: cdale commentedShort summary of what I believe is in the 2.x branch that might need testing.
Comment #2
cweagansSounds like a pretty accurate list. I'd also throw in that we need tests for any bugs that get fixed.
Comment #3
cdale CreditAttribution: cdale commented@cweagans Reckon you could chime in on #1928688: Coding details in the 7.x-2.x branch? Wouldn't mind your input.
Comment #4
cdale CreditAttribution: cdale commentedWhat kind of tests are we actually wanting to see here? Testing the API integration works? Or is this where we would test the libphonenumber/phony code?
I'm at a bit of a loss as to what should actually be tested or have tests written for it.
Comment #5
cweagansThe libphonenumber/phony code should be tested with PHPunit separately from Drupal, IMO. This would be about testing the integration, the field, etc. A few web tests to ensure that validation, storage, parsing, etc works, maybe one to make sure that the output is what is expected..
Also, we don't have to write all of these at once. We can do this incrementally. I'd just like to have good test coverage for this module (test anything that makes sense to test) so that we don't get weird bugs in the future.