08/19/2021
5 mins - Importance of debugging
Leading with: Big Overal Example
specific example
10 mins - Lesson/Demo
Jr Dev: Print or alert yourself to any variables
Mid/Sr Dev: uses log statements or breakpoints with, they will build testing into the code, hooking into a software dev lifecycle, keep an eye on your logs to see if something is wrong
4 steps:
add breakpoints
start debugging
run application
debug code
Show: Adding breakpoints in the debugger LINK
showing the actual debugging in the IDE, but also time it
5 mins - Recap
Wrong Variables, space explosion LINK
what you just learned in OS IDE summary
Common Qs
In OutSystems, where can we place breakpoints?
In OutSystems, it is possible to inspect the values of variables while debugging?
Can I debug natively in the mobile app?
CTA: Enjoyed this lesson? More Decoded lessons in your pocket for podcast
Additional notes LINK
Titles:
Ease and importance of debugging
Fear the fatalities of not debugging
Catching bugs with PKMN Trainer Syd
double-check my title "How to debug before I ragequit"
Agenda
https://www.outsystems.com/nextstep/osdc/agenda-americas/
tell Rui if I want an updated descritpion
Breakpoints are placed where code execution will be suspended later on.
To add breakpoints in logic-flows, right click on a break point to add an element, SS then registers the breakpoints and lists them in the debugger panel. Then while debugging the app, whenever the execution goes through the piece of code w/ an active breakpoint, the execution will automatically stop.
Breakpoints can be disabled and removed at any time
Now that the breakpoints defined, it’s time to start the debugger
Whenever the execution reaches a breakpoint, it’s suspended
This allows you to execute the code step by step
In this process, it is easy to see what is happening with the code
Since it is possible to analyze the value of variables and understand when the app is not behaving as it’s expected
When teh execution stops w/in the breakpoint, the focus returns back to service studio
Step Over
Step Into
Step Out
When the execution stops in the Break Point, the focus goes back to SS
So in SS, we can find the regular debugging operations, the options step over, step into, and step out allow the step by step execution of the code to help the dev analyze its behavior
There’s also options to stop the debugger and stop, continue, suspend or abort
Break on All Execptions - to suspend the execution of hte app, whenever an exception is raised