API Karate tests implementation - Tech Debt (FAT-892)

[UXPROD-3393] Tech Debt: Create EDGE-PATRON tests with Karate - R1 2022 Created: 01/Nov/21  Updated: 20/Jan/22  Resolved: 20/Jan/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Lotus (R1 2022)
Parent: API Karate tests implementation - Tech Debt

Type: New Feature Priority: P2
Reporter: Holly Mistlebauer Assignee: Holly Mistlebauer
Resolution: Done Votes: 0
Labels: NFR, quality_control, tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by EDGPATRON-54 Create Karate test for Edge-Patron: ... Closed
is defined by EDGPATRON-55 Create Karate test for Edge-Patron: ... Closed
is defined by EDGPATRON-56 Create Karate test for Edge-Patron: ... Closed
is defined by EDGPATRON-57 Create Karate test for Edge-Patron: ... Closed
is defined by EDGPATRON-58 Create Karate test for Edge-Patron: ... Closed
is defined by EDGPATRON-59 Create Karate test for Edge-Patron: ... Closed
is defined by EDGPATRON-60 Create Karate test for Edge-Patron: ... Closed
Relates
relates to FAT-161 mod-users-bl: Setup API Karate tests ... Open
relates to FAT-165 mod-users-bl: Create test plan to cov... Open
relates to FAT-175 mod-users-bl: Implement API Karate te... Open
relates to UXPROD-3138 Tech Debt: Create MOD-USERS tests wi... Closed
relates to UXPROD-3347 Tech Debt: Create MOD-CIRCULATION tes... Closed
relates to UXPROD-3348 Tech Debt: Create MOD-INVENTORY tests... Closed
relates to UXPROD-3394 Tech Debt: Create EDGE-RTAC tests wi... Closed
Epic Link: API Karate tests implementation - Tech Debt
Back End Estimate: XL < 15 days
Back End Estimator: Holly Mistlebauer
Development Team: Prokopovych
PO Rank: 100

 Description   

Create Karate tests for EDGE-PATRON module.



 Comments   
Comment by Adesh Singh [ 02/Dec/21 ]

Api key issue

we can generate random API keys  but  The problem is that the secret store on the hosting side needs to be aware of the information in them.

we Can not hardcode diku/diku tenant, this creates a coupling that could be challenging in the future. These tests shouldn’t be aware of the diku tenant at all..
 

Generated at Fri Feb 09 00:31:39 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.