Feature #3030
Testing framework can send bug report to mailinglist
| Status: | Resolved | Start date: | 2009-04-03 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Error | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 5 | |||
| PHP Version: | Complexity: | |||
| Has patch: | ||||
| Votes: | 0 |
Description
After the test suites are completed and a test failed, ask the Developer if a detailed bug report should be send to the TYPO3 Mailinglist. Of course only if a failed test belongs a to a public package. If you have ever compiled php and did a make test you might actually know what i mean.
This behaviour could also expanded when an exception was thrown.
Associated revisions
[~TASK] FLOW3 (Error): the DebugExceptionHandler now shows a link to Forge for creating an issue - we'll see how that turns out... Resolves #3030.
History
Updated by Robert Lemke about 4 years ago
- Target version set to 283
Updated by Robert Lemke almost 4 years ago
- Target version deleted (
283)
Updated by Karsten Dambekalns over 3 years ago
For the testing framework I would not do this. Tests in that part should fail on the developer's machine or the CI server. Thus we don't need any mails to bother innocent developers :)
For the exception handling, I partly agree. But I would not send an email but rather link to a form for a new issue on forge with some stuff pre-filled in the form. This is easily done:
http://forge.typo3.org/projects/package-<key>/issues/new?issue[subject]=Foo&issue[description]=Bar+Baz&issue[category_id]=76
Updated by Karsten Dambekalns over 3 years ago
- Status changed from New to Accepted
- Assignee set to Karsten Dambekalns
- Target version set to 1.0 alpha 5
Updated by Karsten Dambekalns over 3 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r3233.