- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 03-31-2022 01:33 AM
Before we build or design the test strategy, we would need to take care of the business requirements as per the project needs.
For example: -
- What should be the Characteristics, its’s options, the RS, SS, PS and PO?
- How should be the relationship types defined between them?
- What categories should be assigned with respect to the specifications?
Now, the product model will be setup as per requirement and a payload can be generated or framed which can be used to consume the API.
There are two ways to perform test for Order: -
- Use existing ORD.
- Generate new ORD in during ATF execution.
Use existing ORD
With this approach, you need to consume the API manually or via some FLOW... etc. (basically as per your comfort) and follow below steps.
- Query the recently created ORD and validate required fields on it.
- Query for ORDL related to the ORD from above step.
- Validate the required fields on ORDL.
- Approve the ORD, and validate the state changes on both ORD, ORDL.
- Query for product / service orders being generated after approval (based on the product model or your business requirements).
- Open the PO, SO queried in above step and validate the fields as per requirement.
- Check / query for TASK’s as per the FLOW (if it is attached) for decomposition.
- Check / query if product inventories and models are being generated during the decomposition process.
- Validate the state changes on inventories.
- Close the Order.
- Validate the fields, or changes on PI, ORD.
Generate new ORD in during ATF execution
With this approach, you can consume the API in ATF itself, refer below steps:
- Consume the API in the test itself with some payload that is framed as per the product model (i.e., business requirement).
- Query the recently created ORD and validate required fields on it.
- Query for ORDL related to the ORD from above step.
- Validate the required fields on ORDL.
- Approve the ORD, and validate the state changes on both ORD, ORDL.
- Query for product / service orders being generated after approval (based on the product model or your business requirements).
- Open the PO, SO queried in above step and validate the fields as per requirement.
- Check / query for TASK’s as per the FLOW (if it is attached) for decomposition.
- Check / query if product inventories and models are being generated during the decomposition process.
- Validate the state changes on inventories.
- Close the Order.
- Validate the fields, or changes on PI, ORD.
Note: -
I have attached a sample ATF asper the TEST product model created by me, and it includes ORD generation and validation, so you can extend it with your approach or business requirement for testing.
Any suggestions or comments to improve the test cases or approach will be much appreciated.
Hope this helps.
If you think this has helped you or can be helpful for other, please mark it as Helpful, Bookmark it, and share it.
Thank You!
Regards,
Kailash
- 11,703 Views