API Karate tests implementation - Tech Debt
(FAT-892)
|
|
| 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: | Adesh Singh |
| Resolution: | Done | Votes: | 0 |
| Labels: | NFR, quality_control, tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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-RTAC 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.. |
| Comment by Khalilah Gambrell [ 09/Dec/21 ] |
|
Adesh Singh, this feature is blocked due to the api key issue? Can you direct me to the story that addresses this issue? |
| Comment by Adesh Singh [ 10/Dec/21 ] |
|
My Apologies , i have started working on it & forgot to update the status . |
| Comment by Marc Johnson [ 10/Dec/21 ] |
There is no issue for addressing this issue. We decided to use the same workaround that others took before us :-/ I think the workaround of using the diku tenant has the unfortunate impact of coupling these tests to the hosted reference environments (meaning they can't be run against a BugFest environment for example) and they change the state of the tenant that folks use for manual testing. I think this should be resolved. I haven't raised an issue because I don't know who would be responsible for this work. I can raise an issue if that would be helpful? |
| Comment by Khalilah Gambrell [ 10/Dec/21 ] |
|
Thank you Marc Johnson and Adesh Singh |
| Comment by Marc Johnson [ 15/Dec/21 ] |
|
Khalilah Gambrell I've created a
|