<p>Well, I'm not sure that "weirdness" is the most likely use-case for such tests, since weirdness usually means difficulty in reproducing the problem, which means its going to be difficult to write a test to reproduce it.</p>
<p>I'm not sure how the proposed test harness works, can it see what changes happen on the edit buffer?  Thats where most results appear.</p>
<p>As Geany recently had accessibility capabilities added, perhaps some of the testing mechanisms that use accessibility to read the screen may be appropriate, but AFAIK nobody has looked at doing it.</p>
<p>Note that very few plugins are part of Geany itself, most are third party maintained, see the Geany-Plugins repository and others are purely listed on the plugin website.  So its not really up to Geany itself to apply such testing.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/1462#issuecomment-292706733">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJw2yIOT8rdl_OcqsSjqYP-36y-Gzks5rt1StgaJpZM4M3o7W">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ3grBLZX2mEfPENoC_1hyzYTJ_moks5rt1StgaJpZM4M3o7W.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/issues/1462#issuecomment-292706733"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #1462: Well, I'm not sure that \"weirdness\" is the most likely use-case for such tests, since weirdness usually means difficulty in reproducing the problem, which means its going to be difficult to write a test to reproduce it.\r\n\r\nI'm not sure how the proposed test harness works, can it see what changes happen on the edit buffer?  Thats where most results appear.\r\n\r\nAs Geany recently had accessibility capabilities added, perhaps some of the testing mechanisms that use accessibility to read the screen may be appropriate, but AFAIK nobody has looked at doing it.\r\n\r\nNote that very few plugins are part of Geany itself, most are third party maintained, see the Geany-Plugins repository and others are purely listed on the plugin website.  So its not really up to Geany itself to apply such testing."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1462#issuecomment-292706733"}}}</script>