Tips for getting Sandbox Output
Troubleshoot missing sandbox output during tests and learn how to generate debug output by using the target application (login, submit forms, etc.).
Sandbox Output
Sometimes you may need extra guidance while working through a lesson—especially in Break/Fix lessons. In these cases, you can add print/debug statements to your code to generate output in the Sandbox Output panel.
You can find lesson-specific debugging tips in the lesson itself:
Language Selector → Info
Important Notes
-
You must interact with the target application to trigger output.
The required interaction depends on the lesson instructions (for example: log in, add a post, submit a form, etc.). - Example: If you added print/debug statements to the login authentication code, you’ll need to attempt a login in the web app to generate output and see it in the Sandbox Output panel.
-
Do not use the browser’s Developer Console for debug output.
The sandbox environment is meant to function like your development terminal/console, and your print statements should appear in the Sandbox Output panel instead.
Additional Considerations
We don’t show debug output during tests because it could reveal the test data. That would make it easy for learners to code specifically to the test results instead of building a solution that works generally.