Note that we do not cover testing js here. That is covered in a later chapter.
This is for cases where we just want to give our code a "quick run check".
We'll take a look at doing a quick run check in a browser which might be done in parallel, or after the other editing/running techniques mentioned in this chapter.
On occasion, web browsers can be fussy (they have gotten better). If the browser is acting odd (e.g. not showing anything on console, etc) try to refresh. Also try "Clear Browsing Data". And then restart it.