StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20206933
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-26T01:29:14.017
FavoriteCount
0
LastActivityDate
2013-11-26T01:29:14.017
LastEditDate
LastEditorUserId
0
OwnerUserId
279936
ParentId
20156934
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
In a related <a href="https://github.com/sbt/sbt/issues/1001" rel="nofollow">github issue discussion</a>, Josh suggested an approach to the particular case I asked about (overriding it:test with a task that calls the original test task). The approach works by reimplementing the test task. I don't know if there's a more general way to get access to the original version of the task. (A more general way would be a better answer than this one!) Here's how to reimplement the it:test task: <pre><code> /** run integration tests (just like it:test does, but explicitly so we can overwrite the it:test key */ lazy val itTestTask: Initialize[Task[Unit]] = Def.taskDyn { for { results <- (executeTests in IntegrationTest) } yield { Tests.showResults(streams.value.log, results, "test missing?") } } </code></pre> Here's the composite integration test task (evolved slighly from the original question, though that version should work too): <pre><code> /** run integration tests against a test server. (the server is started before the tests and stopped after the tests) */ lazy val testWithServiceTask = Def.taskDyn { (start in testService).value match { case Success(_) => testAndStop case Failure(e) => val stack = e.getStackTrace().mkString("\n") streams.value.log.error(s"failed to start test server: $e \n ${stack}") emptyTask } } /** run integration tests and then stop the test server */ lazy val testAndStop = Def.taskDyn { SbtUtil.sequence(itTestTask, stop in testService) } val emptyTask = Def.task {} </code></pre> And now plugging the composite task we've built into the it:test key doesn't create a cycle: <pre><code> lazy val mohs = Project(id = "mohs", base = file(".")) .settings ( test in IntegrationTest <<= testWithServiceTask, ) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSBT: how to modify it:test with a task that calls the original test task?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLee Mighdoll
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
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.