<Freddy Mallet> I mean creating a measure is a good way to access the resource through a drilldown and the measure could be ... "number of profiled unit tests". So this measure will be displayed in the project dashboard and if the user click on it, all unit test (resource) with profiling information will appear.
<Evgeny Mandrikov> Yes - it's very good idea. But I decided to call it "number of profiled tests", because we also need profiling for integration-tests.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||PROFILER-0.1 [ 16310 ]|
|Assignee||Evgeny Mandrikov [ godin ]|
|Project Import||Wed May 27 15:34:50 CEST 2015 [ 1432733690440 ]|
|Project Import||Wed Jun 03 10:43:16 UTC 2015 [ 1433328196345 ]|
|Workflow||jira [ 37004 ]||Default SonarSource Workflow [ 58844 ]|
|Workflow||Default SonarSource Workflow [ 58844 ]||Default Agile SonarSource Workflow [ 78709 ]|
|Workflow||Default Agile SonarSource Workflow [ 78709 ]||Default Agile SonarSource Workflow V2 [ 107491 ]|
|Workflow||Default Agile SonarSource Workflow V2 [ 107491 ]||Default Agile SonarSource Workflow V3 [ 131332 ]|