Details
Improvement
Resolved
Major
Description
Moving stories view generation concern to the embedder would allow the view to be generated after the stories are run (each with their single story report generation). We can then avoid the two-phase process currently in 2.x and have it all performed in a single execution via Maven or Ant. The embedder is also aware of the configuration used to generate the reports, so we can reduce need/risk of configuration mismatch.
The view generation should be on by default, but with ability to disable via a runtime flag.
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Mauro Talevi [ maurotalevi ] |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Mauro Talevi
made changes -
| Description |
If report rendering were the concern of the story embedder, it would allow the rendering to be performed after the story running (and their raw report generation). We can then avoid the two-phase process currently in 2.x and have it all performed in a single execution via Maven or Ant. The embedder is aware of the configuration use to generate the reports, so it also reduces need/risk of configuration mismatch between generation and rendering.
The rendering should probably be on by default, but with configurable to switch off. |
If report rendering were the concern of the story embedder, it would allow the rendering to be performed after the story running (and their raw report generation). We can then avoid the two-phase process currently in 2.x and have it all performed in a single execution via Maven or Ant. The embedder is aware of the configuration used to generate the reports, so we can reduce need/risk of configuration mismatch between report generation and rendering.
The rendering should be on by default, but with ability to disable via a runtime flag. |
Mauro Talevi
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Mauro Talevi
made changes -
| Summary | Allow story embedder to render reports | Allow embedder to generate stories view after running them |
| Description |
If report rendering were the concern of the story embedder, it would allow the rendering to be performed after the story running (and their raw report generation). We can then avoid the two-phase process currently in 2.x and have it all performed in a single execution via Maven or Ant. The embedder is aware of the configuration used to generate the reports, so we can reduce need/risk of configuration mismatch between report generation and rendering.
The rendering should be on by default, but with ability to disable via a runtime flag. |
Moving stories view generation concern to the embedder would allow the view to be generated after the stories are run (each with their single story report generation). We can then avoid the two-phase process currently in 2.x and have it all performed in a single execution via Maven or Ant. The embedder is also aware of the configuration used to generate the reports, so we can reduce need/risk of configuration mismatch.
The view generation should be on by default, but with ability to disable via a runtime flag. |
Added renderReportsAfterStories=[true|false] flag (defaulting to true) to Ant/Maven run stories entry points.