teamcapybara/capybara

0

/ 100

Documentation91
Engineering74
Health95
Ruby10,165MIT2mo ago
Grade a repo

Popular and well-maintained. A little polish away from elite status.

Acceptance test framework for web applications

Documentation

91

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

74

Reproducibility6pt22

No dependency lockfile found (−70 pts).

→ Commit Gemfile.lock so Bundler installs are repeatable.

CI/CD14pt68

CI is configured (.github/workflows/build.yml).

Tests18pt80

Test files detected (lib/capybara/spec).

Linting and formatting5pt100

Ruby linting configured (.rubocop.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

95

Activity5pt80

Actively maintained (pushed within 3 months).

Dependency manifest6pt100

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • features
  • gemfiles
  • lib
    Good: Test files detected (lib/capybara/spec).
  • spec
  • .codeclimate.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .rspec
  • .rubocop.yml
    Good: Ruby linting configured (.rubocop.yml).
  • .yardopts
  • appveyor.yml.outdated
  • capybara.gemspec
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • gem-public_cert.pem
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • History.md
  • License.txt
    Good: Licensed under MIT.
  • Rakefile
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • UPGRADING.md