casacore_assay(1)

📦 version 3.8.1, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 casacore_assay — the manual, but make it make sense 💖

okay bestie, welcome to casacore_assay, a lil' page from the General Commands Manual section of your friendly neighbourhood casacore docs. it's a test-runner wrapper. it's giving "personal assistant for your test suite". let's get into it 🫶

✨ NAME ✨

casacore_assay — invoke an AIPS++ test program and verify its output

like, it runs your test and then checks that the test actually did the thing it was supposed to do. main character energy fr fr 👑

🌸 SYNOPSIS 🌸

casacore_assay testexe

one argument. that's it. we love a minimal interface 💅

🦋 DESCRIPTION 🦋

so here's the vibe: casacore_assay invokes a casacore test program. simple enough.

but the way it decides how to invoke it? iconic. two paths:

  • if the test program has an associated .run file, it just simply invokes it. no extra steps, no drama. that's it.
  • otherwise, casacore_assay invokes the test executable directly, and then — if there's a corresponding .out file — it compares the test's output against that file. output disagreement gets caught. no cap.

also, plot twist: if there's a .in file associated with the test program, then assay will redirect stdin from it 🎀. so your test gets fed the input it expects, automatically. queen behaviour.

🍓 Exit status: 🍓

here's the receipts — what each exit code is telling you:

  • 0 — success ✨ everything worked, slay
  • 1 — test execution failed 😭 the test itself didn't run right
  • 2 — test output disagreement 💀 the test ran, but its output did not match the .out file
  • 3 — untested (usually returned from a .run) 🙈
  • 130 — interrupt ⚡ somebody hit that Ctrl-C

🌈 ENVIRONMENT VARIABLES 🌈

  • CASACORE_CHECK — do checking using tools like valgrind. it defines a script that will execute the command. that script can invoke the checking tool. and if you set it to 1, yes, or YES, the script casacore_memcheck will be used, which uses valgrind's memcheck tool. 🧚 memory leak detection, but make it automatic.

👑 AUTHOR 👑

this manual page was written according to the in-program comments by Benda Xu <heroxbd@gentoo.org>, for the Debian GNU/Linux system. respect the author, bestie 🫡

ngl if your test is disagreeing with its .out file, that's exit code 2 and it's not being subtle about it 💀

and that's the whole page, no notes. this was casacore_assay from casacore, dated 2016-03-25. periodt 💖✨🦋

📦 where this page comes from