Centralized authentication and authorization API for multiple independent services. Manages users, roles, permissions, and service associations.
An equation parser using the finum crate
Multi-sequence extractor from FASTA using FAI indexing, with parallelism and flexible region input formats.
A Rust library for managing and processing sequences of events.
Regex-like pattern matching for arbitrary sequences using predicate functions
Generate your pattern files through this generator: Eq. rails g pattern MyCustomDecorator
advanced_subject attempts to cut out having to explicitly write the subject of your example group when trying to call methods or add arguments to methods. It works by reading the conventional description syntax to determine what the method you are calling is and later you state what you are passing to it. Given you have a file advanced_subject_spec.rb. ```ruby describe Hash do when_initialized_with [:a, :b] do it { should eq({a: :b}) } describe '#fetch' do when_passed :a do it { should eq(:b) } end end end end ``` When you run `rspec -f d advanced_subject_spec.rb` it will output: ``` Hash when initialized with [:a, :b] should eq {:a => :b} #fetch when passed :a should eq :b ```
RFC7516-compliant JSON Web Encryption (JWE) token generator that uses RSAES-OAEP and AES GCM. Suitable for use with the ONS eQ Survey Runner.
Adds the `maybe` syntax to RSpec: describe Thing do it 'is maybe equal to another thing' do maybe(Thing.new).will eq(another_thing) # Passes sometimes. Maybe. end end
Oktest.rb is a new-style testing library for Ruby. You can write `ok {1+1} == 2` instead of `assert_equal 2, 1+1` or `expect(1+1).to eq 2`. In addition, Oktest.rb supports **Fixture injection** feature inspired by dependency injection and **JSON Matcher** feature similar to JSON schema. See https://github.com/kwatch/oktest/tree/ruby/ruby for details.
For tests that need to modify files
Remember when RSpec had stub_chain? They removed it for good reasons but sometimes you just need it. Well, here it is, a proxy object. It doesn't actually mock anything for you (the name is just catchy) so you need to do that. But that actually comes with a lot of benefits: 1) It's compatable with any testing framework 2) You can use it for purposes other than testing, e.g. prototyping, code stubs 3) Flexibility in how you use it without overloading the number of methods you have to remember Here's an example usage: let(:model_proxy) do MockProxy.new(email_client: { create_email: { receive: proc {} } }) end before { allow(Model).to receive(:new).and_return model_proxy } it 'should call receive' do proc = MockProxy.get(model_proxy, 'email_client.create_email.receive') expect(proc).to receive(:call) run_system_under_test MockProxy.update(mock_proxy, 'email_client.create_email.validate!') { true } MockProxy.observe(mock_proxy, 'email_client.create_email.send') do |to| expect(to).to eq 'stop@emailing.me' end run_system_under_test2 end As you can see, the proc - which ends the proxy by calling the proc - can be used for anything. You can spy on the call count and arguments, mock methods, or just stub out code you don't want executed. Because it doesn't make any assumptions, it becomes very flexible. Simple, yet powerful, it's uses are infinite. Enjoy
GraphQL interface over WCC::Contentful store
Contentful API wrapper library exposing an ActiveRecord-like interface