Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Modify the subject <a href="http://xunitpatterns.com/SUT.html" rel="noreferrer">under test (SUT)</a>. If something is hard to unit test, then the design might be awkward.</p> <p>Faking method calls within the class under test leads to over specified tests. The result are very brittle tests: As soon as you modify or refactor the class, then it is very likely that you also need modify the unit tests. This leads too high maintenance costs of unit testing.</p> <p>To avoid over specified tests, concentrate on public methods. If this method calls other methods within the class, do not test these calls. On the other hand: Method calls on other <a href="http://xunitpatterns.com/DOC.html" rel="noreferrer">dependend on component (DOCs)</a> should be tested.</p> <p>If you stick to that and have the feeling that you miss some important thing in your tests, then it might be a sign for a class or a method which is doing too much. In case of a class: Look for violations of the <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle" rel="noreferrer">Single Responsibility Principle (SRP)</a>. Extract classes out of it and test them separately. In case of a method: Split it up the method in several public methods and test each of them separately. If this is still too awkward, you definitely have a class which violates the SRP.</p> <p>In your specific case you can do the following: Extract the methods <code>ExportExcelDocToDataSet</code> and <code>GetDataTableFromExcelSheet</code> into two different classes (maybe call them <code>ExcelToDataSetExporter</code> and <code>ExcelSheetToDataTableExporter</code>). The original class which contained both methods should reference both classes and call those methods, which you previously extracted. Now you are able to test all three classes in isolation. Apply the <a href="http://martinfowler.com/refactoring/catalog/extractClass.html" rel="noreferrer">Extract Class refactoring</a> (<a href="http://rads.stackoverflow.com/amzn/click/0201485672" rel="noreferrer">book</a>) to achieve the modification of your original class.</p> <p>Also note that retrofitting tests are always a bit cumbersome to write and maintain. The reason is that the SUTs, which are written without unit tests, tend to have an awkward design and thus are harder to test. This means that the problems with unit tests must be solved by modifying the SUTs and cannot be solved by pimping up the unit tests.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I test a method was called within a class under test?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTheo Lenndorff
    1. USTheo Lenndorff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I test a method was called within a class under test?
      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. VTAcceptedByOriginator
    1. COI had thought of extracting the methods you mentioned into separate classes so I could unit test them using the AssertWasCalled extension, but I wasn't sure if this was a great idea because I could see that leading to a ton of very shallow classes with one or two methods in them at most. I will definitely check out the book you recommended and also more about the SRP. The best thing about all of this is I'm the only person on the project and all the code has been written by me, so I can do whatever I need to make it work out.
      singulars
      1. PO
      1. USGage Trader
    2. CO@Gage Trader: Do not measure a class in terms of numbers of methods. For example the Command Pattern exposes only one method and still is a widley used technique. Before I applied unit testing and good OO design principles, I was not comfortable with the higher number of classes. I took me some time to realize that a higher number of classes does not mean more work. Yes, it is true that you need more time for design and testing, but the higher quality and the lower bug count compensates this by far.
      singulars
      1. PO
      1. USTheo Lenndorff
 

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