When I read other Issues "Common database service" title issues/4 solved all question marks in my mind. This issue can be closed. The other thing that the design drawing could be useful for the future, I just wanted to create a discussion for what could be for the future and help for the drawing?
Hi @anthdm,
I’d like to open a discussion about the frameworks, tools, and libraries we should adopt to ensure we achieve our goals effectively.
Key Points for Discussion:
1. Testing and QA:
What testing frameworks and tools should we adopt for unit, integration, and end-to-end testing in Go? (e.g., Testify, GoConvey, Selenium)
What best practices should we follow to maintain high code quality and performance benchmarks?
2. Other Tools and Libraries:
Are there any additional tools, libraries, or resources you believe would be beneficial for the Superkit project? (e.g., Redis for high performance and caching)
When I read other Issues "Common database service" title issues/4 solved all question marks in my mind. This issue can be closed. The other thing that the design drawing could be useful for the future, I just wanted to create a discussion for what could be for the future and help for the drawing?
Hi @anthdm,
I’d like to open a discussion about the frameworks, tools, and libraries we should adopt to ensure we achieve our goals effectively.
Key Points for Discussion:
1. Testing and QA: What testing frameworks and tools should we adopt for unit, integration, and end-to-end testing in Go? (e.g., Testify, GoConvey, Selenium) What best practices should we follow to maintain high code quality and performance benchmarks? 2. Other Tools and Libraries: Are there any additional tools, libraries, or resources you believe would be beneficial for the Superkit project? (e.g., Redis for high performance and caching)
Thank you for your contributions!