Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm going to <em>assume</em> by testing the back end you are referring to the bit of code that actually talks to the Email server and to test the rest of your software you have <a href="http://en.wikipedia.org/wiki/Mock_object" rel="nofollow noreferrer">mocked</a> this layer.</p> <p>Now this may or may not be integration tests depending on your definition unit. Frankly I don't care what you decide to call it but if you write some automated tests that are quick to run and are executed often then they might as well use the same platform as your unit tests.</p> <p>I'd try to write this so it can work in at lest the following two ways - The first would be that it connects to an process-local email server that you can set up and configure as you need. In Java I use <a href="http://quintanasoft.com/dumbster/" rel="nofollow noreferrer">Dumpster</a> but I'm sure alikes exist for C++. The second would be to connect to at least one local email server that you can script. One that you can splatter as much as you like (so NOT real or shared between developers¹) and run the same set of tests against that. The reason being that the developers of SMTP servers hate everyone and you will want to check that your stub works the same as a real thing. This I see as the equivalent to <a href="http://dbunit.wikidot.com/onedatabaseperdeveloper" rel="nofollow noreferrer">One Database Per Developer</a>.</p> <p>Now if you have not written your own SMTP client and just have a <a href="http://en.wikipedia.org/wiki/Facade_pattern" rel="nofollow noreferrer">facade</a> around an existing 3rd party API I less likely to "integration test" this on the assumption that the 3rd party API has been battered enough that bugs have already fallen out. I would look at mocking the 3rd party API and validating that the facade works as expected.</p> <p>1) Maybe you could do this just during the CI cycle, so then share one set of email servers between all developers and the local run just uses a C++ Dumpster alike.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to unit test an email client
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMichael Lloyd Lee mlk
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to unit test an email client
      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
    1. CODo you know of a way to mock a C API? That is the problem I am seeing: it seems straightforward if it was a C++ library. Another consideration is that I'm not 100% sure what I should be getting back from the 3rd party API, since a lot of this is new to me, so I'm more inclined to go with setting up a test email server than mocking the API's results.
      singulars
      1. PO
      1. USMatt Moriarity
    2. COI did not see this requirement until after I posted the above. I don't really do much C/C++ development but http://www.lastcraft.com/cgreen.php looks promising. The other option would be to create a thin wrapper around it (basically a mockable interface with every method declared and then a real call the just deligates.)
      singulars
      1. PO
      1. USMichael Lloyd Lee mlk
    3. COBut if mocking the C API is completely out of the question, stub the SMTP server (as described above using something like Dumpster if you can).
      singulars
      1. PO
      1. USMichael Lloyd Lee mlk
 

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