Xuanwo opened a new issue, #3066: URL: https://github.com/apache/incubator-opendal/issues/3066
OpenDAL's behavior test greatly enhances the stability and reliability of the openal rust core. I used to think bindings can use rust core directly and don't need to perform their own test frameworks. However, some users blocked by binding issues, for example: https://github.com/apache/incubator-opendal/issues/3037 So I think it's better to build a behavior test framework for all bindings instead. This test framework should reuse all our existing setup and workflows as much as possible. And our binding should only need to implement test case once and can run upon different services. ## Design - Binding read `.env` like `core` does to init different services. - Binding implement behavior test like `core` does, for example, write a file and read it. ## Tasks - [ ] Move all `fixtures` from `core/src/services/{service}` to top-level `fixtures/{service}` - [ ] Java - [ ] Implement functions to read `.env` (and env) to init operator - [ ] Implement `test_write` / `test_read` - [ ] Add java test in `service_test_s3.yml` - [ ] Python - [ ] Implement functions to read `.env` (and env) to init operator - [ ] Implement `test_write` / `test_read` - [ ] Add python test in `service_test_s3.yml` - [ ] Node.js - [ ] Implement functions to read `.env` (and env) to init operator - [ ] Implement `test_write` / `test_read` - [ ] Add node.js test in `service_test_s3.yml` - [ ] Remove Cucumber based BDD Test Other bindings can follow those work based on their own progress. ## Notes This issue is only for bootstrapping the test framework. We will create separate tracking issues for different bindings to continue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
