From 037b2025a65411464bd5dd976d9f5a0e93b215dc Mon Sep 17 00:00:00 2001 From: Vincent Chan Date: Sat, 18 Nov 2017 19:57:58 +0800 Subject: [PATCH] description about building and testing babylon in CONTRIBUTING.md (#6756) developers maybe confuse about the steps of building and testings in the mono project --- CONTRIBUTING.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ffab4ff491..bf40809c8f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -231,6 +231,18 @@ descriptive name, and add the following: * Add an `expected.json` file with the expected parser output. For added convenience, if there is no `expected.json` present, the test runner will generate one for you. +After writing tests for babylon, just build it by running: + +```sh +$ make build-babylon +``` + +Then, to run the tests, use: + +```sh +$ TEST_ONLY=babylon make test-only +``` + #### Bootstrapping expected output For both `@babel/plugin-x` and `babylon`, you can easily generate an `expected.js`/`expected.json` automatically by just providing `actual.js` and running the tests as you usually would.