c# - Should I avoid hitting the database on tests as a shortcut to fill object with valid data? -


i have test suite works against dedicated copy of real database. application creates complex object filling database , lot of work create 1 "manually" or mocking 1 bring valid state. ran database query tests in order have valid object (not verify integrate database correctly). working blazing fast. after first call mssql caching , query ran in less 1 ms.

are there arguments why should avoid doing this? if it's because speed when database on same network it's working fast? seems literature out there wouldn't recommend doing - why?

edit - answer own question: "unit tests" means each test autonomous, if touch database 1 test modify , affect test. though transactions can solve it, it's still not quite in "spirit" of "unit tests" , make them bit cumbersome. should avoided not under circumstances, if have no choice i'll access database in transaction make sure won't affect other tests.

this seems principle people follow - should never hit database - experience sometimes, trying hard avoid database creates these giant tests, over-use of mocks, or strange , brittle data access interface. search test-induced design damage more on idea.

for part, i'm happy access database part of tests. can write tests if can wrap whole test in transaction, too.


-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more