From 52feebeefc586d06a72e794882583ee7b26713d1 Mon Sep 17 00:00:00 2001
From: Victor Tsvetov <vtsvetov@sipwise.com>
Date: Mon, 20 Apr 2020 15:05:11 +0300
Subject: [PATCH] TT#79955 Allow rewriting 'unique_id" in API TestFramework

Following "TT#74160 Allow reuse of API TestFramework object",
allow calling the same API TestFramework object with different
'unique_id" value.

Change-Id: I4119361fee64629466668d49244961123c4b72b6
---
 lib/NGCP/API/TestFramework.pm | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/lib/NGCP/API/TestFramework.pm b/lib/NGCP/API/TestFramework.pm
index 4de4902371..70715a0d01 100644
--- a/lib/NGCP/API/TestFramework.pm
+++ b/lib/NGCP/API/TestFramework.pm
@@ -29,7 +29,7 @@ has 'file_path' => (
 
 has 'unique_id' => (
     isa => 'Str',
-    is => 'ro'
+    is => 'rw'
 );
 
 sub run {
@@ -77,8 +77,10 @@ sub run {
     my $test_executor = NGCP::API::TestFramework::TestExecutor->new();
 
     # If $self->{retained} is already defined, use its previously collected variables.
-    # Otherwise, initialize it with received "unique_id" for fields that need to be unique.
-    my $retained = $self->{retained} //= { unique_id => $self->unique_id };
+    # Otherwise, initialize it.
+    # In any case, update with received "unique_id" for fields that need to be unique.
+    my $retained = $self->{retained} //= {};
+    $retained->{unique_id} = $self->unique_id;
 
     my $test_case_result = { success => 1, error_count => 0 };