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

Literal extensions - RegExp #22

Closed
2 tasks done
jugglinmike opened this issue May 21, 2015 · 2 comments
Closed
2 tasks done

Literal extensions - RegExp #22

jugglinmike opened this issue May 21, 2015 · 2 comments
Assignees
Milestone

Comments

@jugglinmike
Copy link
Member

Flags:

  • "y"
  • "u"

(literal and via RegExp)

@jugglinmike jugglinmike added this to the SOW2 milestone May 21, 2015
jugglinmike added a commit that referenced this issue May 25, 2015
Since the introduction of `assert.throws` in gh-22, the preferred means
of expressing expectations regarding errors has changed. Update the
CONTRIBUTING.md file to reflect the latest approach.
jugglinmike added a commit that referenced this issue May 26, 2015
Since the introduction of `assert.throws` in gh-22, the preferred means
of expressing expectations regarding errors has changed. Update the
CONTRIBUTING.md file to reflect the latest approach.
jugglinmike added a commit that referenced this issue May 27, 2015
Since the introduction of `assert.throws` in gh-22, the preferred means
of expressing expectations regarding errors has changed. Update the
CONTRIBUTING.md file to reflect the latest approach.
jugglinmike added a commit that referenced this issue Jun 3, 2015
- Remove trailing white space
- Streamline documentation of test tags
- Do not reference obsolete tags
- Document `features` frontmatter tag
- Document `es6id` frontmatter tag
- Omit unnecessary detail about test262 website generation. This is not
  directly useful to potential test contributors. Implementation details
  like these can be taken for granted by that audience.
- Remove documentation on YAML syntax. Details on YAML may be helpful
  for some new contributors, but this document should not attempt to
  cover the topic (especially not from the description of a specific
  frontmatter entry). Replace with a link to a more comprehensive source
  as this will be more generally useful to those who need it (and less
  obtrusive for those who do not).
- Consolidate information on test helpers
- Document `assert` helpers
- Update instructions for asserting errors. Since the introduction of
  `assert.throws` in gh-22, the preferred means of expressing
  expectations regarding errors has changed. Update the CONTRIBUTING.md
  file to reflect the latest approach. Explain purpose of `throw
  NotEarlyError;` in example test.
- Re-order information on file names. The inconsistency in the project's
  file names should not go unmentioned, but neither should it not
  preceed instructions for the accepted approach to namine tests.
- More clearly document required frontmatter tags. Explicitly list
  `description` as a required frontmatter tag, implicitly identifying
  all other tags as optional.
@jugglinmike jugglinmike self-assigned this Jul 2, 2015
@jugglinmike
Copy link
Member Author

Test coverage for y flag merged via tc39#354

@jugglinmike
Copy link
Member Author

Test coverage for u flag merged via tc39#352

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

No branches or pull requests

1 participant