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

[7.0] Run Babel's unittests in a custom sandbox (take 2). #5263

Merged
merged 2 commits into from Feb 4, 2017

Conversation

loganfsmyth
Copy link
Member

Take 2 for #5135. I simplified the code a little, and now I'm submitting it to 7.0 branch since is was too difficult to get this to work Babel 6 for both modern Node 6 and 0.10.

@mention-bot
Copy link

@loganfsmyth, thanks for your PR! By analyzing the history of the files in this pull request, we identified @hzoo, @zertosh and @motiz88 to be potential reviewers.

@hzoo hzoo added the PR: Internal 🏠 A type of pull request used for our changelog categories label Feb 3, 2017
@codecov-io
Copy link

codecov-io commented Feb 3, 2017

Codecov Report

Merging #5263 into 7.0 will increase coverage by 0.02%.

@@            Coverage Diff             @@
##              7.0    #5263      +/-   ##
==========================================
+ Coverage   89.61%   89.63%   +0.02%     
==========================================
  Files         200      200              
  Lines        9752     9772      +20     
  Branches     2596     2601       +5     
==========================================
+ Hits         8739     8759      +20     
  Misses       1013     1013
Impacted Files Coverage Δ
...-helper-transform-fixture-test-runner/src/index.js 91.5% <100%> (+1.97%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ba0df23...f4d7eb3. Read the comment docs.

@hzoo
Copy link
Member

hzoo commented Feb 3, 2017

Doesn't look slower at all without node 0.10/0.12

Can you do that simple test that adding something to the global scope in the source doesn't affect the test? (so we can prevent the error that caused us to want this PR in the first place?) basically that we used a polyfill when it wouldn't be supported otherwise

@loganfsmyth
Copy link
Member Author

@hzoo Added a test, is that what you had in mind? It just tests that things run in independent environments, since it seems like explicitly testing for something standard might be tough to get consistent across node versions?

@loganfsmyth loganfsmyth merged commit 6fa6f59 into babel:7.0 Feb 4, 2017
@loganfsmyth loganfsmyth deleted the sandbox-tests branch February 4, 2017 21:31
hulkish added a commit to hulkish/babel that referenced this pull request May 2, 2017
* 7.0: (37 commits)
  resolved conflicts
  [7.0] Switch decorators-legacy to decorators in the Stage 1 Preset (babel#5318) (babel#5319)
  [7.0] Replacing current decorators with decorators-legacy (babel#5290)
  Add Node 7 to CI (babel#5165)
  [7.0] remove standalone babel package (babel#5293)
  .gitignore for test [skip ci]
  update yarn
  use lerna@2-beta.37 (babel#5254)
  [7.0] Run Babel's unittests in a custom sandbox (take 2). (babel#5263)
  [7.0] Remove quotes option (babel#5154)
  [7.0] List babylon plugins instead of * in babel-generator tests (babel#5231)
  Remove babel-runtime from packages' dependencies (babel#5218)
  Bump `detect-indent`. (babel#5226)
  [7.0] Add legacy-decorators to stage-1. Fixes babel#5220 (babel#5225)
  [7.0] Use lerna's --independent mode + changes (fixes babel#5221)
  [7.0] Bump `home-or-tmp` for `babel-register`. (babel#5189)
  [7.0] Added yarn.lock (babel#5175)
  [7.0] Remove old babel-runtime code (babel#5187)
  [7.0] Drop support for Node 5 (babel#5186)
  Remove path-is-absolute in favor of builtin path.isAbsolute (babel#5179)
  ...
@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Oct 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Internal 🏠 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants