Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QA - Create common resource for Charles Proxy map local files #9437

Closed
4 tasks done
TKDickson opened this issue Aug 22, 2024 · 2 comments
Closed
4 tasks done

QA - Create common resource for Charles Proxy map local files #9437

TKDickson opened this issue Aug 22, 2024 · 2 comments
Assignees
Labels
Closed - Deployed/Fixed documentation QA and Release Label identifies this work is done on the QA and Release Team QA Tickets require QA work / review QA 2 QA work sized as a 2

Comments

@TKDickson
Copy link
Contributor

TKDickson commented Aug 22, 2024

Charles Proxy is an important tool for mocking responses from APIs, especially when we are unable to create or update staging data to cover edge cases.

Right now each QA on the team has their own Charles Proxy methods, and local stash of files that they map to. We'd like to pool those - for instance, only the H&B QA now has the information on how to map claims calls for the new 8-step data. With a shared folder that we all pull from and update, we'd hopefully be able to easily share that information.

ACs:

  • Create a private folder to house Charles Proxy calls, probably with some subfolders (errors, [feature X], [feature Y], etc)
  • Create documentation about how to add files (ex: file format, naming convention, do the files include headers or not, etc) that can just live in the parent folder
  • Add your own local mapping files to the folder(s)
  • Share the information with the QA team

This ticket explicitly does not include 'badgering other QA to add their files' as an AC. Feel free to close the ticket once your individual work is complete.

@TKDickson TKDickson added documentation QA and Release Label identifies this work is done on the QA and Release Team QA Tickets require QA work / review QA 2 QA work sized as a 2 labels Aug 22, 2024
@TKDickson TKDickson added this to the Sprint XXX, release 2.42 milestone Nov 6, 2024
@kellylein kellylein removed this from the v2.42.0 milestone Nov 26, 2024
@DJUltraTom
Copy link
Contributor

closing as A/C has been met

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed - Deployed/Fixed documentation QA and Release Label identifies this work is done on the QA and Release Team QA Tickets require QA work / review QA 2 QA work sized as a 2
Projects
None yet
Development

No branches or pull requests

3 participants