Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need to follow the basics of testing. Unit Testing</p> <ul> <li>Positive test cases, simple test cases that get you started</li> <li>Negative test cases, add bad data that fails validations, and check if its been written</li> <li>Boundary (dont confuse it with negative), check for all limits, validations, 0, maxint, minint. For gps, check for +90 degrees, -90 degrees, -180 degrees... Basically testing is not as easy as you think. Doing it right is as/more painful than coding.</li> </ul> <p>All the above tests should focus on code COVERAGE (path coverage too, if you have the guts :)).</p> <p>And yes, you need to test for add, update, remove anomalies, from your system. Do this per table, per connection per relation.</p> <p>Scale-ability</p> <ul> <li>Each table, you need to add data from different clients, increase the number of clients until you break. IT MUST BREAK. That is what you can scale to max.</li> </ul> <p>Performance</p> <ul> <li>Is comparative in nature. You cannot test for performance by itself. It has to be between builds, between competitive product (exactly same data, exactly same hardware, exactly same scenario)</li> </ul> <p>Stress</p> <ul> <li>Add a lot of data from all sides, concurrently (dont use scale-ability max's here, the intent is "NOT" to break, but to find out if it can deal with a lot of data, users, concurrency.</li> </ul> <p>Reliability</p> <ul> <li>Here, use normal data, normal scenario that your customer is looking for. And run it over 48/72 hours. The gc's should bot go crazy, memory leaks should not keep growing, performance should be "consistent" (need not be the best). But should not "DROP" over time. Look for "things going bad with time".</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow do you test your software on possible sql server deadlocks before production?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSiddharth
    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. COActually i asked how to test my app for possible SQL DEADLOCKS...
      singulars
      1. PO
      1. USSergey Smelov
    2. COThese tests will uncover a lot more than just deadlocks.
      singulars
      1. PO
      1. USSiddharth
 

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