# Reduced Test Cases

> FullCalendar v4 documentation, for an old release. Web version: https://legacy.fullcalendar.io/v4/reduced-test-cases
>
> Latest version (v7): https://fullcalendar.io/reduced-test-cases

<h2>Step 1: Isolate the bug on your end</h2>

<p>
  More often than not, the problem is with your code, not with FullCalendar. To determine this,
  remove as much of your code as possible:
</p>

<ul>
  <li>Remove all unrelated stylesheets and JS files</li>
  <li>Remove all unrelated 3rd party libraries</li>
  <li>Remove all server-side logic. Use static HTML and JSON files instead.</li>
</ul>

<p>
  For more info on this technique, read
  <a href='https://css-tricks.com/reduced-test-cases/'>Reduced Test Cases</a>.
</p>

<h2>Step 2: Post a public demonstration of the bug</h2>

<p>
  Use a service like <a href='https://codepen.io/'>CodePen</a> or
  <a href='https://jsfiddle.net/'>JSFiddle</a> to demonstrate the bug online. Enter your JS, CSS,
  HTML, and JSON and wire up all the relevant dependencies. To help you get started, here are some
  <strong>debugging templates for FullCalendar v4:</strong>
</p>

<ul>
  
    <li>
      <a href='https://legacy.fullcalendar.io/v4/initialize-globals-demo' data-codepen='/v4/initialize-globals-demo'>Standard</a>
      
        (<a href='https://legacy.fullcalendar.io/v4/debug-json-feed' data-codepen='/v4/debug-json-feed'>with JSON feed</a>)
      
    </li>
  
    <li>
      <a href='https://legacy.fullcalendar.io/v4/debug-scheduler' data-codepen='/v4/debug-scheduler'>Premium plugins</a>
      
        (<a href='https://legacy.fullcalendar.io/v4/debug-scheduler-json-feed' data-codepen='/v4/debug-scheduler-json-feed'>with JSON feed</a>)
      
    </li>
  

  
</ul>