As I’m writing more and more Motoko, it would be nice to have a playground to quickly test code. The quickest way I’ve found to test a function is to run this after each modification: dfx deploy && dfx canister call my_can myFunc Even with minimal code, this takes roughly 30 seconds before the out…

If you’ve only made changes to a single canister you can run: dfx build my_can && dfx canister install my_can -m upgrade && dfx canister call my_can myFunc You can check the options for any of these commands with the --help flag too, eg: dfx canister install --help

This might help: [image] Motoko documentation with live edits Developers The Motoko documentation has been updated to support live edits of code examples: You can edit the code in the language guide and see the result in the browser. Check it out!

We are going to release a web-based playground for Motoko to allow you deploy canisters online soon :slight_smile: The live edits in the SDK website is a lightweight version of the playground, if you want to explore small Motoko code snippets.

Excellent Something like Remix would reach Solidity devs; https://remix.ethereum.org/

@Ori For some reason, when I try to build just the one canister I’m working on, it fails with import error, canister alias "credits" not defined even though I do have a canister named credits in the project that can be built successfully with dfx build credits Everything builds and runs successf…

Have you tried running dfx deploy once first, then using the commands I suggested for any further single canister changes?

Yup. The first command, dfx build serve fails, complaining that credits is not found. serve is one canister that imports the credits canister which is in the same project and both exist in the canister_ids.json file: "credits": { "local": "rwlgt-iiaaa-aaaaa-aaaaa-ca }, "serve": { "local": "ryjl…

Ah, you’ll need to add the credits canister as a dependency of the serve canister in your dfx.json, like this: "serve": { "main": "src/serve/main.mo", "type": "motoko", "dependencies": [ "credits" ] }, Then the above steps should work, so… First run only: dfx deploy Subs…

Oh interesting. Odd that the deploy command works without the dependency, but the build command doesn’t. I thought deploy just used build under the hood. Something else is going on?

dfx deploy will be doing the same as dfx build --all, which will work too, but to build an individual canister it needs the dependencies listed.

Development workflow: quickly test code modifications

Developers

enzo January 13, 2021, 8:11pm 3

This might help:

4 Likes

Topic		Replies	Views
Is there a way to test without needing to run dfx deploy all of the time? Developers	8	482	October 25, 2023
Dfx 0.26.0 Release Command Line Tools dfx	37	848	May 16, 2025
Creating a web canister Developers	33	1537	June 20, 2023
Motoko codes are not updating with dfx deploy Motoko	4	179	May 13, 2024
Developer Liftoff: Feedback and discussion Education dev , developer-liftoff	90	3922	March 3, 2025

Development workflow: quickly test code modifications

Related topics