Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are four possible problems here;</p> <p><strong>The namespaces in your code are dividing your classes too finely.</strong> if you have, for example;</p> <pre><code>using MyCompany.Drawing.Vector.Points; using MyCompany.Drawing.Vector.Shapes; using MyCompany.Drawing.Vector.Transformations; </code></pre> <p>consider collapsing them to the single <code>MyCompany.Drawing.Vector</code> namespace. You probably aren't gaining by dividing too much. Visual Studio Code Analysis/FxCop has a rule for this, checking the number of classes in a namespace. Too few and it will warn you.</p> <p><strong>You are putting too many tests into the same class.</strong> If you are referencing <code>System.Data</code>, <code>System.Drawing</code>, and <code>System.IO</code> in the same class, consider writing more atomic tests -- some which access databases, some which draw images, and some which access the file system. Then divide each type across three test classes.</p> <p><strong>You are writing tests which do too much.</strong> If you are referencing a lot of namespaces, your tests may be coupling too many features together. This kind of coupling can often be buggy, so try to break big, wide-ranging functions into smaller parts, and test these in seperate files. </p> <p><strong>Many are redundant.</strong> Are they all used, or are they just copy-pasted from other files. Right-click on the code editor and choose from the 'Organise Using' options to remove unused statements.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload