Open Rajaneeshkumar opened 3 days ago
Hi @Rajaneeshkumar ,
Thank you for raising this detailed feature request. I appreciate you taking the time to share your specific use cases and challenges.
I've tagged this with question
label. I will review your requirements and get back to you with more detailed feedback later today.
We value your input in making Specmatic better.
Thanks, Pranav
Thanks for checking this on a priority @pranavgawri !! Expecting feedback and would be happy if there is any workaround .
Hi @Rajaneeshkumar ,
Thanks for your patience.
I hope this helps, please feel free to let me know in case you have any other doubts or confusions.
Thanks, Pranav
Is your feature request related to a problem? Please describe. I am currently exploring Specmatic for contract testing of our microservices. While I appreciate its ability to dynamically generate provider tests by simply passing an OpenAPI (YAML) file, I’ve encountered limitations that hinder its usability in certain scenarios:
1)Lack of Mock Data Customization: Unlike the setExpectations feature for consumer-side contract tests, there’s no straightforward way to provide mock data for specific requests during provider-side contract testing. 2)Dependency Management Across Requests: Some test scenarios require prerequisites, such as creating resources (e.g., generating an ID) that need to be reused in subsequent requests. Specmatic doesn’t seem to support this workflow seamlessly.
These limitations are making it difficult for me to decide whether to continue with Specmatic or switch to another tool that better fits our requirements.
Describe the solution you'd like It would be highly beneficial if Specmatic provided more customization options and flexibility for generating contract tests
Additional context I have recently contributed to Specmatic and have a fair understanding of it https://github.com/znsio/specmatic/issues/1429
Your valuable suggestions would greatly help us move forward. This is a bit urgent, so I would appreciate your prompt response. Thank you!
@harikrishnan83 @samyakOO7