Skip to content

Conversation

@sethstoudenmier
Copy link
Contributor

Description:

Technical Details:

Requirements for PR Merge:

  1. Unit & integration tests updated
  2. API documentation updated (examples listed below)
    1. API Contracts
    2. API UI
    3. Comments
  3. Data validation completed (examples listed below)
    1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
    2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
    3. Is the expected data returned with the expected format?
  4. Appropriate Operations ticket(s) created
  5. Jira Ticket(s)
    1. DEV-0

Explain N/A in above checklist:

collinwr and others added 30 commits June 10, 2025 18:31
…y/usaspending-api into tst/emr-pipeline-testing
…line-testing-transaction-search-dataframe-integration
…-pipeline-testing-transaction-search-dataframe-integration
…e-testing-transaction-search-dataframe-integration

Combine the two EMR testing branches
@sethstoudenmier sethstoudenmier added the do not merge [PR] shouldn't be merged label Oct 16, 2025
@sethstoudenmier sethstoudenmier changed the base branch from qat to staging October 27, 2025 14:27
@sethstoudenmier sethstoudenmier marked this pull request as ready for review October 30, 2025 20:36
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was moved to avoid confusion as the model in the file is used by a test case and is not a test case itself.

@sethstoudenmier sethstoudenmier removed the do not merge [PR] shouldn't be merged label Nov 5, 2025
@boozallendanny boozallendanny merged commit 2cd0544 into staging Nov 5, 2025
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants