# "No setting named \_\_ exists" when trying to run specs on poll plugin

**URL:** https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751
**Category:** Support
**Created:** [August 8, 2021, 11:36pm UTC](https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751 "2021-08-08T23:36:39Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![frank.manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frank.manuel/32/203348_2.png) [@frank.manuel](https://meta.discourse.org/u/frank.manuel)
#### Post date: [August 10, 2021, 10:05am UTC](https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751/3 "2021-08-10T10:05:19Z")

</div>

Thanks. Like you said, it did run all the plugin specs, which I worked around by removing the other plugins. I was basing off of [this](https://meta.discourse.org/t/how-do-i-run-only-discourse-plugins-poll-spec/47244/8), but it turns out the parentheses were in the wrong spot.

Yes, the database is migrated in the test environment. I worked around this error by commenting out the `raise ArgumentError.new("No setting named '#{name}' exists")` line and replacing it with a `puts`, and it shows only `discourse_narrative_bot_enabled` triggers this error; all other settings are fine. I don’t think we did anything with this setting. Anyway, since my spec run properly while ignoring this error, I can leave the workaround in my local discourse. When I find what actually caused this, I’ll update this post.

---

_[View the full topic](https://meta.discourse.org/t/no-setting-named-exists-when-trying-to-run-specs-on-poll-plugin/199751)._