On 17 August 2012 19:26, Milamber <[email protected]> wrote:
>
>
> Le 16/08/2012 18:43, sebb a ecrit :
>>
>> On 16 August 2012 19:17, Milamber<[email protected]>  wrote:
>>>
>>> [snip]
>>>
>>>
>>> -<component name="Line Graph" index="&sect-num;.3.12">
>>> -<description>To do</description>
>>> +<component name="Line Graph" index="&sect-num;.3.13"  width="837"
>>> height="610" screenshot="linegraph.png">
>>> +<description>
>>> +The Line Graph draws a line chart showing the evolution of response time
>>> during the test, for each labelled request.
>>>>
>>>> Maybe it should be called "Response Time Graph"?
>>>>
>>>> Or if it could be adapted to graph other variables against time, maybe
>>>> "Time Line Graph" would be better?
>>>
>>>
>>> Other variables against time seems less interesting (in a first time).
>>
>> Active thread count could be quite useful.
>
>
> On the same graph (with the response time) or an independent graph?
>

Probably more useful on the same graph, as an optional variable.
If the response time can also be made optional that would be a 3-in-1 graph:
- response time
- active thread count
- response + active count

But it that's hard to do, don't worry.

>
>>
>>> I've prefer use "Response Time Graph". I will make changes on docs.
>>
>> That's much better than Line Graph.
>
>
> Done.
>
>
>>
>>> I've suppose I need to change too the class name (LGraphXXXX to
>>> RespTimeGraph)?
>>
>> It's not essential to change the class name, but it would help to note
>> the GUI name in the header comments if not.
>
>
> Done.
>
>
> Milamber
>
>>
>

Reply via email to