StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19686592
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-30T15:12:53.400
FavoriteCount
0
LastActivityDate
2015-08-18T14:44:32.760
LastEditDate
2015-08-18T14:44:32.760
LastEditorUserId
300053
OwnerUserId
300053
ParentId
6715281
PostTypeId
2
Score
32
ViewCount
0
LastEditorDisplayName
text
Body
The JUnit way to compose reusable code (instead of inheriting from it) are Rules. See <a href="https://github.com/junit-team/junit/wiki/Rules" rel="noreferrer">https://github.com/junit-team/junit/wiki/Rules</a> Here is a dumb sample, but you'll get the point. <pre><code>import org.junit.rules.TestRule; import org.junit.runners.model.Statement; import org.junit.runner.Description; public class MyTestRule implements TestRule { @Override public Statement apply(final Statement statement, Description description) { return new Statement() { public void evaluate() throws Throwable { // Here is BEFORE_CODE try { statement.evaluate(); } finally { // Here is AFTER_CODE } } }; } } </code></pre> You can then use your TestRule like this: <pre><code>import org.junit.Rule; public class MyTest { @Rule public MyTestRule myRule = new MyTestRule(); } </code></pre> BEFORE_CODE and AFTER_CODE will then be executed around each of your test methods. If you need to run your code only once per class, use your TestRule as a @ClassRule: <pre><code>import org.junit.ClassRule; public class MyTest { @ClassRule public static MyTestRule myRule = new MyTestRule(); } </code></pre> Now, <code>BEFORE_CODE</code> and <code>AFTER_CODE</code> will be executed around each of your test class. <a href="http://junit.org/javadoc/latest/org/junit/Rule.html" rel="noreferrer">@Rule</a> field is not static, <a href="http://junit.org/javadoc/latest/org/junit/ClassRule.html" rel="noreferrer">@ClassRule</a> field is. A @ClassRule can be declared in a Suite too. Note that you can declare several rules in a single test class, that's how you compose test lifecycles at test-suites, test-classes and test-methods levels. A Rule is an object that you instanciate in your test classes (statically or not). You can add contructor parameters if needed. HTH
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to avoid inheritance in JUnit test cases?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USeskatos
UserOwnerUserId
1. USeskatos
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to avoid inheritance in JUnit test cases?
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
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.