apycot-moved #22707 Links to mercurial should link to log, not just single changeset [open]
When I on http://apycot.hg-scm.org/testexecution/98419 find a link to the mercurial revision at http://apycot.hg-scm.org/revision/98409 I would like to see which changesets were included in the test. A link to the single changeset (which often is a merge) is not very helpful. I would rather see a shortlog or a graph (ideally with all other "heads" pruned) | |
| priority | normal |
|---|---|
| type | enhancement |
| done in | <not specified> |
| closed by | <not specified> |
Comments
-
2010/05/11 07:36, written by sthenault
-
2010/05/11 08:04, written by mkiilerich
add commentwhat do you mean ? Short log of changesets which occured since the latest execution ?
A log of changesets since last (successful) test could probably be nice too - especially when working in "what introduced this failure" mode. That would however make the output stateful in a bad way; the test output would no longer be a pure function of the code base but depend on historic data.
My thoughts was however that a test execution doesn't test just a single changeset - it tests the sum of all changesets up to and including "the" changeset. Quickly browsing the 10-50 latest shortlogs often gives a good indication what changesets are incluced - much more than a single "merged with stable" message. That would for example answer questions like "I thought I fixed that failure - isn't m fix included?" or "I see that this test is failing ... could that perhaps be because the suspicious patch I saw on the mailing list the other day has been applied"?