Tracking ECMAScript Proposals
-
Updated
Jul 20, 2021
{{ message }}
Tracking ECMAScript Proposals
Make it a fun to create spec for developers and teammates
Human-optimized error messages for clojure.spec
Complete instrumentation for clojure.spec
Hassle-free inline clojure.spec with semi-automatic generative testing and side effect detection
The Filecoin protocol specification
Clojure(Script) library for phrasing spec problems.
Real time console spec reporter for jasmine testing framework
A small Ruby Gem to run RSpec and Serverspec, Infrataster and Capybara tests against Dockerfiles or Docker images easily.
Pinpointer is yet another clojure.spec error reporter based on a precise error analysis
Notion Abstract Syntax Tree specification.
ECMAScript spec abstract operations.
Related to icy-arctic-fox/spectator#19 but expanded to support passing a line number within the grouping of a spec. If the line number matches a context block, every spec within that context should be run. The same goes for the describe block. If the line number falls on a specific spec then that should be run specifically, still.
Add a description, image, and links to the spec topic page so that developers can more easily learn about it.
To associate your repository with the spec topic, visit your repo's landing page and select "manage topics."
The command exist test always returns true regardless of if the command is invalid.
Describe the problem
On Windows, we want to test if a command/cmdlet exists before running it. However, the 'command().exist?‘ test always returns true no matter what command t