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
I noticed some "pain" around this subject for a good amount of people so decided to propose to allow regex patterns for @expectedExceptionMessage.
This feature could keep test suites dryer when dealing with fuzzy exception messages while keeping consistency when test annotations are preferred. Ex:
/** * @expectedException ParserException * @expectedExceptionMessage /Cannot use \w+ as type \w+ (on line \d+)/ * @dataProvider typeErrorProvider */publicfunction testTypeError()
{ ...
Some dynamic exception messages that would pass the example test:
Cannot use 2 as type float (on line 2)
Cannot use sebastian as type integer (on line 14)
The text was updated successfully, but these errors were encountered:
I noticed some "pain" around this subject for a good amount of people so decided to propose to allow regex patterns for @expectedExceptionMessage.
This feature could keep test suites dryer when dealing with fuzzy exception messages while keeping consistency when test annotations are preferred. Ex:
Some dynamic exception messages that would pass the example test:
The text was updated successfully, but these errors were encountered: