Merging old and new test scripts

[govindkrishnamurthi]

Goal - This feature would allow customers to merge specific detail added by them in test scripts into new scripts User Journey:

• The customer has been working with a script - S1. The user has added some specific logic to the script at their end. This new script is S1_modified
• The user creates a new test flow that includes ALL the actions in the previous test, in the same order, and also some new actions.
• The user follows the normal steps to create a new test script, along with indicating that any previous additions to the test must automatically be present in the new script received by the customer. The user needs to send the modified Script S1_modified along with the new JSON to Wringr.
• Wringr receives the new JSON and the modified script S1_modified.
• Wringr compares the old script S1 (stored at Wringr), with the new Script S2 generated from the new JSON to check whether the new test flow satisfies the condition of it being the previous test (exactly) plus new actions.
  • If this test fails, we inform the user that the merge can not be performed at this time and return the new script S2. S2 is stored locally in Wringr.
  • If the test succeeds, then Wringer must merge - add all the additional logic present in S1_modified to S2 to create S2_modified and send S2_modified to the customer. S2, S2_modified is stored in Wringr.

Front-End changes needed

• Mechanism for the customer to indicate that a merge needs to happen. The customer has to send S1_modified along with the JSON.
• A message to the customer taking their permission for data being stored locally
• Display a way for the customer to download S2 and S2_modified.

Back-end modifications

• All JSONs received and associated scripts generated have to be stored going forward. Customer needs to be informed about this change and this feature should be offered ONLY after the customer agrees to data being stored locally.
• New logic to find the old S1 from S1_modified and new JSON have to be developed
• New logic to make sure that the test needed to see whether a merge needs to happen should be implemented
• If merge happens logic to create S2_modified
• Send S2_modified or S2 securely to the customer.

[govindkrishnamurthi]

@andreiqv and @TeutaUkshini ,please take a look at the ticket and make modifications if needed.