Skip to content

Conversation

@osulzhenko
Copy link
Collaborator

@osulzhenko osulzhenko commented May 13, 2025

🔧 Type of changes

  • new bid adapter
  • bid adapter update
  • new feature
  • new analytics adapter
  • new module
  • module update
  • bugfix
  • documentation
  • configuration
  • dependency update
  • tech debt (test coverage, refactorings, etc.)

✨ What's the context?

What's the context for the changes?

🧠 Rationale behind the change

Why did you choose to make these changes? Were there any trade-offs you had to consider?

🔎 New Bid Adapter Checklist

  • verify email contact works
  • NO fully dynamic hostnames
  • geographic host parameters are NOT required
  • direct use of HTTP is prohibited - implement an existing Bidder interface that will do all the job
  • if the ORTB is just forwarded to the endpoint, use the generic adapter - define the new adapter as the alias of the generic adapter
  • cover an adapter configuration with an integration test

🧪 Test plan

How do you know the changes are safe to ship to production?

🏎 Quality check

  • Are your changes following our code style guidelines?
  • Are there any breaking changes in your code?
  • Does your test coverage exceed 90%?
  • Are there any erroneous console logs, debuggers or leftover code in your changes?

@osulzhenko osulzhenko requested a review from marki1an May 13, 2025 18:43
@osulzhenko osulzhenko self-assigned this May 13, 2025
@osulzhenko osulzhenko added tests Functional or other tests work in progress Signals not finished work labels May 13, 2025
@osulzhenko osulzhenko marked this pull request as draft May 14, 2025 07:36
…hile-creating-activity-infrastructure' into functional-tests/Invalid-GPP
@osulzhenko osulzhenko changed the base branch from master to handle-exceptions-while-creating-activity-infrastructure May 18, 2025 20:31
@osulzhenko osulzhenko removed the work in progress Signals not finished work label May 18, 2025
@osulzhenko osulzhenko marked this pull request as ready for review May 18, 2025 20:33
Comment on lines 2049 to 2054
then: "Generic bidder request should have data in EIDS fields"
def genericBidderRequest = bidder.getBidderRequest(ampStoredRequest.id)
assert genericBidderRequest.user.eids[0].source == ampStoredRequest.user.eids[0].source

and: "Generic bidder request should have data in EIDS fields"
assert genericBidderRequest.user.eids == ampStoredRequest.user.eids
Copy link
Collaborator

Choose a reason for hiding this comment

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

You can leave only last one assert

Copy link
Collaborator

Choose a reason for hiding this comment

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

Meaning just:

and: "Generic bidder request should have data in EIDS fields"
assert genericBidderRequest.user.eids == ampStoredRequest.user.eids

Copy link
Collaborator

Choose a reason for hiding this comment

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

And also please check other cases

def accountId = PBSUtils.randomNumber as String
def ampStoredRequest = getBidRequestWithPersonalData(accountId)

and: "amp request with link to account"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
and: "amp request with link to account"
and: "Default amp request with link to account"

]
}

def "PBS amp call when regs.gpp empty in request should leave EIDS fields in request"() {
Copy link
Collaborator

Choose a reason for hiding this comment

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

What about metrics when the transmit activity proceeds?

assert metrics[ALERT_GENERAL.getValue()] == 1

and: "Generic bidder request should have data in UFPD fields"
def bidderRequest = bidder.getBidderRequest(ampStoredRequest.id)
Copy link
Collaborator

Choose a reason for hiding this comment

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

What about bidderRequest.user.eids?

@osulzhenko osulzhenko requested a review from marki1an May 19, 2025 12:29
@osulzhenko osulzhenko merged commit 6c49d73 into handle-exceptions-while-creating-activity-infrastructure May 19, 2025
1 check passed
@osulzhenko osulzhenko deleted the functional-tests/Invalid-GPP branch May 19, 2025 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tests Functional or other tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants