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.

Sign up for GitHub

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

Jump to bottom

EVSS PCIU Migration: Identify test users #74975

Closed
Tracked by #73776
jennb33 opened this issue Jan 30, 2024 · 2 comments
Closed
Tracked by #73776

EVSS PCIU Migration: Identify test users #74975

jennb33 opened this issue Jan 30, 2024 · 2 comments
Assignees
@flooose @jennb33
Labels
2024 backend devops practice area categorization -- NOT a team assignment evss PCIU pciu-cleanup platform-product-team

Comments

@jennb33
Copy link
Contributor

jennb33 commented Jan 30, 2024 •
edited by RachalCassity
Loading

Issue Description

Identity test users to facilitate the deprecation process of the PCIU (Personnel and Casualty Information Update) service. As part of the transition to using the VAProfile service, it's crucial to ensure that adequate testing is conducted to validate the functionality and performance of the new integration. Identifying test users who can provide valuable feedback and assist in testing various scenarios is essential for a smooth and successful migration.
@jennb33 jennb33 added backend devops practice area categorization -- NOT a team assignment evss needs-grooming Use this to designate any issues that need grooming from the team platform-product-team labels Jan 30, 2024
@jennb33 jennb33 changed the title Copy of EVSS PCIU Migration: Write/use service class to call VA Profile EVSS PCIU Migration: Identify test users Jan 30, 2024
@RachalCassity RachalCassity added pciu-cleanup blocked and removed needs-grooming Use this to designate any issues that need grooming from the team labels Mar 21, 2024
@jennb33 jennb33 added the needs-grooming Use this to designate any issues that need grooming from the team label Mar 26, 2024
@jennb33 jennb33 removed the blocked label Apr 18, 2024
@jennb33
Copy link
Contributor Author

jennb33 commented May 2, 2024

In 5/2 Grooming meeting: There is a team that is creating the new TUD (Test User Dashboard) - contact ves-developer-experience-team to get our test users!

@jennb33 jennb33 removed the needs-grooming Use this to designate any issues that need grooming from the team label May 2, 2024
@jennb33 jennb33 assigned flooose and unassigned RachalCassity May 29, 2024
@jennb33 jennb33 self-assigned this Jun 24, 2024
@jennb33
Copy link
Contributor Author

jennb33 commented Jun 24, 2024

From EKS Testing meeting on 6/24:

  • Lindsey and Issac were going back and forth on the mock auth
  • There is a Postman collection already
  • We might not need to create any new users, because of what exists already.
  • Pointing to Test User 228 for testing.
  • Peter said there may be some subset of endpoints that may not map to this user
  • We can run the Postman collection
  • Lindsey recommended Test User 99 or Test User 336, we should check with Charlie Strand re: requirements
  • Peter said we should be able to use what is in TUD currently (there are a bunch in there already)

@jennb33 jennb33 closed this as completed Jun 24, 2024
@jennb33 jennb33 mentioned this issue Aug 29, 2024
Open
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flooose flooose

@jennb33 jennb33

Labels
2024 backend devops practice area categorization -- NOT a team assignment evss PCIU pciu-cleanup platform-product-team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@flooose @RachalCassity @jennb33