Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Does it matter how large my test class becomes? (i.e. thousands of tests?)</p> </blockquote> <p>Yes it does. Tests need to be maintained in the long term, and a huge test class is difficult to understand and maintain.</p> <blockquote> <p>When is it time to refactor my functionality classes? (25 or 50 methods, 1000 lines of code, etc)</p> </blockquote> <p>When you start to feel it is awkward to find a specific test case, or to browse through the tests related to a specific scenario. I don't think there is a hard limit here, just as there is no hard limit for the size of production classes or the number of methods. I personally put the limits higher for test code than for production code, because test code tends to be simpler, so the threshold where it starts to become difficult to understand is higher. But in general, a 1000 line test class with 50 test methods starts to feel too big for me.</p> <p>I just recently had to work with such a test class, and I ended up partitioning it, so now I have several test classes each testing one particular method / use case of a specific class*. Some of the old tests I managed to convert into parameterized tests, and all new tests are written as paramterized tests. I found that parameterized tests make it much easier to look through the big picture, and keep all test cases in mind at once. I did this using JUnit on a Java project, but I see NUnit 2.5 now offers parameterized tests too - you should check it out.</p> <p>*You may rightly ask shouldn't the class under test be refactored if we need so many test cases to cover it - yes it should, eventually. It is the largest class in our legacy app, with way too much stuff in it. But first we need to have the test cases in place :-) Btw this may apply to your class too - if you need so many test cases to cover it, it might be that the class under test is just trying to do too much, and you would be better off extracting some of its functionality into a separate class, with its own unit tests.</p>
    singulars
    1. This table or related slice is empty.
    1. POTesting Classes - When to refactor?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPéter Török
    1. USPéter Török
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTesting Classes - When to refactor?
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI actually didn't know what parameterized tests were and upon reading a definition I realized I had already done this with my test classes which is why I have a seperate class for tests that calls them.
      singulars
      1. PO
      1. USFooBar
    2. COThe test classes test the functionality of a website which is why they are growing, I will take your advice and refactor them as they grow.
      singulars
      1. PO
      1. USFooBar
 

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