test262

Commit Graph

Author	SHA1	Message	Date
Richard Gibson	38f3545344	Fix test:diff npm scripts (#2225 ) * Include untracked files in `npm run diff` * Suppress non-file output from nested `npm run diff`	2019-07-08 15:32:35 -04:00
Leo Balter	cc83d1d3de	Use .. for git diffs in the npm scripts This will allow the script to fetch only changed files from the working branch/PR	2019-05-01 15:25:29 -04:00
Leo Balter	7a21a1bd5e	fixup! set npm scripts to run tests	2019-05-01 15:25:29 -04:00
Leo Balter	1273d6e5c8	set npm scripts to run tests	2019-05-01 15:25:29 -04:00
Leo Balter	705d78299c	Update dependencies in package.json (#2138 )	2019-04-24 17:26:45 -04:00
Rick Waldron	5bd2e28406	4.0.0 (#2132 ) The latest changes to INTERPRETING.md require a incrementing the major version.	2019-04-24 11:48:29 -04:00
Leo Balter	ebbe13e2b5	Add CircleCI (#2106 ) Transfer Travis jobs to CircleCI	2019-03-20 21:04:41 -04:00
Leo Balter	d534df2b12	Use travis ci to run new or modified test files on engines	2018-11-07 10:03:00 -05:00
Rick Waldron	8dbeb27b59	v3.0.0	2018-05-03 13:28:46 -04:00
Mike Pennisi	fad683d14b	Increment major version Recent changes to the metadata for negative tests fundamentally alter the way those tests are intended to be interpreted. Increment the project's version number in order to signal this to project consumers.	2018-01-05 15:17:51 -05:00
jugglinmike	a7f5616713	Introduce version number (#1255 ) Changes to the instructions for interpreting tests will likely produce new failures for consumers who are updating between revisions of Test262. Introduce a machine-readable convention for signaling substantive changes.	2017-10-02 11:12:14 -04:00

11 Commits