Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm going to go with your second thought on this "Or is this the entirely wrong way to go about solving this problem".</p> <p>To solve this problem easily and not confuse your support department I would recommend creating a little command-line wrapper around the test class. You can write the command-line tool yourself, or if you prefer you can do the following:</p> <pre><code>using CSharpTest.Net.Commands; static void Main(string[] args) { MyTest testClass = new MyTest(); // optional: testClass.MySetupMethod(); new CommandInterpreter(testClass).Run(args); } </code></pre> <p>Just build the above code as a command-line exe in a new project referencing your test assembly and CSharpTest.Net.Libary.dll. The namespace <a href="http://code.google.com/p/csharptest-net/source/browse/#svn/trunk/src/Library/Commands" rel="nofollow noreferrer">CSharpTest.Net.Commands</a> is defined in the CSharpTest.Net.Libary.dll assemby <a href="http://code.google.com/p/csharptest-net/downloads/detail?name=CSharpTest.Net_35_v1.9.1004.144.zip&amp;can=2&amp;q=#makechanges" rel="nofollow noreferrer">from this download</a>.</p> <p>Essentially the above code will crawl your test class (named MyTest in the example above) and expose all the public methods as commands that can be executed via the command line. By default it provides help output and sets the Environment.ExitCode on failure. If you want to get fancy you can decorate your tests with any of the following:</p> <pre><code>public class MyTest { [System.ComponentModel.DisplayName("rename-this-function")] [System.ComponentModel.Description("Some description for tech-support")] [System.ComponentModel.Browsable(true | false)] public void TestSomeFunction() { ... } } </code></pre> <p><em>(And yes I acknowledge I am shamelessly plugging my own code a wee-bit :)</em></p>
    singulars
    1. This table or related slice is empty.
    1. POUnit Testing a Customer's Installation (with NUnit and MSTest)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UScsharptest.net
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUnit Testing a Customer's Installation (with NUnit and MSTest)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COInteresting. I've gone down this a bit since yesterday, whipping up a small console app that used reflection to call the test methods in my class, but ran into problems with TestContext and the class initialization methods. Looks like you build your initializers yourself per test run?
      singulars
      1. PO
      1. USCase
    2. COAhh, no I forgot about MsTest's weird initialization dependencies. I think they did it intentionally to force you to keep using MsTest :) Anyway, can you break your dependencies on the MsTest specific stuff? If not, I would have to retract my original recommendation and suggest you write a command-line utility apart from the tests. Just keep it automated in the build in parallel with the tests to ensure it continues to work.
      singulars
      1. PO
      1. UScsharptest.net
    3. COThis is the closest answer to what I ended up going with - which was just another version of my code that ran on NUnit with a subset of the tests.
      singulars
      1. PO
      1. USCase
 

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