[E2E Tests] Cover Instance vs. Subaccount vs. Provider vs. Subscriber Destinations in Non-DwC Test
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 41
- Forks
- 33
- Avg merge
- 18h 34m
- Merged PRs (30d)
- 19
Description
Currently, our E2E tests do not cover the difference between /instanceDestinations and /subaccountDestinations. (at least I couldn't find any place).
Ensure our E2E tests cover all 6 following cases:
- provider + instance
- provider + subaccount
- subscriber + override via ALWAYS_PROVIDER+ instance
- subscriber + override via ALWAYS_PROVIDER+ subaccount
- subscriber + instance
- subscriber + subaccount
We should have the same destination name for all 6 cases, but different properties, such that we can assert for each case if the correct destination was fetched
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Java E2E tests for non-DwC destination resolution and run the existing destination-related test suite first. Add coverage for all six provider and subscriber combinations, including ALWAYS_PROVIDER overrides, using one destination name with distinct properties. Done means each case asserts that the correct destination was fetched.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100