StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10645595
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-18T01:26:02.773
FavoriteCount
0
LastActivityDate
2012-06-15T13:54:55.953
LastEditDate
2012-06-15T13:54:55.953
LastEditorUserId
717274
OwnerUserId
717274
ParentId
10525267
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
In my experience, any test toolkit you use is either going to work itself into your code in subtle ways, or never get to the depth you need (or both). It's possible to write custom test code and still keep the code clean for the app being tested. I did it on a large Windows C++ gui app that I needed to autotest. The basic idea is to create a new project, reference all the code from your base project, and write a new set of classes that derive from the base classes and that contain your testing code. In my case, I created a new Visual Studio project, but you can do the same with a new Qt project. The base classes may have to be refactored to expose the functions to be tested, of course. The test classes call the base class functions as needed - you can create an entire test gui if you want. As a very simple example, if this is your project... <pre><code>class MyView : public QMainWindow {} class MyController {} class MyModel {} </code></pre> ...create a new project, pull in your base code, and add these: <pre><code>class TestView : public MyView {} class TestController : public MyController {} class TestModel : public MyModel {} </code></pre> In the end, after a little work, zero test code was in my base classes, and I was still able to tie in and fire off all kinds of repetitive autotests in a nice test gui. I'm not saying this is an easy or trivial task. I'm just encouraging you that it can be done. :-) EDIT: This is not a criticism of embedded unit testing, which is great if you can get it in place from the start of your project. But this was a large legacy app and it was a hard requirement that I didn't inject test code into the base code.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODo Gui testing in Qt
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmoodboom
UserOwnerUserId
1. USmoodboom
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.