Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>MSTest is certainly not as efficient or extensible as some of the open source frameworks, but it is workable. Since the question asks about making life easier with MSTest and not about alternatives, here are my MSTest tips.</p> <ul> <li><strong>Shortcuts</strong>. Like Haacked said, take a few seconds to learn the shortcuts.</li> <li><strong>Current Context</strong>. Since MSTest is so slow, run tests only in the current context when you can. (<strong><kbd>CTRL</kbd>+<kbd>R</kbd></strong>, <strong><kbd>CTRL</kbd>+<kbd>T</kbd></strong>). If your cursor is in a test method, this will only run the method. If your cursor is outside a method, but in a test class, this will only run the test. And with namespace, etc etc</li> <li><strong>Efficient tests and organization</strong>. It's dog slow. Make things as best as you can by writing efficient tests. Move slow tests to other test classes or projects so you can run the fast tests more frequently.</li> <li><strong>Testing with WCF</strong>. If you're testing services, be sure to DEBUG tests rather than RUN tests so Visual Studio can fire up the ASP.NET development web servers. After these are up, then you can go back to RUN, but it can be easier to just always DEBUG so you don't have to think about it.</li> <li><strong>Config Files</strong>. Edit your test-run configuration to move .config files into the test execution folder.</li> <li><strong>Integration with Source Safe</strong>. You need to be aware that MSTest hates SourceSafe and the feeling is mutual. Because MSTest wants to put test files under source control, and add them to the solution, it must check out the solution every time you run tests. So SourceSafe must be running in multi-check-out mode to avoid killing your fellow developers.</li> <li><strong>Ignore the fluff</strong> With MSTest, you get a dozen different windows and views. Test Runs, Test View, Test Lists ... they're all less-than-helpful. Stick with Test Results and you'll be much happier. </li> <li><strong>Stick with "Unit Tests"</strong>. When you add a new test, you can add an ordered test, a unit test, or run through a wizard. Stick with just plain simple unit tests.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow to Ease TDD with MSTest / VS2008
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USvahid abdi
    1. USBrad Tutterow
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to Ease TDD with MSTest / VS2008
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou must be kidding. The CTRL+R, T Command starts MSTest in Visual Studio 2008 10 times faster!! If I use R# it takes like 10 seconds, with the shorthand 1 second to start. LOVE IT! Thanks!
      singulars
      1. PO
      1. USbastianwegge
 

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