A unitt bug in Arturo?

I’m getting this both locally and in the web editor:

===== tests/test-leap.art =====

Suite: Leap 
 
    ✅ - assert that a year not divisible by 4 is a common year 
         assertion: 
══╡ Name Error ╞════════════════════════════════════════════════════ <script> ══

  Cannot resolve requested value

  Identifier not found: 
      as

  ┃ File: /root/.arturo/packages/cache/unitt/1.1.2/unitt.art
  ┃ Line: 269
  ┃ 
  ┃  267 ║                  
  ┃  268 ║                  prints " "
  ┃  269 ║►                 prints as.code val
  ┃  270 ║              ]
  ┃  271 ║  

  Hint: Perhaps you meant... asec ?
                             or... asin ?
                             or... case ?



===== Statistics =====

⏏️    TOTAL: 1 assertions
✅  PASSED: 1 assertions
⏩ SKIPPED: 0 assertions
❌  FAILED: 0 assertions

===== ========== =====


══╡ Program Error ╞═════════════════════════════════════════════════ <script> ══

  Some tests failed!

I have

$ arturo --version
arturo v/0.9.84-alpha b/3385.nightly.2025-06-25 (arm64/macOS)

Perhaps I’ll try to acquire 0.9.83

Known issue unfortunately. as was deprecated back in April, and unitt hasn’t been updated yet to resolve the issue. If you source a nightly from before April 10th, you should be set.

I was under the impression the online test runner would be fine though. The last update to the Dockerfile was in February.

It sure would be good if they told the docs.

That’s the documentation for the stable release. Use Library | Documentation - Arturo to access the docs for the nightly. It’s confusing the first few times.

Hmm, it’s never going to be precise, is it? We have to use a nightly from April 2025, but the “master” docs are today’s.

Bump `unitt` to 2.0.1 by BNAndras · Pull Request #38 · exercism/arturo-test-runner · GitHub and unitt v2 by BNAndras · Pull Request #159 · exercism/arturo · GitHub should bring the nightly up-to-date and resolve the unitt issue. I missed that it had been fixed a while back.

2 Likes