A CLI program which can process the steps that GitHub Copilot Chat might produce.
Provides low-level interfaces and helper methods for tracing in Azure SDK
Core library for interfacing with AutoRest generated code
Pre-built WASM files for Tree-Sitter and Tree-Sitter languages that VS Code uses
Polyfill for IE/Node 8 for Symbol.asyncIterator
Isomorphic client library for Azure KeyVault's keys.
steps ui component for react
A lightweight and trustworthy URL polyfill for React Native
Damerau - Levenshtein distance by The Spanish Inquisition + relative distance
steps ui component for react
Launch related operations
Azure Storage Common Client Library for JavaScript
Core library for shared utility methods
TBD
Core logic for the steps widget implemented as a state machine
react animation library
A react multi-step, wizard component for managing data collection via forms and sub components
A dead-easy-to-use light-weight react hook to handle multi-paths wizards (and simple wizards too) and navigate into them.
Core library for interacting with XML payloads
Rotate an array by a given number of steps
Core library for interfacing with Azure Rest Clients
Official React Native Tracking Library for Mixpanel Analytics
Common internal functionality for all of the Azure Key Vault clients in the Azure SDK for JavaScript
Axios interceptor to store, use, and refresh tokens for authentication.
Do dry run for turnip feature specs to get some step metadata.
With neverfails, step definitions do not simply check whether the existing code satifies the required behaviour or not. They also write the code to make them pass.
The Ultimate Gravatar Gem! This gem is used to interface with the entire Gravatar API: it's not just for generating image URLs, but for connecting to and communicating with the XML-RPC API too! Additionally, it can be used to download the Gravatar image data itself, rather than just a URL to that data. This saves you the extra step of having to do so.
A minimal implementation of integration testing within RSpec. Allows you to build sequential specs, each with a description, but where state is maintained between tests and before/after actions are only triggered at the beginning and end of the entire sequence. Cool things you can do with this: * Build multi-step user stories in plain RSpec syntax. Locate the point of failure quickly, and break up large integrations into sensible steps * Speed up groups of related tests by running your factories only once before the whole group.
BlackStack Deployer automates what you already know how to do manually, but in a repeatable, scalable fashion. There is no magic here! BlackStack Deployer dutifully connects to your server(s) via SSH and executes the steps necessary to deploy your project. You can define those steps yourself, or by using pre-built task libraries provided by the BlackStack Deployer community.
Help the user get to a place where the speedy F8/F10/F11/etc keys work. == Pry F-Keys [+F4+] ls -l (show all locally-defined variables and values) [+F5+] whereami (show the code context) [+F6+] up (a frame, depends on pry-stack_explorer, as does the next one) [+F7+] down [+F8+] continue (depends on pry-debugger, as do step/next/finish) [+Shift-F8+] try-again (restart from last 'raise', depends on pry-rescue) [+F10+] next (run the current statement) [+F11+] step (step into the next method call) [+Shift-F11+] finish (get back out of the last 'step')
robotag analyzes a cucumber suite. It finds Scenarios and Scenario outlines with steps that match certain patterns. It ensures that the associated scenarios or outlines contain or do not contain certain tags
Leash provides a lightweight framework to implement "Do Nothing Scripting" with Ruby. A "do nothing script" is a script that encodes instructions of a manual procedure and encapsulates each step in a function. Making it easier to start small and gradually increase the level of automation.
Deployer automates what you already know how to do manually, but in a repeatable, scalable fashion. There is no magic here! Deployer dutifully connects to your server(s) via SSH and executes the steps necessary to deploy your project. You can define those steps yourself, or by using pre-built task libraries provided by the Deployer community.
Accounting sucks. Well if you are trying to do it right it does. Bean machine gives you the power of an immutable double entry accounting system through the use of a simple transfer method. The idea is to make accounting easy by breaking it into easy to follow steps. Transfer this much from this account to that account.
progression provides a set of simple utility classes and a DSL for measuring an objects progress through a progression of steps. This is especially useful for defining and calculating profile completion status in a social application. There are a few existing solutions similar to progression, but they try to do too much. The other options that I am familiar with are either coupled with ActiveRecord or ActionController in some way.
Problem: While Cucumber is an awesome tool, for some kinds of tests it's default behaviour becomes an obstacle. Testing large batches of input against a slow error prone system is the source of much frustration. Cucumber will skip remaining steps on failure or error. This is especially problematic if the test input is a dynamic collection, *(e.g. results of a database query). This is opposed to a static collection testing which is solved by a Scenario Outline. Solution: We need to step putside Cucumber's default pass/fail/error handling. Capture all failures and errors in collections. Log errors and failures. Generate a pass/fail manifest against the test inputs. Do not use this for normal BDD style testing, Cucumber's default behaviour is perfect for that. Public Interface: This is a works in progress so I expect changes as usage reveals more. In your cucumber env.rb Before do |scenario| setup_unstoppable end After do |scenario| print unstoppable_failures(scenario) print unstoppable_errors(scenario) end In a step definition wrap any operation that you do not wish to stop execution like so unstoppable do expect(thing).to be(exected_thing) end This helper method does the following: runs executes the block catches any exception 2a. adds error to errors collection if an error 2b. adds expectation failure to failures collection if error is an RSpec::Expectations::ExpectationNotMetError logs error/failure
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.