-
Updated
Jul 20, 2021
#
spec
Here are 273 public repositories matching this topic...
Tracking ECMAScript Proposals
javascript
language
transfer
proposal
ecmascript
spec
specification
language-design
committee
onboard
finished-proposals
Make it a fun to create spec for developers and teammates
-
Updated
Feb 17, 2021 - HTML
Human-optimized error messages for clojure.spec
-
Updated
Jul 26, 2021 - Clojure
Complete instrumentation for clojure.spec
-
Updated
Jan 1, 2021 - Clojure
Hassle-free inline clojure.spec with semi-automatic generative testing and side effect detection
-
Updated
May 8, 2021 - Clojure
-
Updated
Jun 28, 2021 - Vue
The Filecoin protocol specification
-
Updated
Jul 27, 2021 - SCSS
Clojure(Script) library for phrasing spec problems.
-
Updated
Apr 29, 2020 - Clojure
Real time console spec reporter for jasmine testing framework
-
Updated
Jul 28, 2021 - TypeScript
A small Ruby Gem to run RSpec and Serverspec, Infrataster and Capybara tests against Dockerfiles or Docker images easily.
testing
docker
devops
circleci
tdd
travis-ci
docker-compose
rspec
spec
capybara
serverspec
compliance
tdd-utilities
rspec-retry
-
Updated
Aug 30, 2017 - Ruby
Pinpointer is yet another clojure.spec error reporter based on a precise error analysis
-
Updated
Aug 10, 2019 - Clojure
Notion Abstract Syntax Tree specification.
-
Updated
Jul 10, 2021
ECMAScript spec abstract operations.
-
Updated
Jul 27, 2021 - JavaScript
matthewmcgarvey
commented
Mar 30, 2021
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.
Improve this page
Add a description, image, and links to the spec topic page so that developers can more easily learn about it.
Add this topic to your repo
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