Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The only reason you have the parent class is to create instances of your interface, yes?</p> <p>Use <a href="http://code.google.com/p/moq/" rel="nofollow noreferrer">MOQ</a> instead. </p> <p><strong>Edit:</strong> </p> <blockquote> <p><em>Not quite. The ISomeInterfaceTests&lt;T&gt; class is used to test the functionality of the proxies implementing the ISomeInterface&lt;T&gt; interface - it tests the proxies against the objects they are a proxy for (the oracle).</em> – Cornelius </p> </blockquote> <p>Hmm... that sounds like an integration test. Are your oracle objects read from the database somehow, or are you mocking them like you should be? Anyway, I stand by using Moq to get your instances and mocking vs integration testing in general. </p> <p>But it strikes me that your approach for generalization of your tests may be the issue. Perhaps a different approach? Try this on:</p> <pre><code>public static class GenericISomeInterfaceTests { public static void SomePropertyTest&lt;T&gt;(ISomeInterface&lt;T&gt; target, ISomeInterface&lt;T&gt; oracle) { Assert.AreEqual(oracle.SomeProperty, target.SomeProperty); } public static void SomeActionTest&lt;T&gt;(ISomeInterface&lt;T&gt; target, ISomeInterface&lt;T&gt; oracle) { T oracleValue = oracle.SomeAction(); T targetValue = target.SomeAction(); Assert.AreEqual(oracleValue, targetValue); } // More tests } [TestClass()] public class ClassAProxyTests { [TestMethod] public void SomePropertyStringTest() { // set up instances (using MOQ, or whatever) with the string generic type. // Call them target and oracle // then call your generic test methods GenericISomeInterfaceTests.SomePropertyTest&lt;string&gt;(target, oracle); } [TestMethod] public void SomeActionStringTest() { // set up instances (using MOQ, or whatever) with the string generic type. // Call them target and oracle // then call your generic test methods GenericISomeInterfaceTests.SomeActionTest&lt;string&gt;(target, oracle); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUnit tests that inherit from a type that uses generics
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRandolpho
    1. USRandolpho
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CONot quite. The ISomeInterfaceTests&lt;T&gt; class is used to test the functionality of the proxies implementing the ISomeInterface&lt;T&gt; interface - it tests the proxies against the objects they are a proxy for (the oracle).
      singulars
      1. PO
      1. USCornelius
    2. COThe oracle is a mockup object and does no database work. The approach you suggested will still require that the test methods be implemented for all the different proxy tests. Thus ClassBProxyTests and ClassCProxyTests will have to explicitly state all the test methods and the associated attributes (TestMethod, ExpectedException) as well. Granted it would only have a call to a GenericISomeInterfaceTests (which is much better than reimplementing the test each time) but a solution where it would not be needed to do that would be preferable.
      singulars
      1. PO
      1. USCornelius
    3. COI don't think such a solution will exist. You'll need TestMethod on all of your test methods, period.
      singulars
      1. PO
      1. USRandolpho
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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