SASS-SPEC(1)

πŸ“¦
version 3.6.3 Β· 3 versions
, in debian bookworm, ubuntu jammy, ubuntu noble

πŸŽ€ NAME πŸŽ€

sass-spec β€” bestie, this is the sass-spec testsuite for Sass implementions, and yes it lives in section 1 (User Commands) of the manual, so you can pull it up whenever your Sass implementation is acting up πŸ’…


✨ SYNOPSIS ✨

sass-spec.rb [options] [spec_directory...]

That's it. Options first, then as many spec_directory paths as your heart desires πŸ¦‹


🌸 EXAMPLES 🌸

Okay so here's the tea, two ways to run it:

  • Run sassc --style compressed input.scss: ./sass-spec.rb -c 'sass --style compressed'
  • Run tests only in the spec/basic folder: ./sass-spec.rb spec/basic

πŸ’– DESCRIPTION πŸ’–

This script will search for all files under the spec (or specified) directory that are named input.scss. It will then run a specified binary and check that the output matches the expected output. If you want set up your own test suite, follow a similar hierarchy as described in the initial comment of this script for your test hierarchy. πŸ‘‘

This command can also be used to annotate tests to control which tests are ran and when. For details: ./sass-spec.rb annotate -h ✨

🚨 Make sure the command you provide prints to stdout. Like, actually. No cap. If it doesn't, this whole thing simply will not work and you'll be sad 😭

πŸ’… OPTIONS πŸ’…

  • -v, --verbose β€” Run verbosely. Give me every last detail, I want the whole story πŸ—£οΈ
  • -t, --tap β€” Output TAP compatible report. Very structured, very demure ✨
  • -c, --command COMMAND β€” Sets a specific binary to run.
  • --dart PATH β€” Run Dart Sass, whose repo should be at the given path. Point it at the repo, babe 🎯
  • --cmd-args ARGS β€” Pass ARGS to command or Dart Sass.
  • -g, --generate β€” Run test(s) and generate expected output file(s). Manifesting the expected output into existence πŸͺ„
  • --run-todo β€” Run any tests marked as todo. Defaults to false.
  • --probe-todo β€” Run and report tests marked as todo that unexpectedly pass. Defaults to false. Sneaky little overachievers πŸ‘€
  • --impl NAME β€” Sets the name of the implementation being tested. Defaults to 'sass'
  • --filter PATTERN β€” Run tests that match the pattern you provide. Choose your fighters βš”οΈ
  • --limit NUMBER β€” Limit the number of tests run to this positive integer.
  • --migrate-impl β€” Copy tests that fail and make them pass for the current implementatino. (That spelling is straight from the source, bestie β€” we respect the lore πŸ’€)
  • --silent β€” Don't show any logs. Shhh 🀫
  • --check-annotations β€” Check if any test annotations are unecessary.
  • --interactive β€” When a test fails, enter into a dialog for how to handle it. It's giving customer service, but for broken tests 🫢

🌈 SEE YA 🌈

That's the whole page, babe. This one's sass-spec 3.6.3, dated April 2020 β€” go forth and test your implementation, and remember: if the binary doesn't print to stdout, none of this was ever going to work πŸ’œ πŸ¦‹ ✨

πŸ“¦ where this page comes from