From c2e818dce5495bcbdcd984bfde0effe1bd0911ca Mon Sep 17 00:00:00 2001 From: DavidCai Date: Sun, 19 Feb 2017 16:34:57 +0800 Subject: [PATCH] doc: restrict the ES.Next features usage in tests PR-URL: https://github.com/nodejs/node/pull/11452 Refs: https://github.com/nodejs/node/pull/11290 Reviewed-By: Joyee Cheung Reviewed-By: Luigi Pinca Reviewed-By: James M Snell --- doc/guides/writing-tests.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/guides/writing-tests.md b/doc/guides/writing-tests.md index 36cf04fc546825..4f226bfdb2580c 100644 --- a/doc/guides/writing-tests.md +++ b/doc/guides/writing-tests.md @@ -231,8 +231,12 @@ assert.throws( For performance considerations, we only use a selected subset of ES.Next features in JavaScript code in the `lib` directory. However, when writing -tests, it is encouraged to use ES.Next features that have already landed -in the ECMAScript specification. For example: +tests, for the ease of backporting, it is encouraged to use those ES.Next +features that can be used directly without a flag in [all maintained branches] +(https://github.com/nodejs/lts), you can check [node.green](http://node.green) +for all available features in each release. + +For example: * `let` and `const` over `var` * Template literals over string concatenation