dfinity / dfinity/pic-js

Clarify logging when using Vitest test runner

Open
#50 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
10
Forks
13
Avg merge
4h 41m
Merged PRs (30d)
1

Description

Hi,

I followed the running-tests documentation and tried both options showCanisterLogs and showRuntimeLogs but, none of those allowed me to retrieve the ic_cdk::print I logged in my canister.

Therefore, I'm not sure if it's a potential issue or a feature. If the first, maybe I missed something (I'm using vitest), if the latest, it would maybe be nice to clarify that in the documentation.

Best

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the running-tests documentation and its descriptions of showCanisterLogs and showRuntimeLogs. Reproduce the Vitest case using a canister log from ic_cdk::print, then clarify in the documentation whether these options support retrieving that output and what users should expect.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation, testing
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.