# No feedback on test

**URL:** <https://discuss.dev.twitch.com/t/no-feedback-on-test/20133>\
**Category:** Extensions\
**Created:** [February 21, 2019, 4:24am UTC](https://discuss.dev.twitch.com/t/no-feedback-on-test/20133 "2019-02-21T04:24:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [February 21, 2019, 9:53am UTC](https://discuss.dev.twitch.com/t/no-feedback-on-test/20133/2 "2019-02-21T09:53:04Z")

</div>

Console.log works fine for me here. I use it all the time in local development of an extension.

If you are running the rig

> **[End of support for the Twitch Developer Rig](https://discuss.dev.twitch.com/t/end-of-support-for-the-twitch-developer-rig/42995/)**
>
> In 2018, we introduced the Twitch Developer Rig with RFC0004 and launched the beta version in the same year. This native application provided an alternative approach for getting started with an Extension by providing templates, view testing,...

You an use

> window.Twitch.ext.rig.log(\<message to log\>)

as an alternative for console logging

Most issues can be checked with the chrome (or other) inspector to check for JS errors or network errors

---

_[View the full topic](https://discuss.dev.twitch.com/t/no-feedback-on-test/20133)._