{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/64839a8f075a41cabf105d671cc48a07\" frameborder=\"0\" width=\"1664\" height=\"1248\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1248,"width":1664,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1248,"thumbnail_width":1664,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/64839a8f075a41cabf105d671cc48a07-00001.gif","duration":107.46666666666664,"title":"Adding Console Logs in a Should Statement 👀","description":"Hey there! In this Loom, I want to show you how adding console logs in a should statement can be really helpful. Most of the time, adding print statements in the spec doesn't really buy you much because it's at the very beginning of the test. However, in a should statement, it's really nice to add console logs because you are actually inside the application code. I'll show you how to grab the context and paste it into the terminal to get the full state at that point in time. Everything from autocomplete to console eval is right there! I'll even add a print statement and run the same thing. You can try it too!"}