<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Testing on Ilscipio - Enterprise Commerce Experts</title>
    <link>https://www.ilscipio.com/en/tags/testing/</link>
    <description>Recent content in Testing on Ilscipio - Enterprise Commerce Experts</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.ilscipio.com/en/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Test a JetBrains Plugin Across Six IDE Versions</title>
      <link>https://www.ilscipio.com/en/blog/test-jetbrains-plugin-six-versions/</link>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.ilscipio.com/en/blog/test-jetbrains-plugin-six-versions/</guid>
      <description>&lt;p&gt;JetBrains ships three major releases a year, and each version can break plugin APIs. I maintain 22 plugins. That means roughly 132 version combinations to keep working. Most of this is automated, but the automation took a while to build.&lt;/p&gt;&#xA;&lt;h2 id=&#34;compatibility-ranges&#34;&gt;Compatibility ranges&lt;/h2&gt;&lt;p&gt;Every JetBrains plugin declares a version range in &lt;code&gt;plugin.xml&lt;/code&gt; - the oldest and newest IDE version it supports. I target six versions back from the current release. That covers developers who update immediately and developers who stay on last year&amp;rsquo;s IDE because their company locks the version.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
