Automation Approach for Sanbox 2.0 documentation & discussion #2

[emmayank]

Description

Develop a comprehensive automation (mocking) approach for Sandbox 2.0 utilizing Strapi. The primary focus is on mocking on_status updates. This task involves creating a detailed approach document and identifying all domains supported by Strapi.

Goals

• [x] Document the automation strategy for mocking on_status updates and any other if required
• [x] Identify all domains supported by Strapi that are relevant to this project.
• [x] Create a detailed approach document to guide the implementation.
• [x] Ensure the approach is scalable, maintainable, and aligned with project goals.

Expected Outcome

1. A well-documented automation approach that can be used by the team to implement the necessary mocking.
2. A list of all domains supported by Strapi and how they will be utilized in the automation.
3. Clear guidelines on how to implement the mocking for on_status updates and other api calls in Sandbox 2.0.

Acceptance Criteria

• [x] Comprehensive approach document created and reviewed.
• [x] All relevant domains supported by Strapi are identified and documented.
• [x] Mocking of on_status updates is defined with clear steps for implementation.

Product Name

Sandbox 2.0

Domain

Sandbox

Tech Skills Needed

• Backend Development

Complexity

Medium

Category

Sandbox

Sub Category

Feature Implementation

[emmayank]

[Proof of Completion] https://fide-official.atlassian.net/wiki/spaces/EC/pages/edit-v2/553615361?draftShareId=bb2421d6-77dc-4655-aa03-ff70c1f2aa88

[emmayank]

Hey @vbabuEM ,

Requesting you to please review the approach document present here. i can give you a basic overview of the requirement.

This is not so urgent, but it would be good if we close it, this week itself, as the team can pick the development from next iteration.

thanks @emmayank

cc:: @faizmagic

[vbabuEM]

@emmayank , if the requirements have been reviewed by @faizmagic and they are just as listed in the document. The rest of the document looks ok. There are few things that come to mind.

1. We might have to expose this as a deployment to customers. So we might have to keep the overall Sandbox2.0 in a state that users can install and use it.
2. To mimic the current sandbox, we might need to add more catalogs than what is currently present in Strapi. @em-abee might know more Otherwise, this seems ok for the status update.

[emmayank]

thanks for the update @vbabuEM . @em-abee lets discuss this point in our next call with @faizmagic whenever we have it

[yesrag2309]

@emmayank -As discussed in today’s sync-up call, if the review is not a priority, let's create a duplicate of this card for review and close the original. We need to discuss with @faizmagic which iteration the newly created review card can be mapped to.

@viraj89

[emmayank]

@yesrag2309 - created the ticket here - https://github.com/beckn/beckn-utilities/issues/139

closing this ticket now