Bug #9017: Change of a converted error trace does not lead to assotiated leaf reports similarity recalculation - Klever - Open-Source Projects

Actions

Copy link

Bug #9017

closed

Change of a converted error trace does not lead to assotiated leaf reports similarity recalculation

Added by Ilja Zakharov over 6 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Immediate

Assignee:

Vladimir Gratinskiy

Category:

Bridge

Target version:

1.0

Start date:

06/27/2018

Due date:

% Done:

100%

Estimated time:

Detected in build:

svn

Platform:

Published in build:

Description

I have a mark and an unsafe report associated with similarity equal to 0%. When I create a new mark, copy obtained new converted error trace to the old one I expect similarity to be changed from 0% to 100% but nothing happens. Both marks after the change have the same attribute values and same error traces but associated leaf reports differ.

Related issues 1 (0 open — 1 closed)