Bug 210648 - [JUnit] history should show time taken to execute tests.
Summary: [JUnit] history should show time taken to execute tests.
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-22 07:25 EST by Ketan Padegaonkar CLA
Modified: 2022-09-17 08:00 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ketan Padegaonkar CLA 2007-11-22 07:25:11 EST 
When you switch to another test run in the "test run history" of the JUnit view. The time taken to execute that particular test run gets lost.

This time is important in case people want to measure how long each of the various test runs took to execute.
Comment 1 Dani Megert CLA 2008-09-16 05:42:20 EDT 
Using 3.4 it can now be see it in the top-root. However, it should also appear in the description (Finished after ....).
Comment 2 Eclipse Genie CLA 2020-06-18 16:52:49 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2022-09-17 08:00:01 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.