Skip to content
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

Postman collection for all the domains - #1

Open
1 task
vishi24 opened this issue Apr 17, 2024 · 2 comments
Open
1 task

Postman collection for all the domains - #1

vishi24 opened this issue Apr 17, 2024 · 2 comments
Assignees

Comments

@vishi24
Copy link

vishi24 commented Apr 17, 2024

Description

Common postman collection that should work with both protocol server and generic client layer.

The repository does not contain Postman collection for all the domains, a proper Postman collection needs to be created for all the supported domains and all the supported endpoints.
There should be two postman collections

  1. Base URL pointing to protocol server
  2. Base URL pointing to the generic client layer

All the possible values should be in variables.

BEFORE COMMITTING MAKE SURE

  1. All variable values are correct
  2. The postman collection should be ready to use, no changes required after downloading

Goals

  • Postman collections for all supported domains , covering both the protocol server and the generic client layer. These collections will ensure easy access to and testing of all supported endpoints,

Expected Outcome

  1. Two Postman collections will be created:
    • Collection 1: Base URL pointing to the protocol server, containing all supported endpoints and their respective variables.
    • Collection 2: Base URL pointing to the generic client layer, encompassing all supported endpoints along with their variables.
  2. All possible values will be stored in variables within the collections, ensuring flexibility and ease of use for developers.
  3. The collections will be thoroughly tested and verified to ensure that they are ready to use without requiring any modifications post-download.

Acceptance Criteria

  1. Postman Collections Creation: Two Postman collections should be created, each covering all supported endpoints for the protocol server and the generic client layer, respectively.
  2. Variable Usage: All possible values for endpoints, parameters, and headers should be stored as variables within the collections.
  3. Validation Testing: The Postman collections should undergo rigorous testing to verify that all endpoints function correctly and produce expected results.
  4. Ready-to-Use: After downloading the collections, no further modifications should be required to make them usable.
@vishi24 vishi24 self-assigned this Apr 17, 2024
@vishi24
Copy link
Author

vishi24 commented Apr 17, 2024

Before start working on actaul collection creation, list down all the available postman collection with domain, APIs , search implemented and github repository.

@vishi24
Copy link
Author

vishi24 commented Apr 19, 2024

A PR has been raised for the issue
https://github.com/beckn/beckn-sandbox/pull/118
image

@ravi-prakash-v ravi-prakash-v transferred this issue from another repository Jul 23, 2024
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

No branches or pull requests

1 participant