Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update RegExp tests for \w, \W, \b & \B #705

Open
msaboff opened this issue Jun 28, 2016 · 3 comments
Open

Update RegExp tests for \w, \W, \b & \B #705

msaboff opened this issue Jun 28, 2016 · 3 comments
Labels

Comments

@msaboff
Copy link

msaboff commented Jun 28, 2016

ECMA 262 issue 525 Unify handling of RegExp CharacterClassEscapes \w and \W and Word Asserts \b and \B is now closed.

Please update and/or add tests for the changed behavior of \w, \W, \b and B. The new expected behavior includes:

    /\w/iu.test('\u017F') // true
    /\w/iu.test('\u212A') // true
    /\W/iu.test('\u017F') // false
    /\W/iu.test('\u212A') // false
    /\W/iu.test('s')      // false
    /\W/iu.test('S')      // false
    /\W/iu.test('K')      // false
    /\W/iu.test('k')      // false
    /\b/iu.test('\u017F') // true
    /\b/iu.test('\u212A') // true
    /\b/iu.test('s')      // true
    /\b/iu.test('S')      // true
    /\B/iu.test('\u017F') // false
    /\B/iu.test('\u212A') // false
    /\B/iu.test('s')      // false
    /\B/iu.test('S')      // false
    /\B/iu.test('K')      // false
    /\B/iu.test('k')      // false
@jugglinmike
Copy link
Contributor

Thanks for the report, Michael! As the author of the specification patch, you
are in a great position to implement the necessary changes in Test262. Might
you be able to help out?

@msaboff
Copy link
Author

msaboff commented Jun 28, 2016

Thanks for the report, Michael! As the author of the specification patch, you
are in a great position to implement the necessary changes in Test262. Might
you be able to help out?

I could be talked into it. It may take a week or so to get round to it.

@jugglinmike
Copy link
Contributor

Sounds good. @leobalter and I are both working on miscellaneous coverage
concerns, but we'll post here if/when we're able to work on this issue. If
you're able to find the time, don't hesitate to ask us any questions you might
have!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants