-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
alter sonobi unit test to fix Edge test failure #2904
Conversation
@@ -318,6 +318,10 @@ describe('SonobiBidAdapter', () => { | |||
|
|||
it('should map bidResponse to prebidResponse', () => { | |||
const response = spec.interpretResponse(bidResponse, bidRequests); | |||
response.forEach(resp => { | |||
let regx = /http:\/\/localhost:9876\/.*?(?="|$)/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure hardcoded the port is a good way to prevent this error. I'm not sure but some process is generating the port (karma?) and we should probably use whatever it is assigning or figure out another way to prevent this test case failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like we discussed offline - I removed the port values from the unit tests. Please take another look when possible.
* alter unit test to fix Edge test failure * removing port from unit test
* alter unit test to fix Edge test failure * removing port from unit test
* alter unit test to fix Edge test failure * removing port from unit test
* alter unit test to fix Edge test failure * removing port from unit test
* alter unit test to fix Edge test failure * removing port from unit test
Type of change
Description of change
After #2891 was merged into master, Travis began reporting test failures in the sonobiBidAdapter_spec.js file for a unit test in Edge.
See link below:
https://travis-ci.org/prebid/Prebid.js/builds/408728279?utm_source=slack&utm_medium=notification
This PR fixes the error by standardizing the
ref
href URL the unit test utilizes to just the domain (since random numbers are sometimes added in the url when running browserstack).