Bug 518427 - [PHPUnit] Trace failure isn't helpful to track unit test problem
Summary: [PHPUnit] Trace failure isn't helpful to track unit test problem
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: PDT (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PHP UI CLA
QA Contact: Sylvia Tancheva CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-18 17:05 EDT by Michal Niewrzal CLA
Modified: 2020-05-14 10:15 EDT (History)
6 users (show)

See Also:
kaloyan: review? (zulus)
kaloyan: review? (thierryblind)
kaloyan: review? (ibazzi)
kaloyan: review+
kaloyan: review? (wywrzal)
bartlomiej.l: review+

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 Michal Niewrzal CLA 2017-06-18 17:05:30 EDT 
Currently, you cannot find exact place of failure with Trace Failure tab from PHPUnit view. With double click editor with executed method is opened, not place from unit test execution stack.
Comment 1 Eclipse Genie CLA 2017-06-19 03:34:36 EDT 
New Gerrit change created: https://git.eclipse.org/r/99557
Comment 2 Kaloyan Raev CLA 2017-06-19 07:39:32 EDT 
Request for including the fix for this bug in 5.0.1.

The Trace Failure is really useless if it misses the frames of the actual test case.
Comment 4 Kaloyan Raev CLA 2017-06-22 03:31:20 EDT 
Cherry-picked to the stable-5.0 branch.