Skip to content
Test Implementations

Validate 'isFirstParty' logic for tracker that only has eTLD+2 domain defined #217

Sign in to view logs

Validate 'isFirstParty' logic for tracker that only has eTLD+2 domain defined

Validate 'isFirstParty' logic for tracker that only has eTLD+2 domain defined #217

GitHub Actions / BSK Test Report failed Oct 9, 2024 in 0s

1568 tests run, 1556 passed, 10 skipped, 2 failed.

Annotations

Check failure on line 1 in BrowserServicesKit/.build/arm64-apple-macosx/debug/BrowserServicesKitTests.build/ContentBlockerReferenceTests.d

See this annotation in the file changed.

@github-actions github-actions / BSK Test Report

ContentBlockerReferenceTests.testDomainMatching 

/Users/runner/work/privacy-reference-tests/privacy-reference-tests/BrowserServicesKit/Tests/BrowserServicesKitTests/ContentBlocker/ContentBlockerReferenceTests.swift:184 - XCTAssertEqual failed: ("0") is not equal to ("1")

Check failure on line 1 in BrowserServicesKit/.build/arm64-apple-macosx/debug/BrowserServicesKitTests.build/ContentBlockerReferenceTests.d

See this annotation in the file changed.

@github-actions github-actions / BSK Test Report

ContentBlockerReferenceTests.testDomainMatching 

/Users/runner/work/privacy-reference-tests/privacy-reference-tests/BrowserServicesKit/Tests/BrowserServicesKitTests/ContentBlocker/ContentBlockerReferenceTests.swift:189 - failed - Expected to detect tracker for test same party ignore with deeper subdomain
View more details on GitHub Actions