Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>If there is any logic in there, it can be unit-tested.</strong><br> If your logic involves making decisions and calling OS/hardware/system APIs, fake/mock out the device dependent calls and unit test your logic to verify if the right decisions are made under a given set of pre-conditions. Follow the Arrange-Act-Assert triad in your unit test.<br> Assertions are no replacement for automated unit-tests. They dont tell you which scenario failed, they don't provide feedback during development, they can't be used to prove that all specs are being met by the code among other things.</p> <p><strong>Non-vague Update:</strong> I don't know the exact method calls.. I think I'll 'roll my own' Let's say your code examines current conditions, makes a decision and make calls to the OS as required. Lets say your OS calls are (you may have many more):</p> <pre><code>void* AllocateMemory(int size); bool FreeMemory(void* handle); int MemoryAvailable(); </code></pre> <p>First turn this into an interface, <code>I_OS_MemoryFacade</code>. Create an implementation of this interface to make the actual calls to the OS. Now make your code use this interface - you now have decoupled your code/logic from the device/OS. Next in your unit test, you use a mock framework (its purpose is to give you a mock implementation of a specified interface. You can then tell the mock framework that <strong>expect</strong> these calls to be made, with these params and return this when they are made. At the end of the test, you can ask the mock framework to verify if all the expectations were met. (e.g. In this test, AllocateMemory should be called thrice with 10, 30, 50 as params followed by 3 FreeMemory calls. Check if MemoryAvailable returns the initial value.)<br> Since your code depends on an interface, it doesn't know the difference between the real implementation and a fake/mock implementation that you use for testing. Google out 'mock frameworks' for more information on this.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow would you unittest a memory allocator?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGishu
    1. USGishu
    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. 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. COCould you please give more details on how to write the unit tests. You're advocating them plenty, but I read the question and then your answer and I still don't understand what exactly you're proposing.
      singulars
      1. PO
      1. USJason Dagit
    2. COYour answer is too abstract to be useful. Can you please give an example of how would you unit-test a memory allocator? Let's make it even more concrete: first-fit, which returns 50% of free blocks to the system when there is twice as much free than allocated memory.
      singulars
      1. PO
      1. USzvrba
    3. COStep one would be to have your memory allocator obtain and release memory from the system via an interface and not directly via direct system calls. Step two is to create a mock version of this interface that you can use in your tests. Step three is to test and check how the code uses the interface.
      singulars
      1. PO
      1. USLen Holgate
 

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