- Ruby 73.2%
- C# 10%
- JavaScript 5.2%
- HTML 4.9%
- Shell 2.5%
- Other 4.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
4afb729b33ControllerContext declared params/session/cookies/request/flash/render/ redirect_to/respond_to as abstract sigs. Tapioca's generated controller RBIs include the helper modules into every controller, so all 31 controllers became concrete classes inheriting eight unimplemented abstract methods: 33 'Missing definitions for abstract methods' (5023) errors, 964 vs the 919 baseline. The gate was reconciled by raising the baseline instead of fixing the cause. The concern's declarations are also the only static source of the Rails context methods for controllers (this project ships no actionpack gem RBIs), so they cannot simply be deleted - removing any of them turns every controller's flash/respond_to/render/redirect_to call into new 7003 errors. Declare the eight methods as plain super-forwarding methods instead: statically identical resolution, no abstract obligation, and one less runtime indirection than the abstract stub. Errors drop 964 -> 931; lower the baseline accordingly. |
||
| .claude | ||
| .github | ||
| .helix | ||
| .licenses/bundler | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| gems | ||
| hooks | ||
| lib | ||
| log | ||
| public | ||
| sorbet | ||
| spec | ||
| spencers_app | ||
| storage | ||
| test | ||
| tmp | ||
| vendor | ||
| .better-html.yml | ||
| .dockerignore | ||
| .env.example | ||
| .erb-lint-tracking | ||
| .erb_lint.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .licensed.yml | ||
| .parallel_rspec | ||
| .rspec | ||
| .rspec_status | ||
| .rubocop.yml | ||
| .ruby-version | ||
| .standard.yml | ||
| .yamllint.yml | ||
| 14960.md | ||
| attributions.json | ||
| ATTRIBUTIONS.md | ||
| biome.json | ||
| BOUNCING_PILLOW_FIELDS.md | ||
| CLAUDE.md | ||
| code_standard_violations.txt | ||
| config.ru | ||
| devenv.lock | ||
| devenv.nix | ||
| devenv.yaml | ||
| Dockerfile | ||
| erb_lint_output.txt | ||
| Gemfile | ||
| Gemfile.lock | ||
| ID_GENERATION.md | ||
| IMPROVEMENT_PLAN.md | ||
| LICENSE | ||
| NEW_UNIT_TYPES.md | ||
| OFFLINE.md | ||
| Rakefile | ||
| README.md | ||
| RPII_TODO_08_08.md | ||
| standardrb_output.txt | ||
| terragon-setup.sh | ||
| TEST-QUALITY-CRITERIA.md | ||
| TODO.md | ||
| unfixed_issues.txt | ||
play-test - BS EN 14960 inspection-logging tool
A web app for managing safety inspections of inflatable play equipment like bouncy castles and slides. Developed by Chobble CIC, a community interest company in Manchester, UK.
play-test helps inspectors track and document safety checks on inflatable play equipment. It handles equipment records, inspection forms, photo management, and PDF report generation. Makes repeat inspections of the same units quick and straightforward.
A public instance is live at play-test.co.uk.
Sponsor Development
Features
🎪 Equipment Tracking
- Store unit details, dimensions, and manufacturer info
- Keep inspection history for each piece of equipment
- Upload photos with automatic processing
- Quick access to previous inspection data
📋 Inspection Management
- Seven assessment types covering different safety aspects
- Draft inspections you can edit before finalising
- Generate PDF reports with QR codes
- Built-in safety calculations (anchor points, user capacity, etc.)
👥 Company Management
- Company accounts with branding
- User management and access control
- Upload your logo for PDF reports
- Works on phones, tablets, and desktops
🛠️ Technical Features
- Export any unit or inspection as PDF or JSON
- Shows safety standards right where you need them
- Dark/light theme
- Minimal dependencies
- Full internationalisation support
- No JavaScript required for core functionality
Getting Started
Docker
Quickest way to try it out:
docker pull dockerstefn/play-test
docker run -p 3000:3000 dockerstefn/play-test
Production builds exclude development, test and CI-only gem groups, including
licensed and its Rugged dependency. Licence auditing still runs in CI.
The BUNDLE_WITHOUT build argument can be overridden for non-production images.
Development Setup
Uses devenv for easy environment setup:
# Clone the repo
git clone https://github.com/yourusername/play-test.git
cd play-test
# Enter the development environment (run `devenv shell` again whenever you need it)
devenv shell
# Standard Rails setup
bundle install
rails db:create db:migrate db:seed
rails server
Traditional Setup
# Requires the Ruby version in .ruby-version and SQLite
bundle install
rails db:setup
rails server
Ubuntu 26.04 also requires libjitterentropy3-dev for Rugged's static OpenSSL
link during bundle install. CI installs it in the shared setup action;
the devenv configuration is unchanged.
The shared CI setup refreshes APT indexes and installs packages directly. Failed downloads stop setup instead of leaving missing native libraries for Rails to load.
Testing
Currently over 90% test coverage:
# Run all tests with coverage
bin/test
# Check specific file coverage
bin/coverage_check app/models/inspection.rb
# View detailed HTML report
open coverage/index.html
Tests use a separate SQLite WAL database per process. Ordinary examples use Rails' transactional fixtures, which pin the database connection across request cleanup. Do not replace these with unpinned DatabaseCleaner transactions: Rails can return their still-open transactions to the pool between requests.
Examples tagged js: true or concurrent use committed data and
DatabaseCleaner truncation after Capybara finishes pending requests. Tag
examples that make database requests from additional threads accordingly.
IN_MEMORY_DB=true remains an explicit option for mutant's isolated forks.
Security scans run bin/brakeman --no-pager, which requires the latest
Brakeman release. Update it with bundle update brakeman --conservative
when the version check fails.
Test Coverage
If you want to help improve Play-Test, a great way would be to write some more rspec and Capybara tests. Check out coverage.play-test.co.uk for an up-to-date test coverage breakdown.
Tech Stack
- Rails 8.0+ - With minimal gems
- SQLite - No fancy databases (yet?)
- RSpec & Capybara - 90%+ test coverage
- Semantic HTML + MVP.css - Simple CSS
- Turbo for progressive JS enhancement
About Chobble CIC
play-test is developed by Chobble CIC, a community interest company based in Manchester, UK. As a CIC, Chobble is regulated to operate in the public interest rather than for private shareholders — surplus profits are reinvested in community activities like open source development and reduced rates for charities and community organisations.
Chobble's principles include transparency, fair pricing, client ownership of their tools and data, and ethical boundaries. All source code is shared openly, and there's no vendor lock-in.
Contributing
Pull requests welcome! This is an open source project and we're not affiliated with any industry bodies, so improvements from anyone are appreciated.
AGPLv3 - see LICENSE file. This means you can use, modify, and distribute the code, but you must share any improvements.