This project is useful for linting your code with ESLint rules and guidelines.
Generate a unique filename for use in temporary directories or caches.
syntax highlighting component for react with prismjs or highlightjs ast using inline styles
Generate TeamCity service messages.
Cross platform child_process#spawn and child_process#spawnSync
Aimed at making it easier to build Jenkins compatible JUnit XML reports in plugins for testing frameworks
Wrap all spawned Node.js child processes by adding environs and arguments ahead of the main JavaScript file argument.
zlib port to javascript - fast, modularized, with browser support
A typing package for @secretlint
Core library for @secretlint.
A [JSONSchema](https://json-schema.org/) validator that uses code generation to be extremely fast.
Profile manager for Secretlint.
Config file creator for secretlint.
This package exists to make it easier to add Embroider compatibility testing to your addon's or app's continuous integration (CI) matrix.
Module Resolver Utility for textlint
A formatter collection for Secretlint.
Module Resolver Utility for Secretlint
Abstraction bin tool
A secretlint formatter for SARIF format
filesystem bindings for tar-stream
Swizzle a little something into your require() calls.
[](https://github.com/mmkal/expect-type/actions/workflows/ci.yml)  [](ht
Generate JSON schema from your Typescript sources
Regular expression for matching CSS urls.
Automate testing code on the browser by using Rack middleware to include JS testing code files into your rendered HTML.
description of gem for testing my first code.
I don't like Cucumber. I don't need plain text stories. My clients either read code or don't read any test documents, so Cucumber is mostly useless. But often, especially in full integration tests, it would be nice to have steps in a test.
== FEATURES/PROBLEMS: I have written some simple tests of my "local" code, but have not attempted to mock out SmugMug or write a bunch of fragile hard coded tests. On top of that I just put the code together without tests as I was "testing" against the API. So there are a few more rough edges than I like, but it does seem to work :-) So I know there will be bugs, sorry -- please let me know when you find them and I will try and fix them as quickly as possible. == SYNOPSIS:
I don't like Cucumber. I don't need plain text stories. My clients either read code or don't read any test documents, so Cucumber is mostly useless to me. But often, especially in full integration tests, it would be nice to have steps in a test.
Tie log (or other file) rotation to the (un-scheduled?) execution of code. The raison d'étre for this gem is that I'm too lazy to clear out test and development logs manually and am too anal-retentive to be happy with large log files accumulating in my various project directories.
I have been using Travis-CI for a few years to build, test, and deploy my apps. Bash is great, but using a higher level language for interacting with Travis and the build machine would be very beneficial. Trent is a convenient ruby gem that helps you execute system shell scripts with as little code *and pain* as possible.
Abstracts over the interfaces to the various implementation-specific profiling tools
Lookout-Rake Lookout-Rake provides Rake¹ tasks for testing using Lookout. ¹ See http://rake.rubyforge.org/ § Installation Install Lookout-Rake with % gem install lookout-rake § Usage Include the following code in your ‹Rakefile›: require 'lookout-rake-3.0' Lookout::Rake::Tasks::Test.new If the ‹:default› task hasn’t been defined it’ll be set to depend on the ‹:test› task. The ‹:check› task will also depend on the ‹:test› task. There’s also a ‹:test:coverage› task that gets defined that uses the coverage library that comes with Ruby 1.9 to check the test coverage when the tests are run. You can hook up your test task to use your Inventory¹: load File.expand_path('../lib/library-X.0/version.rb', __FILE__) Lookout::Rake::Tasks::Test.new :inventory => Library::Version Also, if you use the tasks that come with Inventory-Rake², the test task will hook into the inventory you tell them to use automatically, that is, the following will do: load File.expand_path('../lib/library-X.0/version.rb', __FILE__) Inventory::Rake::Tasks.define Library::Version Lookout::Rake::Tasks::Test.new For further usage information, see the {API documentation}³. ¹ Inventory: http://disu.se/software/inventory/ ² Inventory-Rake: http://disu.se/software/inventory-rake/ ³ API: http://disu.se/software/lookout-rake/api/Lookout/Rake/Tasks/Test/ § Integration To use Lookout together with Vim¹, place ‹contrib/rakelookout.vim› in ‹~/.vim/compiler› and add compiler rakelookout to ‹~/.vim/after/ftplugin/ruby.vim›. Executing ‹:make› from inside Vim will now run your tests and an errors and failures can be visited with ‹:cnext›. Execute ‹:help quickfix› for additional information. Another useful addition to your ‹~/.vim/after/ftplugin/ruby.vim› file may be nnoremap <buffer> <silent> <Leader>M <Esc>:call <SID>run_test()<CR> let b:undo_ftplugin .= ' | nunmap <buffer> <Leader>M' function! s:run_test() let test = expand('%') let line = 'LINE=' . line('.') if test =~ '^lib/' let test = substitute(test, '^lib/', 'test/', '') let line = "" endif execute 'make' 'TEST=' . shellescape(test) line endfunction Now, pressing ‹<Leader>M› will either run all tests for a given class, if the implementation file is active, or run the test at or just before the cursor, if the test file is active. This is useful if you’re currently receiving a lot of errors and/or failures and want to focus on those associated with a specific class or on a specific test. ¹ Find out more about Vim at http://www.vim.org/ § Financing Currently, most of my time is spent at my day job and in my rather busy private life. Please motivate me to spend time on this piece of software by donating some of your money to this project. Yeah, I realize that requesting money to develop software is a bit, well, capitalistic of me. But please realize that I live in a capitalistic society and I need money to have other people give me the things that I need to continue living under the rules of said society. So, if you feel that this piece of software has helped you out enough to warrant a reward, please PayPal a donation to now@disu.se¹. Thanks! Your support won’t go unnoticed! ¹ Send a donation: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=now%40disu%2ese&item_name=Nikolai%20Weibull%20Software%20Services § Reporting Bugs Please report any bugs that you encounter to the {issue tracker}¹. ¹ See https://github.com/now/lookout-rake/issues § Authors Nikolai Weibull wrote the code, the tests, the manual pages, and this README.
A simple testing library that works on ruby and mruby. This has been designed to be very modular, you can run different types of suites with different setup/teardown and before/after blocks. You can have as many reporters as you want, these can range from "output to the terminal in a nice way" all the way to "shape the results into an XML or JSON for my CI". The secondary purpose of this testing library is to work with mruby for my game engine Taylor and any project built upon that. I also plan to support quite a few ruby versions as I want the code for this to be very portable. The main feature I don't want to drop is positional AND keyword arguments in definitions, this means anything that matches the Ruby 2.6+ spec should be compatible.
I sometimes get a little descriptive with my variable names, so when you're doing a lot of work specifically with one object, it gets especially ugly and repetetive, making the code harder to read than it needs to be: @contract_participants_on_drugs.contract_id = params[:contract_id] @contract_participants_on_drugs.participant_name = params[:participant_name] @contract_participants_on_drugs.drug_conviction = DrugConvictions.find(:wtf => 'this is getting ridiculous') ... And so on. It gets ridiculous. Utility Belt implements a with(object) method via a change to Object: class Object #utility belt implementation def with(object, &block) object.instance_eval &block end end Unfortunately, that just executes the block in the context of the object, so there isn't any crossover, nor can you perform assignments with attr_accessors (that I was able to do, anyway). So, here's With.object() to fill the void. With.object(@foo) do a = "wtf" b = "this is not as bad" end In the above example, @foo.a and @foo.b are the variables getting set. If you prefer, you can require 'with_on_object' instead and use the notation with(object) do ... end. The tests in the /test directory offer more examples of what's been implemented and tested so far (except where noted - namely performing assignment to a variable that was declared outside the block, and is not on @foo). Not everything is working yet, but it works for the simplest, most common cases I've run up against. More complex tests are on the way, along with code to make them pass. Special thanks to Reg Braithwaite, for help and ideas along the way.
Remote syslog appender for Logging
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.