fake_sonic_pi 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: d306b88cdd84d84172709495158c2a2f3f61b2c099b6a1d55b46121c6e12a6c1
+  data.tar.gz: d53eb547c51649cf9b661c5483bfeb0d345bc315d4791e1ec1aa6d3d4466b422
+SHA512:
+  metadata.gz: b8039570e4646317dfa352bd9ec8f5f53783658e19b854f8becf6a7146500901f5ee3dfdb9de1bf263031a8fc9c3e90b6d9e25053cae8d5f9d104dc07f81084e
+  data.tar.gz: ac3bbe806b6f8d3ac46f60df7ae3ecdd67fba167eced1943dfa933efeda2f9caf72866bda0dfac7b2f6c45bd288241eb9fb5380d797f5d9d2d3e13c9286f2f52

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at sgilperez@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,9 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gemspec
+
+gem "rake"
+gem "rspec"
+gem "standard"

data/Gemfile.lock

@@ -0,0 +1,63 @@
+PATH
+  remote: .
+  specs:
+    fake_sonic_pi (0.1.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ast (2.4.2)
+    diff-lcs (1.5.0)
+    json (2.6.2)
+    parallel (1.22.1)
+    parser (3.1.2.1)
+      ast (~> 2.4.1)
+    rainbow (3.1.1)
+    rake (13.0.6)
+    regexp_parser (2.6.0)
+    rexml (3.2.5)
+    rspec (3.11.0)
+      rspec-core (~> 3.11.0)
+      rspec-expectations (~> 3.11.0)
+      rspec-mocks (~> 3.11.0)
+    rspec-core (3.11.0)
+      rspec-support (~> 3.11.0)
+    rspec-expectations (3.11.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-mocks (3.11.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-support (3.11.1)
+    rubocop (1.35.1)
+      json (~> 2.3)
+      parallel (~> 1.10)
+      parser (>= 3.1.2.1)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8, < 3.0)
+      rexml (>= 3.2.5, < 4.0)
+      rubocop-ast (>= 1.20.1, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 3.0)
+    rubocop-ast (1.22.0)
+      parser (>= 3.1.1.0)
+    rubocop-performance (1.14.3)
+      rubocop (>= 1.7.0, < 2.0)
+      rubocop-ast (>= 0.4.0)
+    ruby-progressbar (1.11.0)
+    standard (1.16.1)
+      rubocop (= 1.35.1)
+      rubocop-performance (= 1.14.3)
+    unicode-display_width (2.3.0)
+
+PLATFORMS
+  x86_64-linux
+
+DEPENDENCIES
+  fake_sonic_pi!
+  rake
+  rspec
+  standard
+
+BUNDLED WITH
+   2.3.11

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 Sergio Gil
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,163 @@
+# FakeSonicPi
+
+`FakeSonicPi` is a small utility class used to test Sonic Pi related code. It
+implements a tiny subset of its API in a silent (yep, no sound) and
+instant-running (as opposed to the real Sonic Pi, which is supposed to keep
+running indefinitely). It was originally part of the test suite of
+[sonic-pi-akai-apc-mini](https://github.com/porras/sonic-pi-akai-apc-mini), so
+it implements only a very small part of the Sonic Pi API, focusing on timing
+(being able to check what happens at which time). Since extracting, I've also
+used it to test [ptn](https://github.com/porras/ptn) and added a couple of
+features needed for it.
+
+If that doesn't make much sense, have a look at the examples in this README, the
+tests in `spec/`, and the tests of the projects that use it.
+
+## Installation
+
+Install the gem and add to the library's Gemfile by executing:
+
+    $ bundle add fake_sonic_pi
+
+## Usage
+
+You need to start by requiring it in your test, your `test_helper.rb`, or
+`spec_helper.rb`. Then, you can use it to define a Sonic Pi program, in a block.
+That would be what you would type on a Sonic Pi buffer:
+
+```ruby
+sp = FakeSonicPi.new do
+  live_loop :drums do
+    sample :bd_haus
+    sleep 0.5
+  end
+end
+```
+
+Then, you can _run_ it (you don't really run it but **simulate** it) for a number of beats:
+
+```ruby
+sp.run(2)
+```
+
+After doing that, the `sp` object has an `output`, which contains the sounds
+(and other events that your code has produced), associated to the timing where
+they happened:
+
+```
+#<FakeSonicPi::Events:0x000055ac84368978
+ @events=
+  [[0.0,
+    #<struct FakeSonicPi::Events::Event
+     name=:sample,
+     value=[:bd_haus],
+     processed_by=#<Set: {}>>],
+   [0.5,
+    #<struct FakeSonicPi::Events::Event
+     name=:sample,
+     value=[:bd_haus],
+     processed_by=#<Set: {}>>],
+   [1.0,
+    #<struct FakeSonicPi::Events::Event
+     name=:sample,
+     value=[:bd_haus],
+     processed_by=#<Set: {}>>],
+   [1.5,
+    #<struct FakeSonicPi::Events::Event
+     name=:sample,
+     value=[:bd_haus],
+     processed_by=#<Set: {}>>],
+   [2.0,
+    #<struct FakeSonicPi::Events::Event
+     name=:sample,
+     value=[:bd_haus],
+     processed_by=#<Set: {}>>]]>
+```
+
+You can use this object to check that your code did what it should. The internal
+structure is as follows (as you can see in the inspect output above):
+
+* It has an `events` attribute, which is an array of pairs
+* In each pair:
+  * The first element is a `Float`, referencing the beat in which the event happened.
+  * The second one is an `Event` object, with the following attributes:
+    * `name`: the type of event: `:play`, `:sample`, `:midi_note_on`, ...
+      (basically the Sonic Pi command that was called).
+    * `value`: an array with the arguments passed to that command (the sample
+      name, the note, etc.).
+
+So you can check that your example produced one `:bd_haus` sound each half beat with something like this:
+
+```ruby
+assert_equal 5, sp.output.events.size
+
+beat, event = sp.output.events[0]
+assert_equal 0.0, beat
+assert_equal :sample, event.name
+assert_equal :bd_haus, event.value.first
+```
+
+### RSpec
+
+If you use RSpec, a matcher is provided to make such assertions simpler. Require
+`fake_sonic_pi/rspec` in your `spec_helper.rb` and you can do the following:
+
+```ruby
+expect(sp).to have_output(:sample, :bd_haus).at(0, 0.5, 1, 1.5, 2)
+```
+
+Check the `spec/` directory for more examples.
+
+### Implemented subset / Limitations
+
+The following commands of the API are implemented:
+
+* `play`
+* `sample`
+* `sleep`
+* `at`
+* `midi_note_on` / `midi_note_off`
+* `get` / `set` / `cue` / `sync`
+* `stop`
+* `in_thread` (but not completely, so depending on what you do in the thread, it might not work as expected)
+* `live_loop` (but not the `sync` option)
+* `with_fx`
+* `control`
+* `set_volume!`
+
+The main limitation is that several commands (prominently `sleep`) don't work if
+they're not inside a `live_loop`. This is quite different of the real Sonic Pi,
+where such limitation doesn't exist, but it is in general possible to write your
+tests using `live_loop`s, so, at least for the libraries I've used FakeSonicPi
+with, it is not such a big deal.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run
+`rake spec` to run the tests. You can also run `bin/console` for an interactive
+prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To
+release a new version, update the version number in `version.rb`, and then run
+`bundle exec rake release`, which will create a git tag for the version, push
+git commits and the created tag, and push the `.gem` file to
+[rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at
+https://github.com/porras/fake_sonic_pi. This project is intended to be a safe,
+welcoming space for collaboration, and contributors are expected to adhere to
+the [code of
+conduct](https://github.com/porras/fake_sonic_pi/blob/main/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT
+License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the FakeSonicPi project's codebases, issue trackers,
+chat rooms and mailing lists is expected to follow the [code of
+conduct](https://github.com/porras/fake_sonic_pi/blob/main/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,9 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+require "standard/rake"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: [:spec, "standard:fix"]

data/fake_sonic_pi.gemspec

@@ -0,0 +1,31 @@
+# frozen_string_literal: true
+
+require_relative "lib/fake_sonic_pi/version"
+
+Gem::Specification.new do |spec|
+  spec.name = "fake_sonic_pi"
+  spec.version = FakeSonicPi::VERSION
+  spec.authors = ["Sergio Gil"]
+  spec.email = ["sgilperez@gmail.com"]
+
+  spec.summary = "Support library to write tests for Sonic Pi code"
+  spec.description = "fake_sonic_pi is a reimplementation of a small subset of the Sonic Pi"
+  spec.homepage = "https://github.com/porras/fake_sonic_pi"
+  spec.license = "MIT"
+  spec.required_ruby_version = ">= 2.6.0"
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = spec.homepage
+  # spec.metadata["changelog_uri"] = "TODO: Put your gem's CHANGELOG.md URL here."
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(__dir__) do
+    `git ls-files -z`.split("\x0").reject do |f|
+      (f == __FILE__) || f.match(%r{\A(?:(?:bin|test|spec|features)/|\.(?:git|travis|circleci)|appveyor)})
+    end
+  end
+  spec.bindir = "exe"
+  spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+end

data/lib/fake_sonic_pi/events.rb

@@ -0,0 +1,39 @@
+class FakeSonicPi
+  class Events
+    attr_reader :events
+
+    Event = Struct.new(:name, :value, :processed_by) do
+      def initialize(name, value)
+        super(name, value, Set.new)
+      end
+    end
+
+    def initialize
+      @events = []
+    end
+
+    def most_recent(beat, name)
+      @events.select { |b, e| b <= beat && e.name == name }.max_by(&:first)&.last
+    end
+
+    def next_beat(beat)
+      @events.map(&:first).sort.find { |b| b > beat }
+    end
+
+    def find(beat, name)
+      @events.find { |b, e| b == beat && e.name == name && !e.processed_by.include?(Fiber.current) }&.last
+    end
+
+    def add_batch(events)
+      events.each { |b, n, v| add b, n, v }
+    end
+
+    def add(beat, name, value)
+      @events << [beat, Event.new(name, value)]
+    end
+
+    def ==(other)
+      other.is_a?(self.class) && @events == other.events
+    end
+  end
+end

data/lib/fake_sonic_pi/rspec.rb

@@ -0,0 +1,25 @@
+require "rspec/matchers"
+require_relative "../fake_sonic_pi"
+
+RSpec::Matchers.define :have_output do |command, *args|
+  match do |sp|
+    expect(@beats).to all(satisfy do |beat|
+                            beat_commands = sp.output.events.select { |b, *_| b == beat }.map(&:last)
+                            expect(beat_commands).to include(have_attributes(name: command, value: args))
+                          end)
+  end
+
+  chain :at do |*beats|
+    @beats = beats.map(&:to_f)
+  end
+end
+
+# TODO: The matching is very simplistic, ok for now but might need some refining
+# to be able to pass other matchers.
+RSpec::Matchers.define :a_node do |command, arg|
+  match do |actual|
+    expect(actual).to be_a(FakeSonicPi::Node)
+    expect(actual.command).to eq command
+    expect(actual.args.first).to eq(arg)
+  end
+end

data/lib/fake_sonic_pi/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+class FakeSonicPi
+  VERSION = "0.1.0"
+end

data/lib/fake_sonic_pi.rb

@@ -0,0 +1,154 @@
+require "fiber" # for Ruby < 3.0
+require "set"
+require_relative "fake_sonic_pi/version"
+require_relative "fake_sonic_pi/events"
+
+class FakeSonicPi
+  class NoSleep < StandardError; end
+
+  attr_reader :output
+
+  def initialize(&definition)
+    @definition = definition
+    @output = Events.new
+    @events = Events.new
+    @beat = 0.0
+    @fibers = {}
+  end
+
+  # MAGIC :D I mean Fibers ;)
+  def run(beats, events: [])
+    @events.add_batch(events)
+    instance_eval(&@definition)
+    loop do
+      # remove terminated fibers (`at` blocks that already ran)
+      @fibers.select! { |f, _b| f.alive? }
+
+      # split fibers waiting for an event, and fibers scheduled for a particular
+      # beat (sleeping or scheduled with `at`)
+      waiting_fibers, scheduled_fibers = @fibers.partition { |_f, b| b.nil? }
+
+      # from the scheduled ones, remove those scheduled for after the max number of beats
+      scheduled_fibers.reject! { |_f, b| b > beats }
+
+      # give all waiting fibers a chance
+      events_before = @events.dup
+      waiting_fibers.each do |f, _b|
+        @fibers[f] = f.resume
+      end
+      # if any of them added an event, do it again
+      next if events_before != @events
+
+      # find next scheduled fiber (and for when is it scheduled?)
+      next_fiber, next_beat = scheduled_fibers.min_by { |_f, beat| beat }
+
+      # is there any event to happen before next_beat? if so, process that before
+      next_beat_with_event = @events.next_beat(@beat)
+      if next_beat_with_event && (next_beat.nil? || next_beat_with_event < next_beat)
+        @beat = next_beat_with_event
+        next
+        # otherwise proceed with the next scheduled fiber
+      elsif next_fiber
+        @beat = next_beat
+        @fibers[next_fiber] = next_fiber.resume
+        # and if there is none, then we're done \o/
+      else
+        break
+      end
+    end
+  end
+
+  def live_loop(name, &block)
+    # create a fiber that runs the block repeatedly...
+    f = Fiber.new do
+      loop do
+        Thread.current[:slept] = false
+        block.call
+        raise NoSleep, "live_loop #{name} didn't sleep" unless Thread.current[:slept]
+      end
+    end
+    # ...and schedule it for now
+    @fibers[f] = @beat
+  end
+
+  # sleep the fast way ;)
+  def sleep(n)
+    Thread.current[:slept] = true
+    Fiber.yield @beat + n
+  end
+
+  def at(*beats, &block)
+    # for each specified beat, create a fiber that calls the block once, and
+    # schedule it for then.
+    beats.each do |beat|
+      f = Fiber.new(&block)
+      @fibers[f] = @beat + beat
+    end
+  end
+
+  def sync(event_name)
+    loop do
+      Thread.current[:slept] = true
+      # find event in current beat and return its value, otherwise let the other
+      # fibers progress, then try again
+      if (event = @events.find(@beat, event_name))
+        event.processed_by << Fiber.current
+        return event.value
+      else
+        Fiber.yield nil
+      end
+    end
+  end
+
+  def get(name, default = nil)
+    if (event = @events.most_recent(@beat, name))
+      event.value
+    else
+      default
+    end
+  end
+
+  def set(name, value)
+    @events.add(@beat, name, value)
+  end
+
+  alias_method :cue, :set
+
+  def in_thread
+    # just do it ;) fibers are awesome :D
+    yield
+  end
+
+  def stop
+    # kind of stop :D
+    sleep Float::INFINITY
+  end
+
+  # commands we store as output, returning a (fake) node
+  %i[play sample synth control midi_note_on set_volume!].each do |command|
+    define_method(command) do |*args|
+      @output.add @beat, command, args
+      Node.new(command, args)
+    end
+  end
+
+  def with_fx(*args, &block)
+    block.call(Node.new(:fx, args))
+  end
+
+  Node = Struct.new(:command, :args) do
+    def kill
+      # no-op
+    end
+  end
+
+  # no-ops (sonic pi commands whose effect is not relevant here, but need to be
+  # implemented so that the test doesn't fail)
+  %i[use_real_time].each do |cmd|
+    define_method(cmd) { |*_args| }
+  end
+
+  def include(*args)
+    self.class.include(*args)
+  end
+end

data/sig/fake_sonic_pi.rbs

@@ -0,0 +1,4 @@
+module FakeSonicPi
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -0,0 +1,58 @@
+--- !ruby/object:Gem::Specification
+name: fake_sonic_pi
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Sergio Gil
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2022-10-20 00:00:00.000000000 Z
+dependencies: []
+description: fake_sonic_pi is a reimplementation of a small subset of the Sonic Pi
+email:
+- sgilperez@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".rspec"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- fake_sonic_pi.gemspec
+- lib/fake_sonic_pi.rb
+- lib/fake_sonic_pi/events.rb
+- lib/fake_sonic_pi/rspec.rb
+- lib/fake_sonic_pi/version.rb
+- sig/fake_sonic_pi.rbs
+homepage: https://github.com/porras/fake_sonic_pi
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/porras/fake_sonic_pi
+  source_code_uri: https://github.com/porras/fake_sonic_pi
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.6.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.32
+signing_key:
+specification_version: 4
+summary: Support library to write tests for Sonic Pi code
+test_files: []